How To Fix /ISDFPS/PM118 - Change authorization not in system for &1 &2. Cannot add

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/PM -

• Message number: 118

• Message text: Change authorization not in system for &1 &2. Cannot add

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/PM118 - Change authorization not in system for &1 &2. Cannot add ?

  The SAP error message /ISDFPS/PM118 Change authorization not in system for &1 &2. Cannot add typically occurs in the context of the SAP IS-DFPS (Industry Solution for Defense Forces and Security) module. This error indicates that the user does not have the necessary authorization to make changes to a specific object or record in the system.
  
  Cause:
  
  Authorization Issues: The user attempting to perform the action does not have the required authorization roles or permissions assigned in the SAP system.
  Missing Authorization Objects: The relevant authorization objects that govern the ability to change the specified entity (e.g., a document, record, or configuration) are not defined or are missing in the user's profile.
  Configuration Errors: There may be configuration issues in the authorization management settings that prevent the user from having the necessary access.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check that failed. This will provide insight