EANCOM® 2002 S3 Part II
DELFOR Delivery schedule message
6. Examples

Example of a Location Driven Delivery Schedule

The following is an example of a location driven delivery schedule message. The message is sent by the buyer identified by GLN 5412345000013 to a supplier identified by GLN 4012345500004. The date of the message is the 10th of January 2002.

The delivery is requested for the 20th of January 2002 at 12:30pm. Delivery is requested for two delivery parties identified with both the delivery parties receiving the deliveries by road using trucks.

The first delivery location is identified by GLN 5412345000013 and requests a delivery of 4000 units of the product identified by GTIN 5412345111115.

The second delivery location is identified by GLN 5412345000020. The product for delivery is identified by GTIN 5412345123453 and is requesting 8800 units of the product.
UNH+ME000001+DELFOR:D:01B:UN:EAN004' Message header
BGM+241+LDS562+9’ Delivery schedule number LDS562
DTM+137:20020110:102' Document date 10th of January 2002
DTM+2:200201401230:203' Requested delivery date is at 12:30pm on the 20th of January 2002
NAD+BY+5412345000013::9' The buyer is identified by GLN 5412345000013
NAD+SU+4012345500004::9' The supplier is identified by GLN 4012345500004
GIS+94' Location driven schedule
NAD+DP+5412345000013::9' Delivery party is identified by GLN 5412345000013
TDT+20++30+31' The main carriage transport to be used will be a truck
LIN+1++5412345111115:SRV' The first product in the schedule is identified by GTIN 5412345111115
SCC+1' Firm schedule
QTY+113:4000' The quantity to be delivered is 4000 units
GIS+94' Location driven schedule
NAD+DP+5412345000020::9' Delivery party is identified by GLN 5412345000020
TDT+20++30+31' The main carriage transport to be used will be a truck
LIN+2++5412345123453:SRV' The second product in the schedule is identified by GTIN 5412345123453
SCC+1' Firm schedule
QTY+113:8800' The quantity to be delivered is 8800 units
UNT+19+ME000001' Total of 19 segments in the message

Example of a Product Driven Delivery Schedule

The following is an example of a product driven delivery schedule message. The message is sent by the buyer identified by GLN 5412345000013 to a supplier identified by GLN 4012345500004. The date of the message is the 10th of January 2002. The message is sent as a confirmation to previously agreed schedule sent by means other than EDI. No acknowledgment is required for the transmission.

The delivery is requested for the 20th of January 2002 at 12:30pm. Delivery is requested for one product to two delivery parties.

The product identified by GTIN 5412345111115. The delivery locations are identified by GLNs 5412345000051 and 5412345000068 and requests a delivery of 350 units to each delivery location.
UNH+ME000011+DELFOR:D:01B:UN:EAN004' Message header
BGM+241+PDS416+42+NA' Delivery schedule number PDS416 is a confirmation of a schedule sent previously by means other than EDI. No acknowledgment to the message is needed.
DTM+137:20020110:102' Message date is the 10th of January 2002
DTM+2:200201401230:203' Delivery is requested for 12:30pm on the 20th of January 2002
NAD+BY+5412345000013::9' The buyer is identified by GLN 5412345000013
NAD+SU+4012345500004::9' The supplier is identified by GLN 4012345500004
GIS+95' Product driven delivery schedule
LIN+1++5412345111115:SRV' The first line item in the schedule is identified by GTIN 5412345111115
SCC+1' Firm schedule
QTY+113:700' Total quantity to be delivered is 700 units
NAD+DP+5412345000051::9' First delivery party is identified by GLN 5412345000051
SCC+1' Firm schedule
QTY+113:350' Quantity to be delivered is 350 units
NAD+DP+5412345000068::9' Second delivery party is identified by GLN 5412345000068
SCC+1' Firm schedule
QTY+113:350' Quantity to be delivered is 350 units
UNT+17+ME000011' Total number of 17 segments in the message

Example of a Product Driven Delivery Schedule Response

The following is an example of a product driven delivery schedule response message. The message is sent by the supplier identified by GLN 4012345500004 to the buyer identified by GLN 5412345000013. The date of the message is the 12th of January 2002.

The message accepts the previously sent product driven delivery schedule message identified by the number PDS416 sent the 10th of January of 2002. 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:01B:UN:EAN004' Message header
BGM+291+PDRS216+29’ Delivery schedule response number PDRS216 indicates that the previous message has been accepted without amendment
DTM+137:20020112:102' Message date is the 12th of January 2002
RFF+AAN:PDS416’ Reference to delivery schedule being accepted number PDS416
DTM+171:20020110:102’ Date of delivery schedule being accepted is the 10th of January 2002
NAD+BY+5412345000013::9' The buyer is identified by GLN 5412345000013
NAD+SU+4012345500004::9' The supplier is identified by GLN 4012345500004
UNT+8+ME000032' Total number of segments in the message equals 8

Note:
The EDI interchange will include the UNB..UNZ segments and, if applicable, the UNG..UNE segments. (See part 1 section 5.7).

© Copyright GS1 Edition 2016 Upd. 2021