| EANCOM PART II | 1997-07-01 | |||
| DELFOR | - Delivery Schedule Message | VERSION 002 | ||
The following is an example of a product driven delivery schedule response message. The message is sent by the supplier identified by the EAN location number 4012345500004 to the buyer identified by the EAN location number 5412345000013. The date of the message is the 12th of January 1997.
The message accepts the previously sent product driven delivery schedule message identified by the number PDS416 sent the 10th of January of 1997. As the previous message is accepted only the mandatory segments, the identification of the schedule being accepted, and the parties needs to be communicated.
| UNH+ME000032+DELFOR:D:96A:UN:EAN002' | Message header |
| BGM+29E::9+ PDRS216+9+29’ | Product delivery schedule response number PDRS216 indicates that the previous message has been accepted without amendment |
| DTM+137:19970112:102' | Message date is the 12th of January 1997 |
| RFF+AAN:PDS416’ | Reference to delivery schedule being accepted number PDS416 |
| DTM+171:19970110:102’ | Date of delivery schedule being accepted is the 10th of January 1997 |
| NAD+BY+5412345000013::9' | The buyer is identified by the EAN location number5412345000013 |
| NAD+SU+4012345500004::9' | The supplier is identified by the EAN location number 4012345500004 |
| UNS+D' | Message header/detail separator |
| LIN+1’ | LIN segment inserted to avoid segment collision between two UNS segments |
| UNS+S' | Message detail/summary separator |
| UNT+11+ME000032' | Total number of 11 segments in the message |
Note:
The EDI interchange will include the UNB...UNZ segments and, if
applicable, the UNG...UNE segments (see Part 1, section 2.7)
(c) Copyright EAN 1997