How To Fix KH705 - Authorization object is used in another application or another client

SAP Error Message - Details

• Message type: E = Error

• Message class: KH - CO-PA Reporting

• Message number: 705

• Message text: Authorization object is used in another application or another client

What causes this issue?

You tried to change an authorization object which was created in
another application or another client.

System Response

You cannot change the authorization object.

How to fix this error?

If the authorization object was created in another application, call
up that application to change it:
CO-PA Information System: Customizing -> Profitability Analysis ->
Information System -> Authorization objects
CO-PA Planning: Customizing -> Profitability Analysis -> Planning
-> Authorization objects
SAP-EIS: SAP-EIS Customizing -> Environment -> Maintain user ->
SAP-EIS authorizations
If the authorization object was not created in any of these
applications, then it is a customer authorization. Maintain it
in the CASE menu.
If the authorization was created in the current application but in a
different client, you need to transport the corresponding entry from
Table TKEB3 to this client (R3TR TABU).
Once you have done this, the system will check this authorization object
in this client, and you can also maintain it here.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KH705 - Authorization object is used in another application or another client ?

  The SAP error message KH705 indicates that an authorization object is being used in a different application or client than the one currently being accessed. This typically occurs when there are issues related to user authorizations or when the system is trying to access an object that is not available in the current context.
  Cause:
  
  Authorization Issues: The user does not have the necessary authorizations to access the specific application or client.
  Cross-Client Configuration: The authorization object may be defined in one client but is being referenced in another client where it is not available.
  Transport Issues: If the authorization object was transported from one client to another, it may not have been properly configured or activated in the target client.
  Role Assignment: The user’s role may not include the necessary authorizations for the specific application or client.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to analyze the authorization check. This will show which authorization was missing.
  Review the user’s roles and profiles in transaction SU01 or PFCG to ensure that the necessary authorizations are included.
  
  
  
  Verify Client-Specific Settings:
  
  Ensure that the authorization object is correctly defined and active in the client you are trying to access.
  If the object is client-specific, check if it needs to be replicated or configured in the current client.
  
  
  
  Role Maintenance:
  
  If the authorization object is missing from the user’s role, you may need to add it using transaction PFCG.
  After making changes, ensure to generate the profile and assign it to the user.
  
  
  
  Transport Requests:
  
  If the authorization object was recently transported, check the transport logs to ensure that it was successfully imported into the target client.
  If there are issues with the transport, you may need to re-transport the authorization object.
  
  
  
  Consult with Security Team:
  
  If you are not able to resolve the issue, consult with your SAP security team or basis team to investigate further. They can help in checking the configuration and ensuring that the necessary authorizations are in place.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  
  
  Authorization Objects: These are used in SAP to control access to various functionalities and data. Each object has fields that define the specific authorizations required.
  Client Concept: SAP systems can have multiple clients, and each client can have its own set of data and configurations. Authorization objects may be client-specific, meaning they need to be defined in each client where they are used.
  
  By following these steps, you should be able to identify and resolve the issue related to the KH705 error message in SAP.