|
|
|
| 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. |
|
|
|
|
|
| |
Function: |
| |
To identify a message in the subject interchange, and to indicate that message's acknowledgement or rejection (action taken), and to identify any error related to the UNH and UNT segments. |
|
| |
|
EAN |
* |
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
Association assigned code |
|
|
R |
|
|
|
|
|
|
M |
|
| 4 |
|
= |
This level and all lower levels rejected |
| 7 |
|
= |
This level acknowledged, next lower level acknowledged if not explicitly rejected |
|
|
|
|
|
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 |
|
|
|
|
Service segment tag, coded |
|
|
D |
|
|
|
|
|
DATA ELEMENT IDENTIFICATION |
|
|
D |
|
|
|
|
|
Erroneous data element position in segment |
|
|
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. |
|
|
|
|
Erroneous component data element position |
|
|
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. |
|
|
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 0013, S011: If there are errors in the UNH or UNT segments 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, 0013 and S011 are only used when errors are being reported. |
|
