Identifying eligible transactions

A transaction is considered to be eligible for outbound processing if it meets all of the criteria in the following list:
  • If the business day is not in the holdover state, the transaction must not be an exception transaction. Examples of exception transactions are transactions that are marked as a suspect or flagged to be repaired.
  • The transaction must belong to a batch (ICL) that is ready for outbound processing. A batch (ICL) is typically configured to be ready for outbound processing by configuring event definitions in the Transaction Server Scheduler.xml file.

    For more information about configuring batches (ICLs) for outbound processing, see Transaction Server User's Guide.

  • The transaction must not be marked for deletion.
  • The transaction must not be identified as a control document.
  • The transaction must have a valid endpoint, and that endpoint must be associated to a building option. A building option is defined within Partner Profiles and identifies how a transaction is to be built for a specific endpoint. The endpoint must also be associated with a transmission definition.

    For more information about endpoints and building options, see Manage Building Options page.

  • The transaction must not already be associated to an outbound segment.
  • The transaction must not be previously unloaded from Distribution.