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.

For all other format types, there are no segments and so transactions are mapped to batches. Then, batches are mapped to transmissions. Therefore, in the following description you must keep in mind the format type being mapped to understand which thresholds apply for a given transmission format type. For example, when mapping NACHA format transmissions, there is no transaction to segment mapping and so threshold formats are not used.

In addition to checking the transactions for each segment threshold, the mapping process checks the outbound batch (ICL) and transmission thresholds as it maps transactions to outbound segments. Outbound batches (ICLs) have thresholds for the maximum number of transactions that are allowed in the batch (ICL) and the maximum value of the batch (ICL). The batch (ICL) maximum number of transactions threshold is specified in the Distribution user interface on the properties for batches / ICLs screen and can be overridden in the building options that are associated with the endpoint. The batch (ICL) maximum value threshold is specified in the Distribution user interface on the properties for batches / ICLs screen and cannot be overridden.

Transmissions have thresholds for the maximum number of transactions that are allowed in the transmission, the maximum value of the transmission, and the maximum size of the transmission in bytes. The transmission threshold values are specified in the Partner Profiles global transmission settings. These system values can be overridden by the transmission definition that is specified for the partner in Partner Profiles. Specifying a value of minus 1 (-1) for any of the batch (ICL) and transmission thresholds signifies that a limit is not wanted for that parameter.

If either of the batch (ICL) thresholds are met while the mapper is mapping transactions to a segment, the segment and batch (ICL) are closed so no additional transactions are put into the segment or batch (ICL). A new batch (ICL) and segment are then opened and any additional transactions are added to the new segment and batch (ICL). If the maximum number of transactions or maximum value transmission thresholds are met while the mapper is mapping transactions to a segment, the segment, the batch (ICL), and the transmission are closed and a request to build the transmission is sent to a WebSphere® MQ queue. A new segment, batch (ICL), and transmission are opened and any additional transactions are added to the new segment, batch (ICL), and transmission.

The batch (ICL) and transmission maximum number of transactions and maximum value thresholds are trigger mechanisms to stop adding transactions to the batch (ICL) or segment. As such, the batch (ICL) and transmission might exceed the threshold. For example, consider a batch (ICL) that has a maximum value threshold of $1,000,000 and it currently contains $990,000. If a transaction for $15,000 comes in, it is mapped to the batch (ICL) even though the maximum value threshold of $1,000,000 is exceeded. The $15,000 transaction is included so the batch (ICL) now contains $1,005,000 and has reached its threshold. It is closed and a new batch (ICL) for additional transactions is opened.

For X9 transmissions, the transmission size threshold cannot be exceeded. If the transmission size threshold is set to 10,000,000 bytes, the engine does not build a transmission bigger than 10,000,000 bytes. If the next segment to include in the transmission pushes the transmission size over the size threshold, the segment is moved to a new transmission. The exception to this is if the size of a single segment is greater than the transmission size threshold. The Distribution engine does not split segments into smaller pieces. Therefore, if a single segment is larger than the transmission size threshold, the transmission is created with that one segment. For this reason, you should be careful not to create a segment size that is too large.
Note: For physical transmissions built by a WebSphere broker workflow or map, the transmission size threshold that is specified in the Distribution option is ignored because the broker map is solely responsible for building the physical transmission.

A segment is ready to build when it contains the number of transactions, as specified by the maximum transaction segment property, or when the batch (ICL) or transmission that the segment is contained in meets one of its thresholds. The maximum number of transactions per segment is specified in the building options for the endpoint in Partner Profiles. If the maximum number of transactions value that is specified for the batch (ICL) or transmission is smaller than that for the segment, the value that is specified for the segment is used for the transmission and batch (ICL). When an X9 segment is ready to build, the engine posts an internal message to itself through a WebSphere MQ Queue to build the physical segment. This message contains the outbound segment ID of the segment that is ready to be built. Segments that are not X9 segments are closed after they reach their threshold and remain closed until the transmission is built.

Note: When the number of transactions per segment is set to a smaller number while processing segments, the new value goes into effect immediately. However, if any segments currently have more than the new maximum segment size, they are not posted as ready to build until another transaction is mapped to that segment. For example, the current processing is using a maximum segment size of 500, and transactions are being mapped to a segment that contains approximately 325 transactions. If the maximum segment size is changed to 300, the segment with 325 transactions remains in the open state until another transaction is mapped to that segment. The segment is closed and a request to build it is posted to the segment queue.