How To Fix /SCMB/ORDER372 - &1 PO items were evaluated for "ASN Overdue" exceptions

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/ORDER -

• Message number: 372

• Message text: &1 PO items were evaluated for "ASN Overdue" exceptions

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/ORDER372 - &1 PO items were evaluated for "ASN Overdue" exceptions ?

  The SAP error message /SCMB/ORDER372 indicates that certain Purchase Order (PO) items have been evaluated for "ASN Overdue" exceptions. This typically occurs in the context of Supply Chain Management (SCM) and can be related to the Advanced Shipping Notification (ASN) process.
  Cause:
  The error message usually arises due to the following reasons:
  
  ASN Not Received: The system expects an ASN for the PO items, but it has not been received within the expected timeframe.
  Delay in Delivery: The delivery of goods is delayed beyond the expected delivery date, leading to overdue ASN exceptions.
  Incorrect Configuration: There may be configuration issues in the SCM module that affect how ASNs are processed and evaluated.
  Data Inconsistencies: There could be inconsistencies in the data related to the PO or ASN, such as mismatched quantities or incorrect dates.
  
  Solution:
  To resolve the issue, you can take the following steps:
  
  Check ASN Status: Verify if the ASN has been created and sent for the relevant PO items. If not, ensure that the ASN is generated and sent to the system.
  Review Delivery Dates: Check the expected delivery dates for the PO items and compare them with the actual delivery dates. If the delivery is delayed, communicate with the supplier to get an update.
  Update PO Information: If there are changes in the delivery schedule, update the PO information accordingly in the system.
  Configuration Review: Review the configuration settings in the SCM module related to ASN processing to ensure they are set up correctly.
  Data Consistency Check: Perform a data consistency check to identify any discrepancies between the PO and ASN data. Correct any inconsistencies found.
  Monitor Exception Handling: Use the exception handling tools in SAP SCM to monitor and manage ASN overdue exceptions effectively.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCMB/ORDER for order management and /SCMB/ASN for ASN processing.
  Documentation: Refer to SAP Help documentation for detailed information on handling ASNs and exceptions in SCM.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to address the /SCMB/ORDER372 error and manage ASN overdue exceptions effectively.