EDIFACT UNH Message, inbound

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

Overview

EDIFACT UNH Message, 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
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
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. The 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
The 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.
(0113) Message type sub-function ID
Allows 1 to 6 characters from A-Z, a-z, 0-9, <space>, - -, or * for wildcard.
(0051) Controlling agency, coded
Agency that controls 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.
(0035) Test indicator
Operation mode to use for this envelope. The following are the valid values.
  • None (default)
  • Test
  • Syntax Only Test
  • Echo Request
  • Echo Response
  • Any Indicator (wildcard)
Note: When you set up envelopes with wildcards, consider the following points.
  • The De-enveloping service selects the envelope that matches the EDI data most closely. For example, if an envelope has the same Transaction ID as the incoming data, and another envelope has wildcards in all mandatory fields, the envelope with the matching Transaction ID is used.
  • Sender ID and Receiver ID have priority over other EDI fields. For example, two envelopes are found that have a field that matches one EDI field from the data. One envelope matches the value in the Receiver ID field from the data, the other matches the Transaction ID field. The envelope that has the matching the receiver ID is selected by the service and used for processing.
  • If no envelopes are found that have an exact match to fields in the EDI data, and an envelope with wildcards does exist, the envelope with wildcards is used.
  • If multiple envelopes have the same matching information (for example, two envelopes match the sender ID and receiver ID exactly) the service ends with an error.
  • The wildcard character is an “all or nothing” parameter. That is, if you use asterisk, you cannot enter other characters in the field with it. For example, you cannot enter Me* to match MeaslesAnimalHaven and Medeira Foods.

Envelope options

Accept non-compliant groups
Select this checkbox to accept noncompliant groups.
Batch messages received within a functional group.
Select this checkbox to batch messages that are received within a functional group.
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.

Perform duplicate control number checking
Select this checkbox to check for duplicates.
Retain enclosing envelope
Select this checkbox to retain enclosing envelopes.
Translate and/or compliance check document
Select this checkbox to translate or compliance check document. If translate or compliance check document is selected, the next screen will be a 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 generating 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.