|
- |
C |
1 |
- |
Service string advice |
|
The service string advice shall begin with the upper case characters UNA immediately followed by six characters in the order shown below. The same character shall not be used in more than one position of the UNA. |
|
|
|
- |
M |
1 |
- |
Interchange header |
|
This segment is used to envelope the interchange, as well as to identify both, the party to whom the interchange is sent and the party who has sent the interchange. The principle of the UNB segment is the same as a physical envelope which covers one or more letters or documents, and which details, both the address where delivery is to take place and the address from where the envelope has come. |
|
|
Application error and acknowledgement message Heading Section
|
|
- |
M |
1 |
- |
Message header |
|
This segment is used to head, identify and specify a message. |
|
|
|
- |
M |
1 |
- |
Beginning of message |
|
This segment is used to indicate the type and function of a message and to transmit the identifying number. |
|
|
|
- |
C |
9 |
- |
Date/time/period |
|
This segment is used to specify the date of the message. |
|
|
|
- |
C |
1 |
- |
DOC-DTM |
|
A segment group to provide information on the document being acknowledged. |
|
|
|
- |
M |
99 |
- |
Document/message details |
|
To identify documents and details directly related to it. |
|
|
|
- |
R |
99 |
- |
Date/time/period |
|
To specify date, and/or time, or period. |
|
|
|
- |
C |
9 |
- |
RFF-DTM |
|
A group of segments to specify the document/message to which the current message relates, and related date and time. |
|
|
|
- |
M |
1 |
- |
Reference |
|
This segment is used to specify reference numbers related to the message which is being acknowledged. |
|
|
|
- |
C |
9 |
- |
Date/time/period |
|
This segment is used to specify dates or periods relating to the previous RFF segment. |
|
|
|
- |
C |
9 |
- |
NAD |
|
A group of segments to specify the identifications of message sender and message receiver. |
|
|
|
- |
M |
1 |
- |
Name and address |
|
This segment is used to identify the parties who exchanged the message which is being acknowlegded. |
|
|
Application error and acknowledgement message Detail Section
|
|
- |
C |
99999 |
- |
ERC-FTX-SG5 |
|
A group of segments to identify the application error(s) within a specified received message and to give specific details related to the error type or to precise the type of acknowledgement. |
|
|
|
- |
M |
1 |
- |
Application error information |
|
This segment is used to identify the type of application error in the previously sent message. |
|
|
|
- |
C |
1 |
- |
Free text |
|
This segment is used to provide free text information related to the application error. |
|
|
|
- |
C |
9 |
- |
RFF-FTX |
|
A group of segments to specify the functional entity reference (e.g. goods item level, equipment level) relating to the specified error; further details can be added to identify the error more precisely. |
|
|
|
- |
M |
1 |
- |
Reference |
|
This segment is used to specify reference numbers related to the message which is being acknowledged. |
|
|
|
- |
C |
9 |
- |
Free text |
|
This segment is used to provide free text information related to the application error. |
|
|
Application error and acknowledgement message Summary Section
|
|
- |
M |
1 |
- |
Message trailer |
|
This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message. |
|
|
|
- |
M |
1 |
- |
Interchange trailer |
|
This segment is used to provide the trailer of an interchange. |
|
|