X12 ST Transaction, inbound

An incoming envelope that contains the standard message that is surrounded by a header and trailer record.

Overview

X12 ST Transaction, inbound is an incoming envelope that contains the standard message that is surrounded by a header and trailer record. An inbound envelope is, alternatively, referred to as "From 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.

Receiver ID: The coded identifier of the company or division that sends the interchange. It can be up to 15 characters.

Transaction set ID code: Code identifier of the transaction set. The valid value is three standard characters. Can be used as a wildcard.

Group version release ID code: Version, release, and coded identifier of the industry for this interchange. The valid value is 12 standard characters. Can be used as a wildcard.

Test indicator

Operation mode to use for this envelope. The following are the valid values.

Test
Production
Information
Any indicator (wildcard). For example, *.

Envelope options

Implementation convention reference: Allows 1 to 35 characters from A-Z, a-z, 0-9, <space>, - -, or * for wildcard.

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.

Accept non-compliant transactions: Select this checkbox to accept noncompliant transactions.

Batch transactions within a functional group: Select this checkbox to batch your transactions within a functional group.

Perform duplicate control number checking: Select this checkbox to check for duplicates.

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.

Retain envelope: Select this checkbox to retain enclosing envelopes.

Translate and/or compliance check document: Select this checkbox for translation or compliance check document. If you select this checkbox, the next screen is the compliance check screen. The compliance check screen prompts you to select map name mode, select map name, accept noncompliant messages, and validate translation output. If generate from data is chosen as the map name mode, generate map name from data will be the next screen. This screen prompts for options for the name option and primary name format to be chosen.