How To Fix KX072 - Authorization to edit fields is incomplete (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: KX - EC-EIS/EC-BP: Data basis, data collection

• Message number: 072

• Message text: Authorization to edit fields is incomplete (see long text)

What causes this issue?

The user profile does not contain all authorizations that are necessary
to edit fields.

How to fix this error?

For unrestricted use of the field-editing transaction, the following
authorizations for authorization object 'S_DEVELOP' are missing:
Field 'DEVCLASS': 'KC' or '*' (Development class KC).
Field 'OBJTYPE' : 'PROG' or '*' (Object type program).
Field 'OBJNAME' : 'SAPMKCGD' or '*' (Program SAPMKCGD).
Field 'ACTVT' : '03' (Activity: display).

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KX072 - Authorization to edit fields is incomplete (see long text) ?

  The SAP error message KX072, which states "Authorization to edit fields is incomplete (see long text)," typically occurs when a user attempts to access or modify certain fields in the SAP system but lacks the necessary authorizations to do so. This can happen in various transactions, particularly in the context of controlling (CO) or cost center accounting.
  Cause:
  The error is generally caused by one of the following reasons:
  
  Insufficient Authorizations: The user role assigned to the user does not have the necessary permissions to edit specific fields in the transaction or report.
  Field-Level Security: Certain fields may be restricted based on the user's role or profile settings.
  Configuration Issues: There may be configuration settings in the SAP system that restrict access to certain fields based on user roles.
  
  Solution:
  To resolve the KX072 error, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error. This will show you the authorization check that failed and provide insight into which specific authorization object is missing.
  Review the user's roles and authorizations in transaction SU01 or PFCG. Ensure that the user has the necessary authorizations for the transaction and the specific fields they are trying to edit.
  
  
  
  Modify User Roles:
  
  If the user lacks the required authorizations, you may need to modify their roles or create a new role that includes the necessary authorizations. This may involve working with your SAP security team or administrator.
  
  
  
  Consult Long Text:
  
  The error message indicates that there is a "long text" associated with it. You can view this long text for more specific guidance on what authorizations are required. This can usually be accessed by clicking on the message or using transaction SE91 to look up the message number.
  
  
  
  Field Status Group:
  
  Check if the field in question is controlled by a field status group in the configuration. You may need to adjust the field status settings in the relevant configuration area (e.g., controlling area settings).
  
  
  
  Testing:
  
  After making changes to authorizations or configurations, have the user log out and log back in to ensure that the changes take effect. Test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to the fields in question. Common objects related to controlling include K_CCACTVT, K_CCACTVT, and others depending on the specific transaction.
  SAP Notes: Check SAP Notes for any known issues or updates related to the error message KX072. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Review SAP documentation or training materials related to user authorizations and field status management for a deeper understanding of how to manage these settings effectively.
  
  If the issue persists after following these steps, it may be necessary to engage with your SAP support team or consult with SAP directly for further assistance.