How To Fix /ACCGO/CAS_APPL_MSG086 - End of Authorization Check

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_APPL_MSG -

• Message number: 086

• Message text: End of Authorization Check

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 /ACCGO/CAS_APPL_MSG086 - End of Authorization Check ?

  The SAP error message /ACCGO/CAS_APPL_MSG086 End of Authorization Check typically indicates that an authorization check has been performed, and the system has reached the end of the authorization check process. This message is often related to the SAP Controlling (CO) module, particularly in the context of the Cost Accounting (CO) and Financial Accounting (FI) integration.
  Cause:
  
  Authorization Issues: The user may not have the necessary authorizations to perform the action they are attempting. This could be due to missing roles or permissions in the user's profile.
  Configuration Issues: There may be a misconfiguration in the authorization objects related to the specific transaction or process being executed.
  Custom Development: If there are custom programs or enhancements, they may not be handling authorization checks correctly.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization checks failed. This will provide insight into what specific authorizations are missing.
  Review the user's roles and profiles in transaction SU01 or PFCG to ensure they have the necessary permissions.
  
  
  
  Review Authorization Objects:
  
  Identify the relevant authorization objects that are required for the transaction or process. This can often be found in the documentation or by consulting with a security administrator.
  Ensure that the necessary authorizations are assigned to the user.
  
  
  
  Consult with Security Team:
  
  If you are not able to resolve the issue, consult with your SAP security team or basis team. They can help analyze the authorization logs and make necessary adjustments.
  
  
  
  Check Custom Code:
  
  If the error is occurring in a custom program, review the code to ensure that it is correctly implementing authorization checks. You may need to debug the program to identify where the issue lies.
  
  
  
  Testing:
  
  After making changes to authorizations or configurations, 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: Familiarize yourself with the relevant authorization objects for the specific transactions you are working with. Common objects in CO include K_AUSW (Authorizations for CO) and others depending on the specific functionality.
  Documentation: Refer to SAP Help documentation for detailed information on authorization checks and best practices for managing user roles and permissions.
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.