Holdover

Note: In this section, "released and transmitted" and "releasing and transmitting" refer to transmissions that are out of the scope of Distribution. The setting is controlled by the deadline met on transmission release property configuration. If true, the transmission is considered out of scope when it has been copied to the release location. If false, the transmission is not out of scope until the transmitted status is received from Gateway. Holdover checks are performed based on this setting.

Holdover is the process of reassigning and reprocessing any outstanding transactions to another business day. The holdover process is done as part of the business day end of day process to allow the outstanding transactions to be reassigned to the next day.

It is initiated when Distribution receives a business day holdover message. When the message is received, Distribution determines if the holdover can currently be processed. If it is determined that the holdover cannot continue, Distribution sends an error message that describes the reason in a messaging API service response message. The conditions that must be met for a holdover to be allowed are:
  • No outbound transmissions currently releasing and transmitting
  • No outbound replica transmissions that would be eligible for holdover are replicas of an outbound transmission that has already been released and transmitted.
When these conditions are met, Distribution performs the following steps for holdover:
  1. Only outbound batches (ICLs) that have an assigned holdover endpoint or are to be delivered at the end of day are allowed to be built and released during holdover processing. Any attempts to manually build other transmissions causes an error to be displayed that states a holdover is in progress.
  2. All holdover eligible outbound batches (ICLs) for the requested business day are unmapped from the corresponding transactions and removed.
  3. All holdover eligible transactions are assigned a new holdover endpoint that contains a channel definition. The channel definition causes the outbound transmission to be delivered to the inbound Gateway landing zone. The holdover transactions include all eligible transactions, not just the transactions that were originally mapped to an outbound batch (ICL).
  4. Each holdover transaction is remapped to a new holdover outbound batch (ICL).
  5. The presentment availability days field for the transaction is increased, unless it is already set to 3.
  6. The outbound holdover transmissions are created without a deadline or cutoff value. The user must manually build and release the transmissions for them to be built and transmitted to the inbound landing zone.
  7. When the transmission is released, an RTE file is created that contains inbound nodes for holdover and useIncomingISN. These nodes are used by the inbound Gateway.