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

PPH_MRP118 - Overview

• Message type: E = Error

• Message class: PPH_MRP -

• Message number: 118

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

  The SAP error message PPH_MRP118 indicates a discrepancy in the number of reservations (RESB) created during the Material Requirements Planning (MRP) process when comparing the results from MRP Live on HANA and the classic MRP. This message typically arises when there is a mismatch in the data processed by the two systems, leading to different numbers of reservations being generated.
  
  Cause:
  
  Data Inconsistency: There may be inconsistencies in the master data or transaction data that are being used by MRP Live and classic MRP. This can include differences in material master records, BOMs (Bill of Materials), or routing information.
  
  Configuration Issues: The configuration settings for MRP Live and classic MRP may not be aligned, leading to different processing logic or parameters being applied.
  Execution Context: The execution context (e.g., selection criteria, planning horizon) may differ between the two MRP runs, resulting in different outputs.
  Custom Logic: If there are custom enhancements or user exits that