How To Fix /SCMB/ORDER373 - ASN Overdue exception created for &1 PO items

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/ORDER -

• Message number: 373

• Message text: ASN Overdue exception created for &1 PO items

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SCMB/ORDER373 - ASN Overdue exception created for &1 PO items ?

  The SAP error message /SCMB/ORDER373 ASN Overdue exception created for &1 PO items typically indicates that there are Advanced Shipping Notifications (ASNs) that are overdue for certain Purchase Order (PO) items. This message is part of the Supply Chain Management (SCM) module in SAP, specifically related to logistics and order management.
  Cause:
  
  Delayed Shipments: The supplier has not sent the ASN within the expected timeframe, leading to overdue notifications.
  Incorrect Dates: The expected delivery dates in the system may not align with the actual shipment dates.
  System Configuration: There may be issues with the configuration of the ASN process or the integration between the supplier's system and SAP.
  Communication Issues: There could be problems in the communication channels between the supplier and the SAP system, leading to missing or delayed ASNs.
  
  Solution:
  
  Check ASN Status: Verify the status of the ASNs for the affected PO items. This can be done through the relevant transaction codes in SAP (e.g., /SCMB/ASN).
  Contact Supplier: Reach out to the supplier to confirm the shipment status and request the overdue ASNs.
  Update Delivery Dates: If the delivery dates in the system are incorrect, update them to reflect the actual expected delivery dates.
  Review Configuration: Check the configuration settings for ASNs in the SAP system to ensure they are set up correctly.
  Monitor Communication: Ensure that there are no communication issues between the supplier's system and SAP. This may involve checking middleware or EDI settings if applicable.
  Create Manual ASN: If necessary, you can create a manual ASN in the system to acknowledge the shipment and update the status.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCMB/ASN, /SCMB/ORDER, and others that may help in monitoring and managing ASNs.
  Documentation: Refer to SAP documentation or help files for detailed guidance on managing ASNs and handling exceptions.
  User Roles: Ensure that users involved in the process have the appropriate roles and authorizations to view and manage ASNs and POs.
  Training: Consider training for users on the ASN process and exception handling to minimize future occurrences of overdue notifications.
  
  By addressing the underlying causes and following the suggested solutions, you can effectively manage the ASN overdue exceptions in SAP.