How To Fix 5@072 - Authorization cannot be copied

5@072 - Overview

• Message type: E = Error

• Message class: 5@ -

• Message number: 072

• Message text: Authorization cannot be copied

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 5@072 - Authorization cannot be copied ?

  The SAP error message "5@072 Authorization cannot be copied" typically occurs when there is an issue with the authorization objects or roles in the SAP system. This error is often encountered during the process of copying or transferring authorizations from one user to another or when trying to assign roles.
  
  Cause:
  
  Missing Authorization Objects: The authorization objects required for the role or profile you are trying to copy may not exist in the target system or may not be assigned to the user.
  Inconsistent Role Definitions: The role definitions may be inconsistent or incomplete, leading to issues when attempting to copy authorizations.
  User Master Record Issues: The user master record may not have the necessary authorizations or may be locked.
  Transport Issues: If the roles or authorizations were transported from another system, there may have been issues during the transport process.
  Profile Generation Issues: There may be issues with the profile generation process that prevent the