| # EDI business document Delivery The business document Delivery describes the shipment and receipt of ordered goods and includes the following EDI messages: ASN Advance Shipment Notification RDN Receipt Discrepancy Notification Complete the following steps to ship and receive ordered goods: After a sales order is released to Warehousing in the Release Sales Orders to Warehousing (tdsls4246m000) session, prepare the order for shipment to the purchasing company using the Generate Outbound Advice (whinh4201m000) and the Release Outbound Advice (whinh4202m000) sessions. Outbound advice offers information for moving goods from a warehouse storage location to a loading dock for shipment. Use the Freeze/Confirm Shipments/Loads (whinh4275m000) session, or the Confirm Outbound ASN (whinh4230m100) session to confirm shipments that will prepare Advance Shipment Notification (ASN) messages. Use the Shipment Notices (whinh3100m000) session to receive the advance shipment notice that is sent by the selling company. Use the Warehouse Receipt (whinh3512m000) session to record the quantity of goods received from the selling company. Confirm the receipt in the Warehouse Receipt (whinh3512m000) session. After you confirm a receipt or receipt line, ERP Enterprise sends a Receipt Discrepancy Notice (RDN) message to the selling company if the received quantity is not equal to the shipment notice line quantity. ERP Enterprise only sends a discrepancy notice if advanced shipment notices are used. Advance Shipment Notification (ASN) The delivery process is initiated when you do either of the following: Prepare the warehousing order for shipment to the purchasing company using the Generate Outbound Advice (whinh4201m000) and the Release Outbound Advice (whinh4202m000) sessions. Confirm the shipment in the Freeze/Confirm Shipments/Loads (whinh4275m000) session or the Confirm Outbound ASN (whinh4230m100) session to prepare Advance Shipment Notification (ASN) EDI messages. If the Generate ASNs Automatically check box is selected in the Inventory Handling Parameters (whinh0100m000) session, the Freeze/Confirm Shipments/Loads (whinh4275m000) session prepares the outgoing Advance Shipment Notification (ASN) message. If the Generate ASNs Automatically check box is cleared, you must use the Confirm Outbound ASN (whinh4230m100) session to prepare the outgoing Advance Shipment Notification (ASN) message. An Advance Shipment Notification (ASN) message can be sent using the Direct Network Communication (ecedi7205m000) session. A report is provided that shows which EDI messages have been generated. External EDI business partner messages are placed in the appl_from subdirectory under the directory specified for the network. Translation software will retrieve the message. Internal EDI business partner messages are stored in the appl_comm subdirectory. An advance shipment notice (ASN) is an unconfirmed receipt. When the ASN correctly reflects the contents of the shipment and is confirmed, the ASN becomes a receipt. The receipt process is faster when an ASN is received electronically, because data entry time is reduced and the chance of errors is also decreased. In the Warehouse Receipt (whinh3512m000) session, a selected shipment notice automatically populates the receipt data with the data from the shipment notice. To reprocess messages with errors Validation errors can appear when incoming messages are processed. These errors prevent the message from being updated into the ERP Enterprise application. The entire message is stored in the Saved Messages to be Received table and you can view and correct the message using the Saved Messages to be Received (ecedi7150m000) session. A unique batch number is assigned to each processing occurrence per each network. The Saved Messages to be Received (ecedi7150m000) session records processed incoming messages. Use this session to display received batch references created when incoming EDI messages are processed successfully or unsuccessfully. Use the Saved Messages to be Received (ecedi7150m000) session to view and correct data. If you choose to review the messages interactively, or if errors are encountered when message data is validated, an EDI message will not be processed. The unprocessed message is referred to as Saved Messages to Be Received. When you select a record, the saved message data details appear in the Saved Message Data to be Received (ecedi7151s000) session. After the message data has been corrected, the message must be approved before it can be reprocessed. Use the Approve Saved Messages to be Received (ecedi7250m000) session and the Process Saved Messages to be Received (ecedi7252m000) session to complete the steps required for reprocessing a message. After the saved message is successfully processed and updated into the ERP Enterprise application with the Process Saved Messages to be Received (ecedi7252m000) session, the saved message is automatically deleted from saved messages to be received. If you decide not to process the message, you can delete the message with the Print Saved Messages to be Received (ecedi7450m000) and/or Delete Saved Messages to be Received (ecedi7251m000) sessions. You can access both sessions from the Application menu in the Saved Messages to be Received (ecedi7150m000) session. Receipt Discrepancy Notification (RDN) Advance shipment notices can be used to populate receipt data in the Warehouse Receipt (whinh3512m000) session. If any discrepancy exists between the quantity shown on the shipment notice and the actual quantity received and recorded, the discrepancy is logged. After the receipt is confirmed, a Receipt Discrepancy Notification message (RDN) is prepared for EDI. The default conversion setup definition of the outgoing receipt discrepancy message includes the receipt discrepancy code. The code defines the type of discrepancy as follows: Quantity received greater than the quantity indicated on the shipment notice (quantity over). Quantity received less than the quantity indicated on the shipment notice (quantity short). Shipment notice not received prior to receipt of goods (No ASN). To indicate that the shipment notice was not received prior to the arrival of the goods, use the Shipment Notices (whinh3100m000) session to manually enter a shipment notice with zero quantities. The Direct Network Communication (ecedi7205m000) session will generate the outgoing Receipt Discrepancy Notification (RDN) message. A report lists the messages that were generated, and for external EDI, the outgoing message (ASCII) files are stored in the appl_from directory for the translation software. To receive the Receipt Discrepancy Notification (RDN) message, use the Direct Network Communication (ecedi7205m000) session. This session retrieves the RDN message from the appl_to directory, after the ASCII file is placed on the directory by translation software. The message indicates that a discrepancy was found between the quantity indicated on the Advance Shipment Notice (ASN) and the quantity actually received. The discrepancies between shipments and business partner receipts report compares the values in the discrepancy message with the shipment data and displays the differences and any text that is included. The EDI Information fields at the shipment header, and the shipment line’s text field are updated with the information in the discrepancy message. Related topics An overview of EDI business documents The shipment procedure How to receive goods Confirming receipts and receipt lines An overview of BEMIS |