EDIFACT Inbound Syntax 4 UNG UNE Envelope Properties, Group Level

Note: An (*) asterisk indicates that a wildcard value can be used with that parameter (for mandatory fields, the wildcard value is an (*) asterisk). For Inbound envelopes, a wildcard value in the envelope matches any value in the input document, while an empty value in the envelope matches only an empty value in the input document. For Outbound envelopes, a wildcard value is equivalent to an empty value in the envelope.

The following table describes EDIFACT inbound Syntax 4 UNG UNE envelope properties at the group level:

Field
Description
* Sender ID
Interchange ID as it should appear on the message group header sent to this company or division. Valid value is 12 standard characters. Required.
* Sender Organization
The sender organization. Optional for envelopes managed by the Sterling B2B Integrator.
* Identification Code Qualifier (Sender ID)
Coded qualifier of the sender ID as it should appear on the message group header sent to this company or division. Valid value is four standard characters. Optional.
* Recipient ID
Interchange ID as it should appear on the message group header received from this company or division. Valid value is 12 standard characters. Required.
* Receiver Organization
The receiver organization. Optional for envelopes managed by the Sterling B2B Integrator.
* Identification Code Qualifier (Recipient ID)
Coded qualifier of the recipient ID as it should appear on the message group header received from this company or division. Valid value is four standard characters. Optional.
Use global control number
Whether this envelope definition must use a global control number to uniquely identify message group headers. No indicates that the envelope definition must use its own global control number. Required. Valid values are:
  • Yes (default)
  • Yes (and generate name from data)
  • No
Perform Control Number Sequence Checking
Compare the sequence of control numbers in the data with the Control Number parameter for this envelope. Required. Valid values are Yes and No (default).
Perform Duplicate Control Number Checking
Determine control number duplications. Required. Valid values are Yes and No (default).
Note: If this value is set to Yes and the Maximum age of Control Number History Records in days parameter is not given a value, entries are created in the TRANSACT_REGISTER table with a null value for the ARCHIVE_DATE. These entries are not purged automatically.
Maximum age of Control Number History Records in days
Maximum days to retain a history of control numbers to use for duplication determinations. Valid value is nine standard characters. Optional.
Retain Enclosing Envelope
Copy the envelope segments (UNB and UNZ) into each message extracted from the message group header. Required. Valid values are Yes and No.
Primary Name Format
Information to include when generating a name for a global number and finding the correct number to assign based on that name. Optional. Information includes:
  • Message Type
  • Message Version and Release Number
  • Test Indicator

Check each that you want to use in the format.

Use first backup name format
Whether to use the first backup name format (specified below). The default is selected (use the first backup name format).
Backup Name Format
Check boxes to indicate what information to include when generating a name for a global number and finding the correct number to assign based on that name. Optional. Information includes:
  • Message type
  • Message version and release number
  • Test Indicator

Check each that you want to use in the format.

Use second backup name format
Whether to use the second backup name format (specified below). The default is selected (use the second backup name format).
Backup Name Format
Check boxes to indicate what information to include when generating a name for a global number and finding the correct number to assign based on that name. Optional. Information includes:
  • Message type
  • Message version and release number
  • Test Indicator

Check each that you want to use in the format.

Handling of Non-Compliant Groups
Process to follow when non-compliant message group headers are encountered. Required. Valid values are:
  • Accept
  • Reject (default)
Business Process for Non-Compliant Documents
Business process to be used when non-compliant documents are encountered. Required.
Use Security
Turns on AUTACK security for the group. The AUTACK inbound transaction envelope will store the certificate reference or the way the certificate can be generated from the data used in validating the digital signature for the group.

Use previously checked in trusted certificates to verify a secured document transmission. Valid values are Yes and No (default). Required.

Note: This option must be set to Yes when using secure AUTACK messages in EDIFACT.
This is the AUTACK Group Envelope
Specify whether this envelope is the AUTACK group envelope. Valid values are Yes and No (default). Required.
Note: Only displayed if Use Security is set to Yes.