How To Fix FKK_DISCO022 - No authorization for company code object. See log for details.

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_DISCO - Service Disconnection and Reconnection

• Message number: 022

• Message text: No authorization for company code object. See log for details.

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 FKK_DISCO022 - No authorization for company code object. See log for details. ?

  The SAP error message FKK_DISCO022 indicates that a user does not have the necessary authorization for a specific company code object in the context of contract accounts receivable and payable (FI-CA). This error typically arises when a user attempts to perform an action that requires access to a company code for which they do not have the appropriate permissions.
  Cause:
  
  Missing Authorizations: The user lacks the necessary authorization objects related to the company code in question.
  Role Assignment: The user’s role may not include the required authorizations for the specific company code.
  Profile Issues: The user profile may not be correctly configured to include the necessary access rights.
  Company Code Restrictions: The company code may have specific restrictions or settings that limit access.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to analyze the authorization check. This will show which authorization object is missing.
  Review the authorization logs to identify the specific missing authorizations.
  
  
  
  Modify User Roles:
  
  If you have the necessary permissions, go to transaction PFCG to modify the user roles.
  Ensure that the role assigned to the user includes the necessary authorization objects for the company code in question (e.g., F_SKA1_AKT, F_SKA1_BER, etc.).
  
  
  
  Assign Missing Authorizations:
  
  If the user needs access to a specific company code, ensure that the relevant authorizations are added to their profile.
  You may need to work with your SAP security team to ensure that the user is granted the appropriate access.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the transaction again to confirm that the issue is resolved.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP Basis or Security team for specific authorization objects related to FI-CA and company codes.
  
  
  
  Related Information:
  
  
  Authorization Objects: Common authorization objects related to company codes include:
  
  F_SKA1_AKT (Company Code: Activity)
  F_SKA1_BER (Company Code: Authorization for Business Transactions)
  
  
  
  Transaction Codes:
  
  SU01: User maintenance
  SU53: Display authorization check
  PFCG: Role maintenance
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance on authorization management.
  
  
  If the problem persists after following these steps, it may be necessary to engage with your SAP support team for further investigation.