How To Fix VK768 - No authorization. &1 in controlling area &2, company code &3

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 768

• Message text: No authorization. &1 in controlling area &2, company code &3

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 VK768 - No authorization. &1 in controlling area &2, company code &3 ?

  The SAP error message VK768 "No authorization. &1 in controlling area &2, company code &3" typically indicates that the user does not have the necessary authorizations to perform a specific action in the Controlling (CO) module for the specified controlling area and company code.
  Cause:
  
  Missing Authorizations: The user lacks the required authorization objects related to the Controlling area or company code.
  Role Assignment: The user may not have been assigned the appropriate roles that include the necessary authorizations.
  Profile Issues: The user’s profile may not be correctly configured to allow access to the required transactions or data.
  Organizational Level Restrictions: The user may have access to certain organizational levels but not to the specific controlling area or company code mentioned in the error.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which specific authorization object is missing.
  
  
  
  Review User Roles:
  
  Go to transaction SU01 to review the user’s roles and profiles. Ensure that the user has the necessary roles assigned that include access to the controlling area and company code in question.
  
  
  
  Modify Roles:
  
  If the user is missing the required authorizations, you may need to modify existing roles or create new ones. This can be done using transaction PFCG (Profile Generator).
  Ensure that the roles include the necessary authorization objects, such as K_CCA (Cost Center Accounting) or K_CCA_CTR (Cost Center Accounting - Controlling Area).
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, consult with your SAP security team or administrator to request the required access.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects for Controlling, such as:
  
  K_CCA (Cost Center Accounting)
  K_CCA_CTR (Cost Center Accounting - Controlling Area)
  K_CCA_CCC (Cost Center Accounting - Cost Center)
  
  
  
  Transaction Codes:
  
  SU53: Display authorization check
  SU01: User maintenance
  PFCG: Role maintenance
  
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.
  
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the VK768 error message.