The following is an example of
an APERAK message being sent to acknowlegde the order number 652. The ORDERS message was
sent on the 25th of August. The parties who exchanged the ORDERS message are the buyer
with GLN 5412345000013 and the supplier with GLN 4012345500004.
UNH+ME00001+APERAK:D:01B:UN:EAN003' |
Message header |
BGM+305+10012+6' |
Application Error and Ackowledgement number is 10012. |
DTM+137:200208301200:203' |
The Application Error and Ackowledgement message was created at 12:00 on the 30th of
August 2002. |
RFF+ON:652' |
The message being acknowlegded is order number 652. |
DTM+171+20020825:102' |
The message being acknowledged was sent on the 25th of August 2002. |
NAD+BY+5412345000013::9' |
Buyer identified in the ORDERS message. |
NAD+SU+4012345500004::9' |
Supplier identified in the ORDERS message. |
UNT+8+ME00001' |
Total number of segments in the message equals 8. |
UNH+MD00001+APERAK:D:01B:UN:EAN003' |
Message header |
BGM+305+10015+27' |
Application Error and Acknowledgement number is 10015. |
DTM+137:200208231200:203' |
The Application Error and Acknowledgement message was created at 12:00 on the 23th of
August 2002. |
RFF+IV:2744' |
The message being acknowlegded is invoice number 2744. |
DTM+171+200208231100:203' |
The message being acknowledged was sent at 11:00 on the 23rd of August 2002. |
NAD+BY+5412345000013::9' |
Buyer identified in the INVOIC message. |
NAD+SU+4012345500004::9' |
Supplier identified in the INVOIC message. |
ERC+186::92' |
The buyer reports a duplicate invoice number using the bilaterally agreed code 186. |
UNT+9+ME00001' |
Total number of segments in the message equals 9. |