How To Fix /FTI/INTERNAL_ERROR072 - No change authorisation. Editing not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/INTERNAL_ERROR -

• Message number: 072

• Message text: No change authorisation. Editing not possible

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 /FTI/INTERNAL_ERROR072 - No change authorisation. Editing not possible ?

  The SAP error message /FTI/INTERNAL_ERROR072 No change authorisation. Editing not possible typically indicates that the user does not have the necessary authorizations to make changes to a specific object or data within the SAP system. This error is often encountered in the context of SAP Fiori or other SAP applications where user roles and authorizations are strictly enforced.
  Cause:
  
  Authorization Issues: The user attempting to make changes does not have the required authorization roles assigned to their user profile.
  Object Locking: The object being edited may be locked by another user or process, preventing changes.
  Configuration Settings: Certain configuration settings may restrict editing capabilities based on user roles or statuses of the data.
  
  Solution:
  
  
  Check User Roles:
  
  Verify the user’s roles and authorizations in the SAP system. This can be done by using transaction code SU01 to check the user profile and PFCG to review the roles assigned.
  Ensure that the user has the necessary authorizations for the specific transaction or object they are trying to edit.
  
  
  
  Request Additional Authorizations:
  
  If the user lacks the necessary authorizations, they should contact their SAP security administrator or the relevant team to request the required roles or authorizations.
  
  
  
  Check Object Locking:
  
  If the object is locked, identify the user or process that has locked it. You can use transaction code SM12 to view and manage locks in the system.
  
  
  
  Review Configuration Settings:
  
  Check if there are any specific configuration settings that might restrict editing capabilities. This may involve reviewing the application configuration or consulting with the functional team responsible for the module in question.
  
  
  
  Testing in a Different Environment:
  
  If possible, test the same action in a different environment (like a development or quality assurance system) to see if the issue persists. This can help determine if the problem is environment-specific.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SM12: Display and Delete Locks
  SU53: Display Authorization Check (to see what authorizations were checked and failed)
  
  
  
  Documentation: Refer to SAP documentation or help resources for detailed information on authorization objects and roles.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  If the issue persists after following these steps, it may be necessary to escalate the matter to SAP support or consult with a technical expert familiar with the specific SAP environment and configuration.