How To Fix /SCMB/ORDER357 - Overdue Confirmation exceptions of purchase order items were updated

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/ORDER -

• Message number: 357

• Message text: Overdue Confirmation exceptions of purchase order items were updated

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/ORDER357 - Overdue Confirmation exceptions of purchase order items were updated ?

  The SAP error message /SCMB/ORDER357 indicates that there are overdue confirmation exceptions related to purchase order items that have been updated. This message typically arises in the context of Supply Chain Management (SCM) and can be associated with issues in the order confirmation process.
  Cause:
  
  Overdue Confirmations: The primary cause of this error is that the system has detected that certain purchase order items have not been confirmed within the expected timeframe. This could be due to delays in the supply chain, issues with the vendor, or internal processing delays.
  Configuration Issues: There may be configuration settings in the SCM module that are not aligned with the business processes, leading to exceptions being raised.
  Data Inconsistencies: Inconsistencies in master data (like vendor information, material master, etc.) or transactional data can also lead to this error.
  System Settings: The system settings for handling confirmations and exceptions may not be properly configured, leading to the generation of this error message.
  
  Solution:
  
  Review Overdue Confirmations: Check the purchase orders that are generating the error. Identify which items are overdue and investigate the reasons for the delay. This may involve communication with suppliers or internal stakeholders.
  Update Confirmations: If the overdue confirmations are valid, update the confirmations in the system to reflect the current status of the purchase order items.
  Adjust Configuration: If the issue is related to configuration, review the settings in the SCM module to ensure they align with your business processes. This may involve working with your SAP Basis or SCM consultant.
  Data Validation: Ensure that all relevant master data and transactional data are accurate and up to date. Correct any inconsistencies that may be causing the error.
  Monitor and Report: Set up monitoring for overdue confirmations and create reports to track the status of purchase orders and confirmations. This can help in proactively managing exceptions in the future.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like ME23N (Display Purchase Order) or SCMB/ORDER to analyze the order details and confirmation statuses.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on handling this error.
  Documentation: Refer to SAP documentation for the SCM module to understand the configuration settings related to order confirmations and exception handling.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the /SCMB/ORDER357 error and implement a solution to resolve it.