| # EDI business document Error Handling This business document Error Handling describes sending, receiving, and processing Error Notification messages. Sending Error Notification (824/APERAK) to supplier The EDI Messages Supported by Business Partner (ecedi0511m000) session includes the Automatically Prepare Error Notification check box. If both trading partners select this check box, and an error exists in the received Shipment Notice (856), an outgoing Error Notification (824) message will be prepared. To manually prepare the Error Notification message, you must run the Print Received Message Errors (ecedi7451m000) session, and select the Prepare Error Notification check box. The error notification can be prepared for any erroneous message received, but is of particular use for shipment notices with errors received in conjunction with supply chain environments. Use the Direct Network Communication (ecedi7205m000) session to generate the outgoing message. A report listing the messages that were generated will be created. Receiving Error Notification (824/APERAK) from customer After you receive an Error Notification (824/APERAK) from your customer (ship-to business partner), and the message (ASCII) files have been placed in the appropriate appl_to directory by the translation/communication software, use the Direct Network Communication (ecedi7205m000) session to receive the Error Notification message. An incoming Error Notification is associated with a shipment for which an invalid shipment notice was originally sent, and reports application errors that occurred when your business partner tried to process the previously sent shipment notice. When the Error Notification is received, the following occurs: The status of the shipment for which the Error Notification was received, is set to Disapproved. The Remarks in Copied Message report is generated, showing the shipment notice number against which the Error Notification message was received, and any related and pertinent remarks. Optionally, the EDI Information field on the shipment header may be updated with the contents of the Error Notification message. The shipment notice referenced in the received Error Notification message, is automatically prepared for EDI transmission (856/DESADV out). As with all prepared outgoing messages, you can verify that the outgoing message was prepared for EDI using the Messages to be Generated (ecedi7100m000) session. If you do not want the message to be generated the next time the Direct Network Communication (ecedi7205m000) session is run, you can delete the message from this session. Resending canceling and corrected shipment notices in response to received Error Notifications If you wish to send a canceling shipment notice to your customer, and if the network is set up to generate messages upon Direct Network Communication, run the Direct Network Communication (ecedi7205m000) session. Otherwise, run the Generate EDI Messages (ecedi7201m000) session to manually generate the outgoing message. When the outgoing canceling shipment notice is generated, the shipment’s EDI status is Modify, indicating that the shipment should be modified to correct the erroneous data, and resent to your business partner. Note In order to support the requirements of some EDI standards, ERP Enterprise EDI supports the transmission of two kinds of shipment notices: A canceling shipment notice A canceling shipment notice is intended to cancel a previously sent erroneous shipment notice. To utilize this feature, use the Conversion of Shipment Status Codes (out) (ecedi4180m000) session to define codes to include in the message indicating if the shipment notice is an original or a canceling message. An original shipment notice If the shipment’s EDI status is Confirmed, the shipment notice is considered to be an original message. If the shipment’s EDI status is Disapproved, the shipment notice is considered to be a canceling message. Optionally, if the shipment’s EDI status is Modify, you may correct the reported errors by correcting the shipment’s date/time, quantity or weight and any other EDI data included on the original shipment notice, and resend the corrected shipment notice to your business partner. To resend the corrected shipment notice, use the Confirm Outbound ASN (whinh4230m100) session to prepare the corrected shipment notice (856/DESADV) for transmission; preparing the outgoing shipment notice sets the shipment’s EDI status to Confirmed. If the network is set up to generate messages upon Direct Network Communication, run the Direct Network Communication (ecedi7205m000) session. Otherwise, run the Generate EDI Messages (ecedi7201m000) session to manually generate the outgoing message. For external EDI, the outgoing message (ASCII) files are placed in the appl_from directory, under the network’s directory, from which the translation/communication software will retrieve them. Related topics An overview of BEMIS An overview of EDI business documents |