How To Fix FSH_PP_ORD071 - Field &1 is not relevant for planned order type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_PP_ORD - Messages related Master PldOrd & Master ProdOrd

• Message number: 071

• Message text: Field &1 is not relevant for planned order type &2

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 FSH_PP_ORD071 - Field &1 is not relevant for planned order type &2 ?

  The SAP error message FSH_PP_ORD071 indicates that a specific field (denoted as &1) is not relevant for the planned order type (denoted as &2) you are working with. This error typically arises in the context of production planning and can occur during various processes, such as creating or modifying planned orders.
  Cause:
  
  Field Relevance: The field in question may not be applicable to the planned order type you are using. Each planned order type in SAP can have specific fields that are relevant or irrelevant based on the configuration.
  Configuration Issues: The configuration settings for the planned order type may not include the field you are trying to use. This can happen if the planned order type is set up to exclude certain fields.
  Data Entry Errors: There may be an attempt to enter data into a field that is not intended for that specific planned order type.
  
  Solution:
  
  
  Check Configuration: Review the configuration settings for the planned order type in transaction SPRO (SAP Reference IMG). Navigate to:
  
  Production ? Basic Data ? Planned Orders ? Define Planned Order Types.
  Ensure that the field you are trying to use is relevant for the planned order type in question.
  
  
  
  Field Usage: Verify if the field you are trying to fill is indeed relevant for the planned order type. If it is not, you may need to either:
  
  Use a different planned order type that supports the field.
  Modify your data entry to exclude the irrelevant field.
  
  
  
  Consult Documentation: Check SAP documentation or help resources for the specific planned order type to understand which fields are relevant.
  
  
  User Exits or BAdIs: If you need to make a field relevant for a specific planned order type, consider using user exits or Business Add-Ins (BAdIs) to customize the behavior of the planned order type.
  
  
  Testing: After making any changes, test the planned order creation or modification process to ensure that the error no longer occurs.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MD01 (MRP Run), CO01 (Create Production Order), and MD04 (Stock/Requirements List) to understand where the error might be occurring.
  SAP Notes: Search for SAP Notes related to the error message for any known issues or patches that may address the problem.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to access and modify the planned order types and related fields.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.