WILLIAMS SYNCHRO 3/04/92
DSP01 DELIVERY REQUEST CHECK BATCH
Submit N
F2=Command F3=Exit
DELINS/VDA are the electronic delivery request from your customers that define the quantities of specific items they are ordering. The DELINS/VDA acquisition screens allow you to submit the request to start processing these electronic delivery requests. The acquisition program converts the electronic messages received into MAC-PAC readable form. It processes all the newly received messages as well as the messages in queue after they have been corrected or rejected (DELINS/VDA message maintenance).
SUBMIT
Required. Can be 'N' (process not requested) or 'Y' (process requested). Enter Y to confirm submission of request.
AUTOMATIC ACQUISITION OF DELIVERY REQUESTS
This batch process updates Synchro files as per the teletransmitted DELINS/VDA messages and/or the corrected messages in queue. The updated files are: GA210M1 (Delivery Request Headers), GA210M2 (Delivery Request Releases), GA210M3 (Delivery Request Comments) and GA120M2 (Item/Delivery Point Relationship for the Synchronization Data).
This process validates the messages received and, depending on the error level detected, displays a warning message or rejects the delivery request in error, which must then be reentered in the system after correction.
DELINS messages (Delivery Request or Delivery Instruction) are sent by the buyer to the vendor and convey the delivery schedule to be followed for one or several items. Each message includes one or more releases per item. The releases are expressed in quantities per period or per date.
The SY-GALIA translation software on, or compatible with, IBM-PC is used to receive DELINS messages. It generates internal files (on PC) on the basis of one record per segment of message received. The generated files are transferred on AS/400 and read sequentially per the delivery request automatic acquisition program. Each segment leads to the creation of a record organized according to a specific mask as per the type and mainly of variable length (DS variables). The record type is specified on each record, at the same place regardless of the type.
For each item/delivery point relationship associated to a blanket order referenced in a delivery request, the process considers the releases which already are in the system in order to take into account the 'new' releases in "Cancel and Replace" or "Current Actualization" mode, as per the delivery request type. Validation rules vary depending on the type of the delivery request (cancel and replace, current actualization).
An endorsement is associated to each of the acquired releases. The right endorsement is the one valid at the period start date of the release.
The following processes are executed for each segment according to the type:
- MID segment (Message Identification) This segment identifies the message (delivery request number).
- BDT segment (Buyer Identification) This segment identifies the buyer issuer of the delivery request. The system verifies that the issuer corresponds to an active ship-to customer in MAC-PAC and that the delivery request number is unique for this customer.
- CSG segment (Consignee) This segment identifies the final delivery point. It must correspond to an active delivery point defined in SYNCHRO.
- ARD segment (Item-Detail Line) This segment allows to determine the blanket order and the item and to check the existence of the item/ delivery point relationship. It also validates the endorsement for the item/ delivery point relationship. This segment indicates the unit of measure of the order (it is verified that it corresponds to the one defined in the endorsement).
The customer item number is the external reference number maintained in the endorsement.
- FTI segment (Free Text Item) Corresponds to the comments associated to the delivery request item/delivery point relationship.
- PDN segment (Recall of Last Deliveries) and DST segment (Synchronization Data) Up to three AVIEXP message numbers can be given.
- DEL segment (Details of Deliveries) This segment corresponds to a delivery request release. It is repeated for each release which belongs to the same item/delivery point relationship (ARD segment).
DEL segments of type = 3 are not taken into account. They are considered as synchronization data (backorder quantity).
For orders of type = 2 (current actualization), the new delivery request can change the releases which already exist from the first stated period start date. The added releases have an open status, while the replaced one are closed. Only the quantity and nature (confirmed or planned) can be changed. Furthermore, the existing confirmed releases cannot be actualized.
Releases validation rules are the same as the ones defined for the delivery request maintenance transaction.
When a blocking error is detected in a DELINS message, the message is put on hold in the error messages file and an error report in printed. The message can then be manually corrected (DELINS/VDA messages maintenance). It will be processed by default with the next automatic acquisition process; it will then be accepted if its rejection was due to errors in the database which have been corrected.
VDA messages (Delivery Request VDA 4901 and Detail Delivery Requests (4915) are converted into DELINS/VDA messages that are processed by the normal acquisition information flow. The buyer sends VDA messages to the sender. Each message includes one or more item and delivery point relationships. Those releases can be firmed or forecast releases.
The system sends firmed releases on a daily-time period and sends forecast releases in a week or month time period. You must maintain these time periods in Reference File category G77. To process the VDA release type "immediate requirement", this new release type was added to the acquisition process. In contrast to the DELINS/VDA order types "cancel and replace" and "current activation", the VDA messages will replace every release within the time period of one message for one item and delivery point relationship. This time period starts with the first release date end and ends with the date of the last release of one message for one item and delivery point relationship.
VDA Delivery Request 4905/1. The system executes the following processes for each segment of VDA delivery request 4905:
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 (GA115M).
512 - Segment Delivery Request data for one item and delivery point relationship. This segment specifies the delivery requests data and the item and the delivery point for following segments that are sent. If your customer sends for different item and delivery point relationships, you must set the Same Delivery Number and 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 and delivery point.
514 - Additional release information. This segment contains up to thirteen releases and can be repeated many times for one item and 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 counters for each VDA message. If one counter differs from the internal counters, the VDA message is corrupted and the whole message is rejected.
Detail Delivery Requests (VDA 4915). To process detail delivery requests that replace firmed demands, the Authority to Modify flag in Reference File category G31 must be set to "yes" for the Customer DELINS/VDA Acquisition screen (GA195S010). The following process are executed for each VDA 4915 segment:
551 - Segment detail delivery request transmission dates. The message transmission number must be identical to the last detail delivery request number in the EDI Number file.
552 - Segment detail delivery request data for one item and delivery point relationship (similar to 518). If your customer sends a detail delivery horizon date, the system closes all firmed demand releases from the date of the first release up to the horizon date.
553 - Segment detail delivery request synchronization and dispatch advice data. This segment contains dispatch advice information for three dispatch advices and can be repeated three times for each item and delivery point. The system acknowledges only the first dispatch advice for each 553 segment.
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 as segment 519.
The system handles errors for VDA messages in two ways:
o If the system cannot convert a VDA message because it doesn't conform to the VDA rules, the system rejects the whole VDA message, stores it in the VDA Messages in Error file (GA210HP), and prints an error report. The following types of errors can appear on the report:
- Invalid segment type;
- Invalid segment sequence;
- Different segment version;
- Segment counters wrong.
o If an error occurs and can be maintained by the DELINS DELINS/VDA Maintenance (GA215S01), the system stores the DELINS/VDA messages for one item and delivery point in the erroneous DELINS/VDA Messages File and prints an error report. You can then maintain the message manually and the next daily batch retains the message.
COMMAND KEYS
Enter - Validates the submission request.
F2 - Display a window where a fast path option, mnemonic or an OS/400 command (if the user is authorized) can be entered. Fast path allows the next menu selection to be made directly from this screen. When the window is displayed, pressing F3 will remove it.
F3 - Allows the user to exit the screen.
|