% Response.CharSet="utf-8" %>
|SOURCE:||Joint Transport Group (JM4)|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction
This message also occurs in the following versions of this standard:|
D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B
This specification provides the definition of the Application error and acknowledgement message (APERAK) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
The function of this message is:
The Application error and acknowledgement message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
A message being first controlled at system level (CONTRL) to detect syntax errors and to acknowledge its receipt is then transmitted to the application process to be processed.
If an error is detected at the application level, which prevents its complete processing, an APERAK message is sent to the original message issuer giving details of the error(s) encountered. If no error has been detected and when an acknowledgement is necessary (when no dedicated answer to the original message exists) an APERAK message is sent precising the reasons of acknowledgement. In case of application error, the APERAK message will need manual processing e.g. when the underlying reason is a programming error.
In case of acknowledgement the APERAK message may be automatically or manually processed at recipient's discretion.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Application error and acknowledgement message is APERAK.
Note: Application error and acknowledgement messages conforming to this document must contain the following data in segment UNH, composite S009:
A segment to indicate the type and function of the message and to transmit the identifying number.
A segment to specify related date/time.
A segment to specify free form or processable supplementary information related to the whole message. In computer-to-computer exchanges free form text will normally require the receiver to process this segment manually.
A segment to provide message control totals.
A group of segments to specify the document/message to which the current message relates, and related date and time.
A segment to indicate the reference number of the document/message.
A segment to specify the date and time of the referenced document/message.
A group of segments to specify the identifications of message sender and message receiver with their contacts and communication channels.
A segment to specify the identification of the message issuer and message receiver.
A segment to specify a person or department inside the party's organization, to which communication should be directed.
A segment to indicate communication channel type and number inside the party's organization, to which communication should be directed.
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.
A segment identifying the type of application error or acknowledgement within the referenced message. In case of an error, the error code may specify the error in detail (e.g. a measurement relating to a piece of equipment is wrong) or as a rough indication (e.g. a measurement is wrong).
A segment to provide explanation and/or supplementary information related to the specified application error or acknowledgement. For example, the explanation may provide exact details relating to a generic error code.
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.
A segment to provide a reference relating to the acknowledgement type or the specified error (e.g. functional entity reference such as equipment level).
A segment to provide additional details relating to the reference, e.g. the content of the wrong data (and its exact place in the message).
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
|BGM||Beginning of message|
|ERC||Application error information|
|NAD||Name and address|
|├─UNH Message header||×1||(M)|
|├─BGM Beginning of message||×1||(M)|
|├─FTX Free text||×9||(C)|
|├─CNT Control total||×9||(C)|
|├─Segment Group 1||×9||(C)|
|├─Segment Group 2||×9||(C)|
|│─├─NAD Name and address||×1||(M)|
|│─├─CTA Contact information||×9||(C)|
|│─└─COM Communication contact||×9||(C)|
|├─Segment Group 3||×99999||(C)|
|│─├─ERC Application error information||×1||(M)|
|│─├─FTX Free text||×1||(C)|
|│─└─Segment Group 4||×1||(C)|
|│───└─FTX Free text||×9||(C)|
|└─UNT Message trailer||×1||(M)|