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

SAP Error Message - Details

• Message type: E = Error

• Message class: PPH_MRP -

• Message number: 117

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

  The SAP error message PPH_MRP117 indicates a discrepancy in the number of reservation items (RESB) that have been deleted during the Material Requirements Planning (MRP) process. Specifically, it compares the number of deleted reservation items in MRP Live on HANA with the number of deleted reservation items in the classic MRP.
  Cause:
  This error typically arises due to inconsistencies between the MRP Live and classic MRP processes. Possible causes include:
  
  Data Inconsistency: There may be inconsistencies in the data between the two MRP processes, leading to different counts of deleted reservations.
  Configuration Issues: Incorrect configuration settings in the MRP settings or in the integration between MRP Live and classic MRP.
  Custom Code or Enhancements: If there are custom developments or enhancements in the MRP process, they may not be aligned with the standard processes, causing discrepancies.
  System Performance Issues: Performance issues or timeouts during the MRP run could lead to incomplete processing of reservations.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Check MRP Configuration: Review the configuration settings for both MRP Live and classic MRP to ensure they are correctly set up and aligned.
  Data Consistency Check: Perform a data consistency check to identify any discrepancies between the two processes. You can use transaction codes like SE16 or SE11 to analyze the RESB table.
  Run MRP in Classic Mode: If the issue persists, try running the MRP in classic mode to see if it produces the same error. This can help isolate whether the issue is specific to MRP Live.
  Review Custom Code: If there are any custom developments related to MRP, review them to ensure they are not causing the discrepancy.
  SAP Notes and Support: Check for any relevant SAP Notes that may address this specific error. You can search the SAP Support Portal for updates or patches that may resolve the issue.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  MRP Live: MRP Live is a more efficient and faster version of the traditional MRP process, optimized for HANA databases. It processes data in real-time and is designed to handle larger datasets more effectively.
  RESB Table: The RESB table contains reservation data in SAP, and discrepancies in this table can lead to various MRP-related issues.
  SAP Community and Forums: Engaging with the SAP Community or forums can provide insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be necessary to involve SAP support for further investigation.