How To Fix /PF1/MSG_EH_E736 - PO split completed

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_EH_E -

• Message number: 736

• Message text: PO split completed

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 /PF1/MSG_EH_E736 - PO split completed ?

  The SAP error message /PF1/MSG_EH_E736 PO split completed typically indicates that a purchase order (PO) has been split during processing. This can occur in various scenarios, such as when a PO is being processed for multiple delivery dates, different vendors, or when the quantities exceed certain limits.
  Cause:
  
  Delivery Date Variations: If the items in the PO have different delivery dates, SAP may split the PO to manage these deliveries separately.
  Quantity Limits: If the total quantity of items exceeds the system's predefined limits for a single PO, it may trigger a split.
  Vendor Variations: If the items are sourced from different vendors, the system may split the PO accordingly.
  Configuration Settings: Certain settings in the SAP configuration may dictate how POs are handled, leading to automatic splits based on specific criteria.
  
  Solution:
  
  Review PO Details: Check the details of the purchase order to understand why it was split. Look for variations in delivery dates, quantities, or vendor information.
  Adjust PO Settings: If the splitting behavior is not desired, you may need to adjust the configuration settings in the SAP system. This may involve working with your SAP Basis or configuration team.
  Consolidate Orders: If possible, consolidate the items into a single PO before processing to avoid splits.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling PO splits in your version of SAP.
  Contact Support: If the issue persists or if you need further assistance, consider reaching out to SAP support or your internal IT team for help.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to manage POs effectively.
  SAP Notes: Check for any SAP Notes related to PO processing and splitting that may provide additional insights or fixes.
  User Training: Ensure that users involved in the procurement process are trained on how to handle POs and understand the implications of splits.
  
  By understanding the cause and implementing the suggested solutions, you can effectively manage and resolve the /PF1/MSG_EH_E736 PO split completed error in SAP.