Columns
The columns on the outbound transmissions page show basic information about the transmissions that are associated with a business day. The columns available on the outbound transmissions page are shown in the following table.
| Column name | Description |
|---|---|
| Replica Identification | A transmission is identified as a replica when the associated endpoint configuration has an assigned replication endpoint. Transactions that are assigned endpoints that have a replication endpoint are included in different transmissions. The same transactions are in both transmissions, but might have different building options. The replica transmission that is created and processed for the replication endpoint is identified by a shaded background. A replica icon, which resembles sheets of paper, is shown next to the transmissions that are replicas. |
| Holdover Identification | When the holdover process is run, all open (untransmitted) transmissions are re-created
and remapped to holdover endpoints. These holdover endpoints are configured to deliver the transmissions to
the inbound landing zone for processing the next business day. The created holdover transmissions must be
manually built and released by the user. A holdover icon, which resembles an asterisk or a star, is shown next
to the transmissions that are held over. Note: Holdover is only available when Check is
installed.
|
| Sidepoint identification | A transmission is identified as a sidepoint when it contains copies of transactions. Copies of transactions are created by Business Rules during ingestion. The copied transactions might be included in multiple transmissions that each have different building options. A sidepoint icon, which resembles lines of text with an arrow, is shown next to the transmissions that are sidepoints. |
| Stacked transmission identification | A transmission is identified as a stacked transmission when Distribution creates a new transmission that is a concatenation of multiple transmissions that
are destined for a single receiving participant. The stacked transmission consists of a parent
transmission and its children. The parent is listed first and is followed directly by its children.
The parent and child transmissions are identified by icons that are shown next to transmissions that
are stacked. The parent icon looks like an organizational chart with the higher level highlighted.
The child icon looks like an organizational chart with the lower level highlighted. The totals that are displayed for a parent transmission are calculated from the totals of its children. Therefore, the totals for the parent transmissions are excluded from the aggregate totals that are displayed in the column headers. Note: Stacked transmissions are NACHA only.
|
| Business Day | The business day represents the processing date and category with which this
transmission is associated. The value in the business day column is a combination of the site, business date,
and category fields, which are separated by commas. The category can be used to separate work for the same
business date. The status of the business day is shown within parentheses. For example, 0, 2008-05-21,
4 (Active)
Business days are defined by the bank, and are created and maintained by the Transaction Server. For more information about business days, see Business Day Management. |
| Status | Displays the status of the transmission. As an outbound transmission is
created, built, and presented to a participant, each transmission goes through a sequence of status
changes. Valid values for the transmission status are shown in the following list:
For child transmissions that are in a stacked transmission, the status of their parent
transmission is displayed in this column.
Note: Stacked transmissions are NACHA
only.
|
| FTM Transmission Id | A unique ID assigned to the outbound transmission. The ID is optionally assigned, depending on the channel associated with the outbound transmission. |
| Bank | The bank number is a unique identifier that represents the processing bank. The bank number is a numeric value that is created and maintained by using the manage banks page. The bank ID is assigned as work is processed, either through CPCS MICR for paper documents, or through the Gateway for electronic payments. For more information, see Banks Management. |
| Receiver | The name of the receiver that this transmission is presented to. The participant
identifies with whom this work is to be financially settled. This column displays a combination of the
logical description and the participant ID, which is represented by a routing transit number or free-formed
name. An example is For more information about managing participants, see Participants page. |
| Message Standard | The message standard defines the rules that control the context and content of the transmission. The message standard might include a version or revision number, and the transmission needs to comply with this standard. |
| Format | The format of the transmission to create when the transmission is to be presented to a
participant. Each format uses different formatting standards that identify how the content of the transmission
is to be created. Examples of the formats are X9.37, X9.100-180, X9.100-187.
The formats correspond to individual transmission definitions that are maintained in the configuration. For more information about transmission definitions, see Transmission Definitions Management. |
| Cutoff | The cutoff time represents when a transmission is to close, which means no
more transactions are placed in the transmission, and when to start the building process for the
outbound transmission. This time is displayed in the preferred display locale of the user, which is
controlled by the user preferences in the Control Center.
Example:
If the cutoff is the final cutoff for that business day, the cutoff appears in a bold font and is represented with blue text. Distribution uses the WebSphere® Scheduler services to automatically start building the transmission at the cutoff time and then present it to the participant. Transmissions that are registered to automatically build at the specified cutoff time are indicated visually. If this indicator does not exist, this transmission is not scheduled to automatically build. When Distribution automatically starts building the transmission by using the cutoff time, the scheduled indicator is replaced with a checkmark to indicate that the automated task ran successfully. A cutoff time becomes unavailable when work is received and processed after the identified
deadlines for that business day. When this situation occurs, the record shows the cutoff time as
-unavailable- and the transmission is not automatically registered to build by using the scheduler.
The transmission can be presented to a participant only by manually initiating the build process
within the user interface.
Note: If the building of a transmission is started manually, and not
initiated by the automated task within the scheduler, the automated task in the scheduler is
canceled. The scheduler indicator is no longer displayed.
If the transmission is configured for end of day delivery, the cutoff is not used because the transmission is built and released when the send event is received. For filtering purposes, the end of day delivery is treated as the final cutoff for that business day. If the transmission is configured for file to file delivery, the cutoff is not used because the transmission is built and released when the associated inbound transmission is processed. |
| Deadline | The deadline time represents when a transmission is considered to be late.
This time is displayed in the preferred display locale of the user, which is controlled by the user
preferences in the Control Center. Example:
A deadline is considered missed when the transmission is not successfully placed in the release location by the deadline time. If the deadline is the final deadline for that business day, the deadline appears in a bold font and is represented with blue text. To identify when deadlines are missed, a WebSphere scheduler task is created for each transmission that is expected to be
presented to a participant. Each registered task that is scheduled for a deadline has a bell icon
next to the deadline time, which indicates that Distribution is scheduled to monitor and
report if this deadline was missed. When a transmission is presented before the deadline time, the
Distribution engine cancels the deadline monitoring task and indicates that the deadline
was met by replacing the bell icon with a checkmark. When the Distribution engine didn't
present the transmission and cancel the deadline task in time, the transmission that missed its
deadline is identified by an error (X-mark) indicator displayed next to the deadline time.
Note: If
a visual indicator is not next to the deadline time, a failure occurred registering the missed
deadline task for the transmission.
A deadline time becomes unavailable when work is received and processed after the identified deadlines for that business day. When this situation occurs, the record shows the deadline time as -unavailable- and the transmission is not automatically registered to detect a missed deadline. The transmission can be presented to a participant only by manually initiating the build process within the user interface. If the transmission is configured for end of day delivery, the deadline is not used because the transmission is built and released when the send end of day transmission event is received. For filtering purposes, the end of day delivery is treated as the final deadline for that business day. If the transmission is configured for file to file delivery, the deadline is not used because the transmission is built and released when the associated inbound transmission is processed. |
| Connection Owner | The ID of the participant that is configured for the electronic connection that is
associated with the transmission. Electronic connection information for a transmission is in the
<connectionId> element in its route file. |
| Control Credit Amount | The credit amount represents the expected total value of all credit transactions within this transmission. The column header displays the aggregate total for all of the records in the column. |
| Control Debit Amount | The debit amount represents the expected total value of all debit transactions within this transmission. The column header displays the aggregate total for all of the records in the column. |
| Batch Count | The total number of batches (ICLs) for the transmission. A batch (ICL) is a financial
transaction that is sent by the processing bank that indicates how the bank expects to be paid. If the total
number of batches (ICLs) is greater than zero for this transmission, this number is a link. Click the link to
go to the batch / ICL page that displays only the batches (ICLs) associated with this transmission
record. The column header displays the aggregate total for all of the records in the column. |
| Distribution Type | Indicates whether the transmission contains original transactions or copies of
transactions. Valid values for the distribution type are shown in the following list:
|
| Notification Rqst Sent | Displays the status of the notifications that are being sent. Notification is
an optional service that is provided by Distribution that identifies summary information
about the transmission and the time it was sent. The request (Rqst) field identifies if a participant requested notification for each transmission they are to receive. The field has a value of yes or no. The sent field can hold different kinds of values. Dashes indicate that the notification has yet to be sent and a checkmark indicates that the notification was successfully sent. The date and time that the notification was sent is viewed by hovering the mouse over the check mark or by viewing the details of the record. |
| Transmission Name | The transmission name is the name of the created file. Until the file is built, it is not available. The transmission name that is displayed is limited to 20 characters. The full transmission name can be viewed by hovering the mouse over the name. |
| Release Trigger | Indicates whether the transmission was built and released by a user or by the scheduler. |
| Production / Test Indicator | Indicates whether the transmission is a test transmission or not. The letter T indicates that the transmission is a test transmission. |
| Connection | The ID for the electronic connection that is associated with the transmission.
Electronic connection information for a transmission is in the <connectionId> element in
its route file. |
| Connection Channel | The channel type for the electronic connection that is associated with the transmission.
Electronic connection information for a transmission is in the <connectionId> element in
its route file. |
| Custom Descriptor | The custom descriptor for this transmission. |
| Credits | The total number of credit transactions in this outbound transmission. The column header displays the aggregate total for all of the records in the column. |
| Debits | The total number of debit transactions in this outbound transmission. The column header displays the aggregate total for all of the records in the column. |
| Transmission Sequence Number | Displays the sequence number that was generated for this outbound transmission. The sequence number increments for each transmission that is received until it reaches the maximum value that is configured in the transmission properties. Transmissions that are received after the maximum value was reached for a business day transition to an error status. This sequence number is typically used for Canadian ICL transmissions. |
| Addenda Count | The total number of addenda records associated with the transmission. This number is calculated when the transmission is released. The column header displays the aggregate total for all of the records in the column. |
| Parent Id | The ID of the parent transmission. This column shows an ID only when this transmission is a child in a stacked transmission. Otherwise, dashes are displayed. |
| Created | The date that the transmission was created in the database. |
| File Created | The date that the physical file was created. |
| Auxiliary Extract 1 | Indicates that the custom auxiliary extract 1 task completed successfully. |
| RDFI Id | The receiving depository financial institution (RDFI) identification number. |
| Distribution Window Name | The distribution window that is associated with the outbound batch (ICL). |
| FTM Base Status | Displays the status of the transmission from FTM. |
| Identifier | The unique transmission identifier that is used by Distribution for identifying this transmission. This identifier is an internal processing ID. |
| Transmission Definition | The transmission definition name of the transmission. |
| Payment Scheme | The payment scheme name of the transmission. |
| Outbound Currency | The three-letter currency identifier of the transmission. |
| Cancel Type | When the reverse operation is run on an outbound transmission, this column is
set to the cancellation type of the message standard for the transmission, either
Cancel or Reverse. |
| System Debit Amount | The control debit amount that is formatted by the locale and system currency. |
| System Credit Amount | The control credit amount that is formatted by the locale and system currency. |
| Receiver Routing | The routing identifier of the receiver. |
| Transmission Records | The total number of records in the transmission. |
| File Id Modifier | The file ID modifier of the transmission. |
| File Path | The location of the completed transmission file. |
| File Size | The size in bytes of the completed transmission file. |
| Released | The time the transmission was released. |
| Sent | The time the transmission was sent (transmitted). |
| Accounted | The time the accounting task completed processing the transmission. |
| Billed | The time the billing task completed processing the transmission. |
| Remarks | Contains information that is related to any exceptions that occur while the transmission is being processed. |
| Archivable | This column is set to Yes at the time the transmission is
built if there archive services are associated with any of the outbound batch endpoints of this
transmission. Otherwise, it is set to No. |
| Archived | The time that the archive task processed the outbound transmission. |
| Delivery Type | The method of release for the transmission. The delivery type is one of the
following values:
|
| File to File Id | When the File to File property of the transmission
definition is configured as Yes, this column contains the inbound transmission
identifier of the transmission. |
| Settlement Loaded | The time the settlement application loaded data for the transmission. |
| Total Item/Addenda Count | Total number of transactions and related addenda. |
| Total Transactions | Total number of transactions, excluding addenda. |
| Customer Unique Id | The customer unique work flow identifier that was provided by the route file. |
Data filtering
The list of transmissions that are displayed can be filtered by using the filter functions. To filter the transmission list, first select a business day or a range of business days. The default for the business day filter is the most recent business day. You can filter on all business days or on a single business day by using the Business day filter fields.
After a business day is identified, use the Filter field to choose a particular column on which to filter. To display the unfiltered list, select - No Filter - from the Filter list. Click Go to apply the filtering.
| Filter | Operator type | Search term examples |
|---|---|---|
| Bank | Numeric | 5 |
| Receiver Name | String | MyBank |
| Transmission Name | String | X937.T.R399081031.N8103.D090811.T092936 |
| Deadline | Static | Select from a list of deadline choices. |
| Holdover | Static | Select from a list of holdover choices. Note: Holdover is only available when Check is installed.
|
| System Credit Amount | Numeric | 127000 or 127000.50 Note: The filtering on financial data does not support the grouping
delimiters (for example, commas).
|
| System Debit Amount | Numeric | 127000 or 127000.50 Note: The filtering on financial data does not support the grouping
delimiters (for example, commas).
|
| Notification | Static | Select from a list of notification criteria. |
| Status | Static | Select from a list of status types. |
| Unmapped Transmissions | Static | This filter has no search term. Selecting this filter displays the unmapped transmissions and the mapped transmissions. |
| Distribution Type | Static | Select from a list of valid distribution types. |
| Created | Date | 2017-08-25. The date must be in the format yyyy-mm-dd. |
| File Created | Date | 2017-08-25. The date must be in the format yyyy-mm-dd. |
| Stacked Transmissions | Static | This filter has the following search terms.
|
| FTM Transmission Id | Integer | 3 |
| Identifier | Integer | 1 |
| Message Standard | Static | Select from a list of message standards. |
| Format | Static | Select from a list of formats. |
| Connection Owner | String | 987654320 |
| Cancel Type | Static | Select from a list of cancel types. |
| Release Trigger | String | Manual |
| Custom Descriptor | String | ACHP |
| Receiver Routing | String | 987654320 |
| Credits | Numeric | 5 or 5000 Notes:
|
| Debits | Numeric | 5 or 5000 Notes:
|
| File Id Modifier | Character | A. Valid ID modifiers are A-Z, 0-9. |
| Addenda Count | Integer | 0 |
| Distribution Window Name | String | Distribution Window A |
| Total Item/Addenda Count | Integer | 4 |
| Total Transactions | Integer | 4 |
| Auxiliary Extract 1 | Date | 2017-08-25. The date must be in the format yyyy-mm-dd. |
| Business Day | Date | 2017-08-25. The date must be in the format yyyy-mm-dd. |
| FTM Base Status | Static | Select from the list of statuses. |
All of the filters in the previous table act as OR filters, which means that you can filter on only one of the available column filters at a time. For example, you can filter on the transmission name or the transmission type, but not both. A filter in the following table can be used as an AND filter, which means it can be used in addition to one of the filters in the previous table. The AND filters mean that the transmissions can be filtered by using any of the previous filters, and then filtered again by using one of the filters in the following table.
| Filter | Operator type | Search term |
|---|---|---|
| Transmitted | Static | Select a start and end date range. The transmitted filter appears as an option only when the sent column is selected in the user preferences. |
| Deadline | Static | Select a start and end date range. The deadline filter appears as an option only when the deadline column is selected in the user preferences. |
| Created | Static | Select a start and end date range. The created filter appears as an option only when the created column is selected in the user preferences. |
| File Created | Static | Select a start and end date range. The file created filter appears as an option only when the file created column is selected in the user preferences. |
| Business Day | Static | Select a start and end date range. The business day filter appears as an option only when the business day column is selected in the user preferences. |