|
|
| Function: |
| To indicate the type and function of a message and to transmit the identifying number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Document/message name, coded |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code list responsible agency, coded |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Delivery schedule number assigned by the sender. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Segment Notes: |
This segment is used to indicate the type and function of a message and to transmit the identifying number.
DE 1001: In the Delivery Schedule message there are two possible approaches to using the message (detailed in section 1). As the two types of approach may not be mixed in the same interchange it is necessary to positively state which approach is being used by means of the Document/message name, coded data element.
DE 1225: 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.
Example :
BGM+41E::9+LDS562+9'
Indicates a location driven delivery schedule.
BGM+42E::9+PDS416+42'
Indicates a product driven delivery schedule being sent as confirmation to a schedule previously sent by means other than EDI.
Dependency Notes :
DE 4343: The data element is used if the delivery schedule issuer wishes to explicitly indicate whether an acknowledgement is required or not. |
|