VDA Segment Purposes

The VDA segment purposes for delivery requests 4905/1 and 4915 are listed below.

VDA Segment Purpose for Delivery Request 4905/1

The VDA segment purposes for delivery request 4905/1 are as follows:

511:  Segment delivery request transmission dates.

This segment identifies the VDA message.  The message transmission number must be identical to the last delivery request number in the EDI Number file.

512:  Segment delivery request data for one item/delivery point relationship.

This segment specifies the delivery requests data for the item and delivery point for which the following segments are sent.  If your customer sends for different item/delivery point relationships on the same delivery request number, you should set the partial acquisition flag in Reference File category G26 to Yes.

513:  Synchronization, dispatch advice and release information.

This segment contains up to six releases and can only be sent once for one item/delivery point.

514:  Additional release information.

This segment contains up to thirteen releases and can be repeated many times for one item/delivery point.

517:  Container information.

This segment contains mandatory and optional information for LAB delivery requests.  The customer container number and the container volume are required, while the vendor container number is optional.

518:  Comments.

This segment contains up to three 40 character fields for general comments for LAB delivery requests.  The first field is required.

519:  Counter information.

This segment contains counter information for each VDA message.  If one counter differs from the internal counters, it indicates that the VDA message is corrupted and the system rejects the whole message.

VDA Segment Purpose for Detail Delivery Request 4915

To process detail delivery requests which can replace firmed demands, you must set the Authority to Modify flag in Reference File category G31 to Yes for each ship-to customer sending this type of delivery request message.

The VDA segment purposes for delivery request 4915 are as follows:

551:  Same purpose as 511.

552:  Segment detail delivery request date for one item/delivery point relationship (analogous to 512).

If your customer sends a detail delivery horizon date, the system closes all firmed demand from the date of the first release up to the horizon date.

553:  Segment detail delivery request synchronization data and dispatch advice data.

This segment contains dispatch advice information for three dispatch advices and can be repeated three times for each item/delivery point.  For each 553 segment, the system takes into account only the first dispatch advice information.

554:  Segment detail delivery request releases data.

This segment contains the release information (date, quantity, and time).

556:  Container information.

This segment contains mandatory and optional information for FAB detail delivery requests.  The customer container number and the container volume are required, while the vendor container number is optional.

557:  Comments.

This segment contains up to three 40 character fields for general comments for FAB detail delivery requests.  The first field is required.

559:  Same purpose as 519.