How To Fix KH704 - Authorization object does not exist -> choose another

SAP Error Message - Details

• Message type: E = Error

• Message class: KH - CO-PA Reporting

• Message number: 704

• Message text: Authorization object does not exist -> choose another

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 KH704 - Authorization object does not exist -> choose another ?

  The SAP error message KH704 ("Authorization object does not exist -> choose another") typically indicates that the user is trying to access a transaction or function that requires authorization for an object that is not defined in the system. This can occur in various contexts, such as when working with cost center accounting, internal orders, or other financial transactions.
  Cause:
  
  Missing Authorization Object: The specific authorization object that the transaction or function requires is not defined in the system.
  User Role Issues: The user may not have the necessary roles assigned that include the required authorization objects.
  Custom Development: If there are custom programs or enhancements, they may reference authorization objects that are not standard or not properly configured.
  Transport Issues: If the authorization objects were recently transported from another system, they may not have been properly activated or may be missing.
  
  Solution:
  
  
  Check Authorization Objects:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into which authorization object is missing.
  Review the authorization objects in transaction SU01 for the user profile to ensure that the necessary roles are assigned.
  
  
  
  Assign Missing Roles:
  
  If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include the required authorization objects.
  
  
  
  Create or Modify Authorization Objects:
  
  If the authorization object is indeed missing, it may need to be created or modified. This typically requires access to the SAP security configuration and should be done by someone with the appropriate permissions.
  
  
  
  Check Transport Requests:
  
  If the issue arose after a transport, ensure that all necessary objects were included in the transport request and that they were properly imported into the target system.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with SAP support for specific guidance related to the authorization object in question.
  
  
  
  Testing:
  
  After making changes, test the transaction again to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  
  
  Authorization Objects: These are defined in the system and can be viewed in transaction SU21. You can check if the object exists and what fields it contains.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific authorization object or transaction you are working with.
  
  If the problem persists after following these steps, it may be necessary to engage with your SAP Basis or security team for further investigation.