EDIFACT UNH Message, outbound

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

Overview

EDIFACT UNH Message, 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 (from group or interchange): Interchange ID as it must appear on the transaction that is sent to this company or division. The valid value is 12 standard characters. Can be used as a wildcard.

Sender ID code qualifier (from group or interchange): Coded qualifier of the sender ID as it must appear on the group or interchange header segment that is sent to this company or division. The valid value is four standard characters.

Recipient ID (from group or interchange): Interchange ID as it must appear on the transaction that is received from this company or division. The valid value is 12 standard characters. Can be used as a wildcard.

Recipient ID code qualifier (from group or interchange): Coded qualifier of the recipient ID as it must appear on the group or interchange header segment that is sent to this company or division. The valid value is four standard characters.

(0065) Message type: Transaction message type as determined by the information type in the header of the message group, which includes the message or by the information type in the transaction message. Valid value is six standard characters. Can be used as a wildcard.
If you use AUTACK, create a separate AUTACK inbound transaction envelope with a message type of AUTACK so you can configure the trusted certificate that you want to use when you validate the digital signature.

(0052) Message version number: Version number of the standard message. The valid value is three standard characters. Can be used as a wildcard.

(0054) Message release number: The release number of the standard message. The valid value is three standard characters. Can be used as a wildcard.

(0051) Controlling agency, coded: Agency controlling the code that represents the name of the sending EDI service provider and relaying the message group on the sending side. The valid value is an alphanumeric code with three standard characters. Can be used as a wildcard.

(0057) Association assigned code: Assigned associated code for the agency that controls the name of the sending EDI service provider and relaying the message group on the sending side. The valid value is an alphanumeric code with six standard characters. Can be used as a wildcard.

(0113) Message type subfunction identification: Coded identifier of a subfunction of a message type. The valid value is six 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.

(0110) Code list directory version number: Previously defined version number of a code list to implement in this message. Valid value is numeric code with six limited standard characters. Can be used as a wildcard.

(0068) Common access reference: Key that is used for referencing related all subsequent transfers of data to the same business case or file. Can be used as a wildcard.

(0070) Sequence of transfers: Number that is assigned by the sender that indicates the transfer sequence of a message that is related to the same topic. The message might be an addition or a change to an earlier transfer that is related to the same topic. The valid value is two standard characters.

(0073) First and last transfer: The first and last message in a sequence of messages that is related to the same topic. Valid value is one standard character. Can be used as a wildcard.

(0115) Message subset identification: Coded identifier of a message subset by its identifier, version, release, and source. Valid value is 15 standard characters. Can be used as a wildcard.

(0116) Message subset version number: Version number of the message subset. The valid value is three standard characters. Can be used as a wildcard.

(0118) Message subset release number: Release number of the message subset. The valid value is three standard characters. Can be used as a wildcard.

(0051) Message subset controlling agency, coded: Agency controlling the code representing the name of the message subset. Valid value is alphanumeric code with three standard characters.

(0121) Message implementation guideline identification: Coded identifier of a message implementation guideline by its identifier, version, release, and source. The valid value is 14 standard characters. Can be used as a wildcard.

(0122) Message implementation guideline version number: Version number of a message implementation guideline. The valid value is three standard characters. Can be used as a wildcard.

(0124) Message implementation guideline release number: Release number of a message implementation guideline. The valid value is three standard characters. Can be used as a wildcard.

(0051) Message implementation controlling agency, coded: Agency controlling the code representing the name of the message implementer. Valid value is alphanumeric code with three standard characters. Can be used as a wildcard.

(0127) Scenario identification: Coded identifier of a scenario by its identifier, version, release, and source. Valid value is 14 standard characters. Can be used as a wildcard.

(0128) Scenario version number: Version number of a scenario. The valid value is three standard characters. Can be used as a wildcard.

(0130) Scenario release number: Release number of a scenario. The valid value is three standard characters. Can be used as a wildcard.

(0051) Message scenario controlling agency, coded: Agency controlling the code representing the message scenario. The valid value is alphanumeric code with three standard characters.

Next envelope: Search for and select the next envelope.

Note: When you set up your outbound processing, consider the following points.

If an envelope field contains a wildcard, you must supply a correlation value for it or the service halts with an error.
You can override wildcard values in an envelope by using the Correlation service to pass name/value pairs from the primary document to the EDI Encoder service.
If an envelope contains specific values in the Sender ID, Sender ID Qualifier, Receiver ID, or Receiver ID Qualifier field (that is, values other than a wildcard), the values passed from the Correlation service to the EDI Encoder service do not overwrite the values in the fields.
If you are using the same envelope for inbound processing and acknowledgments, supply the sender ID, receiver ID, and qualifiers in the envelope so that they are not overwritten by the correlation values.

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.

(0062) Local message reference number: Select or input the local message reference number. Accepts a numeric value.

Use correlation overrides: Select Always, Default, Never, or Wildcard (*) from the drop down.

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 will allow for options for the name option and primary name format to be chosen.

Validate transaction input: Select this check box to validate the input.

Validate transaction output: Select this check box to validate the output.

Compliance map: Select the specified map from the drop down list.