| Pos |
|
Tag |
Name |
S |
R |
Repr |
|
Notes |
| 010 |
|
|
| REPORT FUNCTION, CODED |
| Coded value identifying type of status or error report. |
|
M |
1 |
an..3 |
|
|
| 020 |
|
|
| STATUS INFORMATION |
| Reason for status or error report. |
|
C |
9 |
|
|
|
| |
|
|
| Status, coded |
| Code identifying the reason for the status or error report. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Status |
| Textual explanation of the reason for the status or error report. |
|
C |
1 |
an..70 |
|
|
| |
|
|
| Language, coded |
| Code identifying the language used. |
|
C |
1 |
an..3 |
|
|
| 030 |
|
|
| DIALOGUE REFERENCE |
| Unique reference for the dialogue between co-operating parties within the interactive EDI transaction. |
|
C |
1 |
|
|
|
| |
|
|
| Initiator control reference |
| A reference assigned by the dialogue initiator. |
|
M |
1 |
an..35 |
|
|
| |
|
|
| Initiator reference identification |
| Organisation code or name assigned by the party that initiated the transaction or dialogue. |
|
C |
1 |
an..35 |
|
|
| |
|
|
| Controlling agency, coded |
| Code identifying a controlling agency. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Responder control reference |
| A reference assigned by the dialogue responder. |
|
C |
1 |
an..35 |
|
|
| 040 |
|
|
| DATE AND/OR TIME OF INITIATION |
| Date and/or time of event initiation. |
|
C |
1 |
|
|
|
| |
|
|
| Event date |
| Date of event. |
|
C |
1 |
n..8 |
|
|
| |
|
|
| Event time |
| Time of event. |
|
C |
1 |
an..15 |
|
|
| |
|
|
| Time offset |
| UTC (Universal Co-ordinated Time) offset from event time. |
|
C |
1 |
n4 |
|
|
| 050 |
|
|
| INTERACTIVE MESSAGE REFERENCE NUMBER |
| Unique interactive message reference assigned by the sender. |
|
C |
1 |
an..35 |
|
1,5 |
| 060 |
|
|
| PACKAGE REFERENCE NUMBER |
| Unique package reference number assigned by the sender. |
|
C |
1 |
an..35 |
|
1,6 |
| 070 |
|
|
| SYNTAX ERROR, CODED |
| A code indicating the error detected. |
|
C |
1 |
an..3 |
|
2,3 |
| 080 |
|
|
| SEGMENT POSITION IN MESSAGE BODY |
| The numerical count position of a specific segment that is within the actual received message body. The numbering starts with, and includes, the UNH or the UIH segment as segment number 1. To identify a segment that contains an error, this is the numerical count position of that segment. To report that a segment is missing, this is the numerical count position of the last segment that was processed before 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. |
|
C |
1 |
n..6 |
|
2,3 |
| 090 |
|
|
| DATA ELEMENT IDENTIFICATION |
| Identification of the position for an erroneous data element. This can be the position of a stand-alone or composite data element in the definition of a segment or a component data element in the definition of a composite data element. |
|
C |
1 |
|
|
3 |
| |
|
|
| Erroneous data element position in segment |
| The numerical count position of the stand-alone or composite data element in error. The segment code and each following stand-alone or composite data element defined in the segment description shall cause the count to be incremented. The segment tag has position number 1. |
|
M |
1 |
n..3 |
|
|
| |
|
|
| Erroneous component data element position |
| 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. The count starts at 1. |
|
C |
1 |
n..3 |
|
|
| |
|
|
| Erroneous data element occurrence |
| The numerical occurrence of the repeating stand-alone or composite data element in error. Each occurrence (as indicated by the repetition separator) shall cause the count to be incremented. The count starts at 1. |
|
C |
1 |
n..6 |
|
|
