EANCOM® 2002 S4 Edition 2016 Part II
CONTRL Syntax and service report message for batch EDI
5. Segments Layout
 
Previous Segment Segment number: 3 Legend Next Segment
SG1 - C 999999 -
UCM-SG2
A group of segments sent in response to a message in the subject interchange identified in the UCI segment. This segment group is only used if the subject interchange does not contain functional groups.
UCM - M 1 -
Message/package response
  Function:
  To identify a message or package in the subject interchange, and to indicate that message's or package's acknowledgement or rejection (action taken), and to identify any error related to the UNH, UNT, UNO, and UNP segments. It can also identify errors related to the USA, USC, USD, USH, USR, UST, or USU security segments when they appear at the message or package level.

Dependency Notes:
1. D1(010,070) One and only one
2. D2(010,020) All or none
3. D2(070,080) All or none
4. D5(050,040) If first, then all
5. D5(060,050,040) If first, then all
6. D5(090,050,040,100) If first, then all
7. D5(100,090,050,040) If first, then all

Notes:
8. 0135, may only contain the values UNH, UNT, UNO, UNP, USA, USC, USD, USH, USR, UST, or USU.
9. This data element shall be present when reporting an error in a security segment.
 
EDIFACT
EAN *
Description
0062
Message reference number
C an..14
R    
S009
MESSAGE IDENTIFIER
C
R    
0065
Message type
M an..6
M    
0052
Message version number
M an..3
M    
0054
Message release number
M an..3
M    
0051
Controlling agency, coded
M an..3
M    
0057
Association assigned code
C an..6
R    
0110
Code list directory version number
C an..6
O    
0113
Message type sub-function identification
C an..6
N    
0083
Action, coded
M an..3
M  
4 = This level and all lower levels rejected
7 = This level acknowledged, next lower level acknowledged if not explicitly rejected
0085
Syntax error, coded
C an..3
D *
General explanations
3 = Message version/release not supported (GS1 Temporary Code)
12 = Invalid value
13 = Missing
14 = Value not supported in this position
15 = Not supported in this position
16 = Too many constituents
17 = No agreement
18 = Unspecified error
21 = Invalid character(s)
22 = Invalid service character(s)
23 = Unknown interchange sender
25 = Test indicator not supported
26 = Duplicate detected
27 = Security function not supported
28 = References do not match
29 = Control count does not match number of instances received
30 = Functional groups and messages mixed
31 = More than one message type in group
34 = Nesting indicator not allowed
37 = Invalid type of character(s)
39 = Data element too long
40 = Data element too short
0135
Service segment tag, coded
C an..3
D    
S011
DATA ELEMENT IDENTIFICATION
C
D    
0098
Erroneous data element position in segment
M n..3
M  
The numerical count position of the simple or composite data element in error. The segment tag and each simple and composite data element position number within the segment.
0104
Erroneous component data element position
C n..3
O  
The numerical count position of the component data element in error. Each component data element position defined in the composite data element description shall cause the count to be incremented.
0136
Erroneous data element occurrence
C n..6
N    
0800
Package reference number
C an..35
N    
S020
REFERENCE IDENTIFICATION
C
N    
0813
Reference qualifier
M an..3
     
0802
Reference identification number
M an..35
     
0534
Security reference number
C an..14
N    
0138
Security segment position
C n..6
N    
Segment Notes:
This segment is used to identify specific messages within the interchange identified in the previous UCI segment.
This segment is similar in layout to the UNH segment (data elements 0062 to 0057 inclusive) and should contain the same information as that contained in the UNH segment.
DE's 0083 and 0085: These data elements are used to indicate the status of the message and in cases where errors are present to identify the error.
DE's 0135, S011: If there are errors in the UNH, UNT or the security service  segments at message level the segment in question and the position of the error in the segment may be identified in these data elements.

Example:
UCM+ME002341+INVOIC:D:01B:UN:EAN010+4+13+UNH+2'
Message reference ME002341, an INVOIC message, has been rejected because the mandatory data element 0062 has not been included in the UNH segment position 2.

Dependency Notes:
Data elements 0085, 0135 and S011 are only used when errors are being reported.
Previous Segment Next Segment
© Copyright GS1 Edition 2016