How To Fix /ISDFPS/PM138 - Error; cannnot determine change authorization for object &1/&2

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/PM -

• Message number: 138

• Message text: Error; cannnot determine change authorization for object &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 /ISDFPS/PM138 - Error; cannnot determine change authorization for object &1/&2 ?

  The SAP error message /ISDFPS/PM138 indicates that the system cannot determine change authorization for a specific object. This error typically arises in the context of SAP's Project Management (PM) or Project System (PS) modules, particularly when trying to make changes to project-related data.
  Cause:
  The error can occur due to several reasons:
  
  Missing Authorizations: The user may not have the necessary authorizations to change the specified object. This could be due to missing roles or authorizations in the user's profile.
  Configuration Issues: There may be issues in the configuration of the authorization objects related to the project management or project system modules.
  Object Not Found: The specified object (e.g., project, WBS element) may not exist or may have been deleted, leading to the inability to determine the authorization.
  Transport Issues: If the system is in a transport environment, there may be inconsistencies between the development and production systems regarding authorization objects.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction SU53 immediately after the error occurs to check the authorization check failure. This will show you which authorization object is missing.
  Review the user's roles and authorizations in transaction PFCG to ensure they have the necessary permissions for the object in question.
  
  
  
  Review Authorization Objects:
  
  Check the relevant authorization objects (e.g., S_PROJECT, S_PROJ, etc.) to ensure they are correctly configured and assigned to the user.
  
  
  
  Validate Object Existence:
  
  Verify that the object (e.g., project, WBS element) exists in the system and is not in a deleted or inactive state.
  
  
  
  Consult with Basis Team:
  
  If the issue persists, consult with your SAP Basis team to check for any transport-related issues or inconsistencies in the authorization setup.
  
  
  
  Check Configuration:
  
  Review the configuration settings related to project management and authorization checks to ensure they are set up correctly.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the code where the error occurs to understand why the authorization check is failing.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SE93: Transaction Codes
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects for project management, as they define what actions users can perform on project-related data.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  If the problem continues after following these steps, it may be beneficial to reach out to SAP support for further assistance.