How To Fix PPH_MRP120 - Number of updated RESB: &1 (MRP Live on HANA), &2 (classic MRP)

SAP Error Message - Details

• Message type: E = Error

• Message class: PPH_MRP -

• Message number: 120

• Message text: Number of updated RESB: &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_MRP120 - Number of updated RESB: &1 (MRP Live on HANA), &2 (classic MRP) ?

  The SAP error message PPH_MRP120 indicates an issue related to the Material Requirements Planning (MRP) process, specifically when using MRP Live on HANA and comparing it to classic MRP. The message typically provides information about the number of RESB (reservation/dependent requirements) records that were updated during the MRP run, with two numbers: one for MRP Live and one for classic MRP.
  Cause:
  
  Data Inconsistency: There may be inconsistencies in the data between the MRP Live and classic MRP processes. This can occur if there are differences in the configuration or if the data has not been properly synchronized.
  Configuration Issues: Incorrect settings in the MRP configuration can lead to discrepancies in how the two processes handle data.
  Performance Issues: If the system is under heavy load or if there are performance issues, it may affect the execution of MRP Live, leading to incomplete updates.
  Custom Code or Enhancements: If there are custom developments or enhancements in the MRP process, they may not be compatible with MRP Live, causing errors.
  
  Solution:
  
  Check Configuration: Review the MRP configuration settings in both MRP Live and classic MRP to ensure they are aligned. Pay attention to settings related to planning parameters, lot sizing, and other relevant configurations.
  Data Consistency Check: Run consistency checks on the relevant master data (material master, BOM, routing, etc.) to ensure there are no discrepancies that could affect the MRP run.
  Performance Monitoring: Monitor system performance during MRP runs to identify any bottlenecks or issues that may be affecting the execution of MRP Live.
  Review Logs: Check the MRP logs for any additional error messages or warnings that could provide more context on the issue.
  SAP Notes: Look for relevant SAP Notes or updates that may address known issues with MRP Live or provide patches that could resolve the problem.
  Testing: If possible, conduct tests in a development or quality environment to replicate the issue and identify the root cause without affecting production data.
  
  Related Information:
  
  MRP Live vs. Classic MRP: MRP Live is designed to leverage the capabilities of SAP HANA for faster processing and real-time planning. Understanding the differences in how these two processes operate can help in troubleshooting.
  SAP Help Documentation: Refer to the official SAP documentation for MRP Live and classic MRP for detailed information on configuration and best practices.
  Community Forums: Engage with SAP community forums or support channels where other users may have encountered similar issues and can share their solutions.
  
  If the issue persists after following these steps, it may be necessary to engage SAP support for further assistance.