How To Fix /ISDFPS/FDPFA042 - No authorization to create positions

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/FDPFA -

• Message number: 042

• Message text: No authorization to create positions

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 /ISDFPS/FDPFA042 - No authorization to create positions ?

  The SAP error message /ISDFPS/FDPFA042 No authorization to create positions typically indicates that the user attempting to create positions in the system does not have the necessary authorizations or permissions to perform this action. This error is commonly encountered in the context of SAP's Flexible Personnel Management (FPM) or similar modules where position management is involved.
  Cause:
  
  Missing Authorizations: The user lacks the required authorization objects that allow them to create positions. This could be due to missing roles or profiles assigned to the user.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for position management.
  Organizational Structure: The user may not have access to the specific organizational units or areas where they are trying to create positions.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization checks failed. This will provide insight into what specific authorizations are missing.
  Review the user’s roles and profiles in transaction SU01 (User Maintenance) to ensure they have the necessary permissions.
  
  
  
  Assign Required Roles:
  
  If the user is missing roles, work with your SAP security team to assign the appropriate roles that include the necessary authorization objects for creating positions. Common authorization objects related to position management include:
  
  P_ORGXX (Authorization for Organizational Management)
  P_PLOGI (Authorization for Personnel Administration)
  P_PERSG (Authorization for Personnel Area)
  
  
  
  
  
  Review Organizational Structure:
  
  Ensure that the user has access to the relevant organizational units where they are trying to create positions. This may involve checking the organizational assignment in their user profile.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, have the user log out and log back in to ensure that the changes take effect. Then, attempt to create the position again.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization’s internal guidelines for managing authorizations and roles, as there may be specific procedures in place.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance (to manage roles and authorizations)
  
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that pertain to position management in your SAP system.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to this error message.
  
  
  If the issue persists after following these steps, it may be necessary to engage with your SAP Basis or Security team for further investigation and resolution.