How To Fix ESH_AU_AUTHORIZATION004 - Authorization object &1 not found via RFC destination &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_AU_AUTHORIZATION - ESH: Checking for authorizations

• Message number: 004

• Message text: Authorization object &1 not found via RFC destination &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 ESH_AU_AUTHORIZATION004 - Authorization object &1 not found via RFC destination &2 ?

  The SAP error message ESH_AU_AUTHORIZATION004 indicates that there is an issue with authorization related to an authorization object that cannot be found via the specified RFC (Remote Function Call) destination. This error typically arises in the context of SAP Enterprise Search or when accessing certain functionalities that require specific authorizations.
  Cause:
  
  Missing Authorization Object: The specified authorization object (denoted as &1 in the error message) does not exist in the system or is not properly defined.
  Incorrect RFC Destination: The RFC destination (denoted as &2) may be incorrectly configured or pointing to a system that does not have the required authorization object.
  Authorization Issues: The user may not have the necessary authorizations to access the specified object, or the object may not be assigned to the user’s role.
  Transport Issues: If the authorization object was recently transported from another system, it may not have been properly activated or may be missing in the target system.
  
  Solution:
  
  
  Check Authorization Object:
  
  Verify if the authorization object exists in the system. You can do this by using transaction code SU21 to check for the object.
  If it does not exist, you may need to create it or ensure it is properly transported from another system.
  
  
  
  Verify RFC Destination:
  
  Check the configuration of the RFC destination using transaction SM59. Ensure that it is correctly set up and points to the right system.
  Test the RFC connection to ensure it is working properly.
  
  
  
  User Authorizations:
  
  Use transaction SU01 to check the user’s roles and authorizations. Ensure that the user has the necessary roles assigned that include the required authorization object.
  If necessary, modify the user’s roles or create a new role that includes the required authorizations.
  
  
  
  Transport and Activation:
  
  If the authorization object was recently transported, ensure that it has been activated in the target system.
  Check the transport logs for any errors related to the transport of the authorization object.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or support notes related to the specific authorization object and its usage in the context of your application.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU21: To manage authorization objects.
  SM59: To manage RFC destinations.
  SU01: To manage user accounts and roles.
  PFCG: To manage roles and authorizations.
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to the error message.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.