How To Fix KH729 - Authorizations still exist for object -> display only

KH729 - Overview

• Message type: E = Error

• Message class: KH - CO-PA Reporting

• Message number: 729

• Message text: Authorizations still exist for object -> display only

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 KH729 - Authorizations still exist for object -> display only ?

  The SAP error message KH729 ("Authorizations still exist for object -> display only") typically occurs in the context of authorization checks within the SAP system, particularly when dealing with authorization objects related to cost accounting or controlling.
  
  Cause:
  This error message indicates that the user attempting to perform a certain action does not have the necessary authorizations to execute that action fully. Instead, the user may only have display authorizations for the relevant objects, which restricts them from making changes or executing certain functions.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error. This will show you the last authorization check that failed and provide insights into which specific authorization object is lacking.
  Alternatively, you can use transaction SU01 to check the user's roles and authorizations.
  
  
  
  Review Roles and Profiles:
  
  Ensure that the user has the appropriate roles assigned that include the necessary authorizations for