How To Fix PPH_FCDM036 - PIR cannot be created as Plant &1 and MRP Area &2 is not Equal

SAP Error Message - Details

• Message type: E = Error

• Message class: PPH_FCDM - Forecast Demand Messages

• Message number: 036

• Message text: PIR cannot be created as Plant &1 and MRP Area &2 is not Equal

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_FCDM036 - PIR cannot be created as Plant &1 and MRP Area &2 is not Equal ?

  The SAP error message PPH_FCDM036 indicates that a Purchase Info Record (PIR) cannot be created because the specified Plant and MRP Area are not equal. This error typically arises in the context of materials management and procurement processes within SAP.
  Cause:
  The error occurs when there is an inconsistency between the plant and MRP area specified in the transaction. Specifically, the system expects the plant and MRP area to match, but they do not. This can happen due to:
  
  Incorrect Data Entry: The user may have entered the wrong plant or MRP area in the transaction.
  Configuration Issues: The configuration settings in the system may not align with the expected values for the plant and MRP area.
  Master Data Issues: The material master data or info record may not be set up correctly for the specified plant and MRP area.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Verify Input Data:
  
  Check the values entered for the Plant and MRP Area in the transaction. Ensure that they are correct and correspond to the same entity.
  
  
  
  Check Master Data:
  
  Review the material master data for the material in question. Ensure that the MRP area is correctly assigned to the plant.
  You can do this by navigating to the material master record (transaction code MM03) and checking the MRP area settings.
  
  
  
  Review Configuration:
  
  If you have access to configuration settings, check the settings for MRP areas and plants in the system. Ensure that they are correctly configured to allow for the creation of PIRs.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for additional guidance on the specific error message and its implications.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME11 (Create Info Record), ME12 (Change Info Record), and MM03 (Display Material).
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may address the issue.
  Training: Consider training sessions or resources on SAP Material Management to better understand how to manage plants, MRP areas, and info records effectively.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to create the Purchase Info Record successfully.