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

PPH_MRP116 - Overview

• Message type: E = Error

• Message class: PPH_MRP -

• Message number: 116

• Message text: Number of inserted 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.

PPH_MRP116 - Details

• The SAP error message PPH_MRP116 indicates a discrepancy in the number of planned orders (PLAF) generated by MRP Live on HANA compared to the classic MRP. Specifically, it shows the number of planned orders created by both processes, where &1 represents the count from MRP Live and &2 represents the count from classic MRP.
  
  Cause:
  
  Different MRP Logic: MRP Live and classic MRP may use different algorithms or logic for generating planned orders. This can lead to variations in the output.
  Configuration Differences: There may be differences in the configuration settings between MRP Live and classic MRP, such as planning parameters, lot sizing procedures, or other settings that affect how planned orders are generated.
  Data Inconsistencies: Inconsistencies in master data (like material master, BOM, routing) or transaction data (like stock levels, open orders) can lead to different results.
  Versioning: If there are different versions of the same material or different planning strategies applied, this can