How To Fix /SCMB/ORDER345 - Order &1, item &2: Request schedule lines aggregated during item split

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/ORDER -

• Message number: 345

• Message text: Order &1, item &2: Request schedule lines aggregated during item split

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/ORDER345 - Order &1, item &2: Request schedule lines aggregated during item split ?

  The SAP error message /SCMB/ORDER345 indicates that there is an issue with the scheduling of order items in the Supply Chain Management (SCM) module. Specifically, this message is triggered when request schedule lines are aggregated during an item split, which can occur in various scenarios, such as when an order item is split due to changes in quantity, delivery dates, or other parameters.
  Cause:
  
  Item Split: The error typically arises when an order item is split into multiple items, and the system attempts to aggregate the request schedule lines for these items. This can happen if there are conflicting delivery dates or quantities that require the system to create separate schedule lines.
  Configuration Issues: There may be configuration settings in the SCM module that are not aligned with the business processes, leading to unexpected behavior during order processing.
  Data Inconsistencies: Inconsistent or incorrect data in the order or related master data (like material master, customer master, etc.) can also lead to this error.
  
  Solution:
  
  Review Order Details: Check the details of the order and the items involved. Look for any discrepancies in quantities, delivery dates, or other parameters that might cause the item to split.
  Adjust Scheduling Parameters: If applicable, adjust the scheduling parameters in the order to ensure that they align with the business requirements and do not lead to item splits.
  Check Configuration: Review the configuration settings in the SCM module related to order processing and scheduling. Ensure that they are set up correctly to handle item splits and schedule line aggregation.
  Data Consistency Check: Perform a data consistency check to ensure that all related master data is accurate and up-to-date. Correct any inconsistencies found.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific recommendations or patches that may address the issue.
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version of SAP you are using and any known issues.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like MD04 (Stock/Requirements List) or CO09 (Availability Check) to analyze the stock and requirements situation for the order.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.