|
|
|
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. |
|
|
|
|
|
A group of segments sent in response to a segment containing one or more errors, and which was part of the message identified by the UCM segment in segment group 1. |
|
|
|
|
|
|
Function: |
|
To identify either a segment containing an error or a missing segment, and to identify any error related to the complete segment. |
|
| |
|
EAN
|
*
|
|
|
|
|
Segment position in message |
|
|
M
|
|
|
The numerical count position of a specific segment that is within the received message. The numbering starts with, and includes, the UNH segment as segment number 1. To identify a segment that contains an error, use the numerical count position of that segment. To report that a segment that is missing use the numerical count position of the last segment that was processed prior to the position where the missing segment was expected to be. A missing segment group is denoted by identifying the first segment in the group as missing. |
|
|
|
|
|
O
|
*
|
|
|
= |
|
Data segment missing/invalid (GS1 Temporary Code) |
|
|
= |
|
Invalid value |
|
|
= |
|
Missing |
|
|
= |
|
Value not supported in this position |
|
|
= |
|
Not supported in this position |
|
|
= |
|
Too many constituents |
|
|
= |
|
Unspecified error |
|
|
= |
|
Invalid character(s) |
|
|
= |
|
Invalid service character(s) |
|
|
= |
|
Security function not supported |
|
|
= |
|
Nesting indicator not allowed |
|
|
= |
|
Too many segment repetitions |
|
|
= |
|
Too many segment group repetitions |
|
This data element may be used to identify an error related to the complete segment. |
|
|
Segment Notes: |
|
This segment is used to identify the position of a segment within a message. This segment is only used to identify segments within the message identified in the UCM segment which have errors.
Example:
UCS+3+12' |
|
