Distribution Engine

This section explains how the Distribution engine builds outbound segments, batches (ICLs), and transmissions.

Overview
The primary purpose of the Distribution engine is to build outbound segments, batches (ICLs), and transmissions. The Distribution engine creates the logical data structure for multiple types of transmissions within the FTM database.
Configuring Distribution
Thresholds
When describing thresholds and the mapping process, understand that for check related transmission format types, transactions are mapped to segments, segments are mapped to batches, and batches are mapped to transmissions.
Deferred settlement and outbound batches (ICLs)
When mapping transactions to outbound batches (ICLs), the Distribution engine does not combine transactions for deferred settlement with transactions that are not for deferred settlement in the same batch (ICL).
Outbound Transmission Creation
The build transmission request can be generated in the following ways:
Outbound transmission reversal
An outbound reversal transmission is created when a financial institution has received a transmission and, for some reason, wants to reverse either all or part of it.
Outbound transmission remake and release
Outbound remake transmissions are created when a financial institution needs to remake an existing transmission and send either all or part of it to another immediate destination or connection.
Cutoffs and deadlines
Pausing and Resuming Distribution
Designating the File Name
FTM Workflow Transmission Format Releasing
After the outbound transmission structure is created in the FTM database, a WebSphere® MQ message is placed on a queue that is monitored by the broker.
Release Trackables
Marking transmissions as having met their deadline
Marking Transmissions as Processed
End of Day Processing
Purge processing

Parent topic: Distribution User's Guide