How To Fix PPH_MRP115 - Number of deleted PLAF: &1 (MRP Live on HANA), &2 (classic MRP)

SAP Error Message - Details

• Message type: E = Error

• Message class: PPH_MRP -

• Message number: 115

• Message text: Number of deleted PLAF: &1 (MRP Live on HANA), &2 (classic MRP)

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 PPH_MRP115 - Number of deleted PLAF: &1 (MRP Live on HANA), &2 (classic MRP) ?

  The SAP error message PPH_MRP115 indicates that there is a discrepancy in the number of planned orders (PLAF) that have been deleted between MRP Live on HANA and the classic MRP. This error typically arises during the execution of the MRP process when the system detects that the number of planned orders deleted in the MRP Live run does not match the number deleted in the classic MRP run.
  Cause:
  
  Inconsistent Data: The primary cause of this error is often due to inconsistencies in the data between the two MRP processes. This can happen if there are differences in the configuration, settings, or data that affect how planned orders are processed in MRP Live versus classic MRP.
  Parallel Processing: If both MRP Live and classic MRP are run in parallel or if there are multiple users making changes to planned orders simultaneously, it can lead to discrepancies.
  Custom Logic: If there are custom enhancements or logic implemented in either MRP Live or classic MRP, it may lead to different behaviors in how planned orders are deleted.
  
  Solution:
  
  Check Configuration: Review the configuration settings for both MRP Live and classic MRP to ensure they are aligned. Look for any differences in parameters that might affect planned order processing.
  Data Consistency: Ensure that the data being processed by both MRP runs is consistent. This may involve checking for any recent changes to master data, such as material master records, BOMs, or routing information.
  Run MRP in Sequence: If possible, avoid running MRP Live and classic MRP simultaneously. Run them in sequence to prevent conflicts and ensure that the data is consistent between runs.
  Review Logs: Check the MRP logs for any additional error messages or warnings that might provide more context on the issue. This can help identify specific planned orders that are causing the discrepancy.
  SAP Notes: Look for any relevant SAP Notes or updates that address this specific error message. SAP frequently releases notes that provide fixes or workarounds for known issues.
  Consult SAP Support: If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They may have additional insights or solutions based on the specific version and configuration of your SAP system.
  
  Related Information:
  
  MRP Live vs. Classic MRP: MRP Live is designed to leverage the capabilities of HANA for faster processing and real-time data handling, while classic MRP is the traditional method. Understanding the differences in how they process data can help in troubleshooting.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MD01 (MRP Run), MD02 (MRP Run for Single Material), and MD04 (Stock/Requirements List) to analyze the planned orders and their statuses.
  Performance Monitoring: Monitor the performance of MRP runs to identify any bottlenecks or issues that may arise during processing.
  
  By following these steps, you should be able to identify the cause of the PPH_MRP115 error and implement a solution to resolve it.