How To Fix PPH_FCDM035 - No Authorizations for Planned Independent Requirements &1 &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: PPH_FCDM - Forecast Demand Messages

• Message number: 035

• Message text: No Authorizations for Planned Independent Requirements &1 &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 PPH_FCDM035 - No Authorizations for Planned Independent Requirements &1 &2. ?

  The SAP error message PPH_FCDM035 "No Authorizations for Planned Independent Requirements &1 &2" typically indicates that the user does not have the necessary authorizations to access or manage Planned Independent Requirements (PIR) in the SAP system. This can occur in various modules, particularly in Production Planning (PP) or Supply Chain Management (SCM).
  Cause:
  
  Missing Authorizations: The user role assigned to the individual does not include the necessary authorizations for accessing or modifying Planned Independent Requirements.
  Authorization Object Restrictions: The authorization objects related to PIR may not be properly configured or assigned to the user.
  User Role Issues: The user may not be assigned to the correct role that includes the necessary permissions for the tasks they are trying to perform.
  
  Solution:
  
  
  Check User Roles: Verify the roles assigned to the user in transaction code SU01 (User Maintenance). Ensure that the user has the appropriate roles that include access to Planned Independent Requirements.
  
  
  Review Authorization Objects: Use transaction code SU53 immediately after encountering the error to check which authorization objects are missing. This will provide insight into what specific permissions are lacking.
  
  
  Modify Roles: If the user lacks the necessary authorizations, you may need to modify the user roles or create a new role that includes the required authorizations. This can be done using transaction code PFCG (Role Maintenance).
  
  
  Consult with Security Team: If you do not have the necessary permissions to change roles or authorizations, contact your SAP security team or administrator to request the required access.
  
  
  Testing: After making changes to roles or authorizations, have the user log out and log back in to ensure that the changes take effect. Test the functionality again to confirm that the error is resolved.
  
  
  Related Information:
  
  Authorization Objects: Common authorization objects related to Planned Independent Requirements include C_MRP_PIR (for PIR access) and C_MRP_MAT (for material access).
  Documentation: Refer to SAP documentation or your organization's internal guidelines for managing user roles and authorizations.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MD61 (Create Planned Independent Requirements), MD62 (Change Planned Independent Requirements), and MD63 (Display Planned Independent Requirements) to understand where the error may occur.
  
  By following these steps, you should be able to identify and resolve the authorization issue related to the error message PPH_FCDM035.