X12 ST Transaction, outbound
An outgoing envelope that contains the standard message that is surrounded by a header and trailer record.
Overview
X12 ST Transaction, outbound is an outgoing envelope that contains the standard message that is surrounded by a header and trailer record. An outbound envelope is, alternatively, referred to as "To EDI" envelope.
Key identifiers
When you edit an envelope configuration, the values for some of the key identifier fields, such as the Sender ID and Receiver ID fields, cannot be edited. Editing the fields might impact the associated routing rules. However, to edit the fields, you can contact IBM Support. For more information about which Key identifiers remain noneditable, see Noneditable fields.
- Sender ID
- The coded identifier of the company or division that sends the interchange. It can be up to 15 characters.
- Sender ID qualifier
- Qualifier used in envelope lookup by EDI Encoder.
- Receiver ID
- The coded identifier of the company or division that sends the interchange. It can be up to 15 characters.
- Receiver ID qualifier
- Qualifier used in envelope lookup by EDI Encoder.
- Transaction set ID code
- Code identifier of the transaction set. The valid value is three standard characters. Can be used as a wildcard.
- Acceptor lookup alias
- Identifying string that is used with the sender ID and the receiver ID to look up this envelope
with the EDI Encoder service. This alias associates a document with the service that it requires.
The valid value must be at least one limited standard character. Note: For 997 or 999 documents, the ALA format must be entered in the format as defined by the Inbound GS/GE envelope. For example, if an inbound 004030 document is received and the Acceptor lookup alias for generated 997/999s is set to use 99X_[group version] format, then the ALA must be entered as 99X_004030.
- Next envelope
- Envelope to apply after this envelope.
Envelope options
- Use global control number
-
- Select Yes from the drop down for envelope to use global control numbers.
- Select Yes and Generate to generate the name of the global control number based on the data. The Yes and Generate option uses the data to dictate which global control number to use. If you select this option, you must add a global control number and deploy it to the production environment. Only then you will be able to search for and select it in the field.
- Select No to use local control numbers. In this case, the Start value of local control number field populates. Input an integer value in this field.
- Use correlation overrides
- Select Always, Default, Never, or Wildcard (*) from the drop down.
- Implement convention reference
- Allows 1 to 35 characters from: A-Z, a-z, 0-9, <space>, - -, or * for wildcard.
- Hold locks until commit
-
Holding a lock until commit does not allow for any gaps in control numbers. However, selecting this checkbox slows down performance. Enable it only when you cannot have gaps in control numbers.
Compliance check options
- Map name mode
- Select the map name mode from the drop-down list. If generate from data is chosen as the map name mode, generate map name from data will be the next screen. This screen allows for options for the name option and primary name format to be chosen.
- Compliance map
- Select the specified map from the drop-down list.
- Validate transaction input
- Select this checkbox to validate the input.
- Validate transaction output
- Select this checkbox to validate the output.