Delivery schedule message
5. Segments Layout
 
Segment number:
4
-
M
1
-
 
Function:
 
To indicate the type and function of a message and to transmit the identifying number.
 
EDIFACT
EAN
*
Description
C002
DOCUMENT/MESSAGE NAME
C
R
   
Document name code
C
an..3
R
 
=
Delivery forecast
=
Delivery schedule response
=
Delivery schedule
Code list identification code
C
an..17
N
   
Code list responsible agency code
C
an..3
N
   
1000
Document name
C
an..35
O
   
C106
DOCUMENT/MESSAGE IDENTIFICATION
C
R
   
1004
Document identifier
C
an..35
R
 
Delivery schedule number assigned by the sender.
For global unique identification of documents Global Document Type Identifier (GDTI) is available.
1056
Version identifier
C
an..9
N
   
1060
Revision identifier
C
an..6
N
   
Message function code
C
an..3
R
*
=
Cancellation
=
Change
=
Duplicate
=
Original
=
Not accepted
=
Accepted without amendment
=
Copy
=
Confirmation via specific means
The message function, coded is a critical data element in this segment. It applies to all data indicated in the message. Code values 27, and 29 are used only when the message is sent as delivery schedule response. The following definitions apply for the restricted codes:
1= Cancellation - A cancellation of a previously sent delivery schedule. The previous delivery schedule number is specified in the RFF segment.
4 = Change - A change to a previously sent delivery schedule. Only the area's changing need to be re-transmitted. The previous delivery schedule number is specified in the RFF segment.
7 = Duplicate - A re-transmission involving the same parties, on the specific request of the receiver.
9 = Original - An original transmission of a delivery schedule.
27 = Not accepted - Message to inform that the referenced message is not accepted by the recipient. The previous delivery schedule number is specified in the RFF segment.
29 = Accepted without amendment - Referenced message is entirely accepted. The previous delivery schedule number is specified in the RFF segment.
31 = Copy - A copy of a delivery schedule for a third party for information purposes.
42 = Confirmation via specific means - A confirmation of a previous delivery schedule sent by means other than EDI, e.g., Fax.
Response type code
C
an..3
D
*
=
Message acknowledgement
=
Acknowledge - with detail and change
=
Acknowledge only changes
=
No acknowledgement needed
The data element is used if the delivery schedule issuer wishes to explicitly indicate whether an acknowledgement is required or not.
Segment Notes:
This segment is used to indicate the type and function of a message and to transmit the identifying number.

Example:
BGM+241+LDS562+9'
Delivery schedule number LDS562

BGM+291+PDS416+9'
Delivery schedule response, number PDS416.
© Copyright GS1
Edition 2016