How To Fix FARR_BIZ_RECON008 - No authorization for Company Code &1 and Accouting Principle &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_BIZ_RECON -

• Message number: 008

• Message text: No authorization for Company Code &1 and Accouting Principle &2

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 FARR_BIZ_RECON008 - No authorization for Company Code &1 and Accouting Principle &2 ?

  The SAP error message FARR_BIZ_RECON008 indicates that a user does not have the necessary authorization to perform a transaction related to a specific Company Code and Accounting Principle. This error typically arises in the context of Financial Accounting and Asset Accounting modules.
  Cause:
  
  Missing Authorizations: The user lacks the required authorization for the specified Company Code and Accounting Principle.
  Role Configuration: The user's role may not be configured correctly to include the necessary permissions for the specified Company Code.
  Authorization Object: The relevant authorization object (e.g., F_BKPF_BES, F_FAA_AKT, etc.) may not be assigned to the user's profile.
  Company Code Settings: The Company Code may have specific settings that restrict access based on user roles.
  
  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 is missing.
  Alternatively, you can use transaction SU01 to view the user's roles and authorizations.
  
  
  
  Modify User Roles:
  
  If you have the necessary permissions, you can modify the user's roles to include the required authorizations for the Company Code and Accounting Principle.
  If you do not have the necessary permissions, contact your SAP security administrator to request the required authorizations.
  
  
  
  Review Authorization Objects:
  
  Ensure that the relevant authorization objects are included in the user's roles. Common authorization objects for financial transactions include:
  
  F_BKPF_BES (Authorization for Document Management)
  F_FAA_AKT (Authorization for Asset Accounting)
  
  
  Make sure that the Company Code and Accounting Principle are included in the authorization object settings.
  
  
  
  Testing:
  
  After making changes to the user's roles or authorizations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Documentation:
  
  Document any changes made to user roles and authorizations for future reference and compliance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  
  
  Authorization Management: Understanding how to manage and assign authorizations in SAP is crucial for maintaining security and compliance.
  SAP Notes: Check SAP Notes for any known issues or updates related to authorization errors.
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.