Professional Documents
Culture Documents
06/07/2017
A UCS segment that identifies a transaction set and indicates the nature of
any error (mandatory)
Notes:
The CONTRL message contains several mandatory data elements that will be copied
from the received interchange. If the data element in the interchange is missing or is
syntactically invalid, a syntactically valid CONTRL message cannot be generated. The
error must then be reported by some means other than a CONTRL message.
SG Loops
The CONTRL functional ACK will be structured differently depending upon whether
the received interchange includes one or more groups. If the interchange includes a
group, the ACK will contain one UCF segment per group. Each UCF segment will
contain one UCM segment per message, and each UCM segment will include a series
of UCS and UCD segments in tandem.
The XML form of the ACK message will include an SG3Loop element that
encapsulates each UCF segment, an SG4Loop element that encapsulates each UCM
element, and an SG5Loop element that encapsulates each pair of UCS and UCD
elements. SG loop tags are not present in the native EDI format of the message.
If the interchange does not include a group, the ACK will not contain any UCF
segments. Instead it will include one UCM segment per message, and each UCM
segment will include a series of UCS and UCD segments in tandem.
The XML form of the ACK message will include an SG1Loop element that
encapsulates each UCM element, and an SG2Loop element that encapsulates each
pair of UCS and UCD elements. As with interchanges that include groups, the SG
tags are not present in the native format of the ACK.
Note:
By default and industry usage, SG1/SG4 loops are not expected for accepted
transaction sets. However, to support compliance with standards, you can force
generation of SG1/SG4 by selecting the Generate SG1/SG4 loop for accepted
transaction sets checkbox in the Acknowledgements page of the Agreement
Properties dialog box for an agreement between two business profiles (or the
Acknowledgements page of the EDI Settings tab for a business profile). If this
checkbox is selected, the receive pipeline will generate SG1/SG4 loops whether the
transaction set is accepted or rejected. Otherwise, these loops will be generated only
for erroneous transaction sets (for which UCM5 != 7).
Data Elements
The CONTRL functional ACK includes the following data elements:
Data
Name Usage
Element
Message reference
UNH1 -
number
The subcomponents are:
- 1 = CONTRL
Message identifier
UNH2 -2=4
subcomponents
-3=1
- 4 = UN
Interchange
UCI1 Mapped from the UNB5 field of the received message.
control number
Mapped from the UNB2 field of the received message.
Interchange The first subcomponent (identification) is mandatory.
UCI2
sender The second subcomponent (code qualifier) and the third
component (reverse routing address) are optional.
Data
Name Usage
Element
Mapped from the UNB3 field of the received message.
Interchange
UCI3 The first subcomponent (identification) is mandatory.
recipient
The second subcomponent (code qualifier) is optional.
The action codes are:
Syntax Error
UCD1 This data element has conditional optionality.
Coded