How To Fix FN002 - You are not authorized to display G/L accounts in company code &.

SAP Error Message - Details

• Message type: E = Error

• Message class: FN - BAPI Messages

• Message number: 002

• Message text: You are not authorized to display G/L accounts in company code &.

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 FN002 - You are not authorized to display G/L accounts in company code &. ?

  The SAP error message FN002, which states "You are not authorized to display G/L accounts in company code &," typically indicates that the user does not have the necessary authorization to view General Ledger (G/L) accounts for a specific company code in the SAP system. This is a common issue related to user roles and authorizations in SAP.
  Cause:
  
  Authorization Issues: The user lacks the required authorization object to access G/L accounts for the specified company code.
  Role Assignment: The user may not have been assigned the appropriate role that includes the necessary permissions.
  Company Code Restrictions: The user may have access to other company codes but not to the one specified in the error message.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error. This will show you the last authorization check and help identify which authorization object is missing.
  Review the authorization objects related to G/L account access, such as F_BKPF_BES (Accounting Document) and F_LFA1_APL (Vendor Master).
  
  
  
  Role Adjustment:
  
  If you have the necessary permissions, you can adjust the user's roles using transaction code PFCG. Ensure that the user has a role that includes the necessary authorizations for the company code in question.
  If you do not have the necessary permissions, contact your SAP security administrator or the person responsible for user management in your organization.
  
  
  
  Request Additional Access:
  
  If you determine that you need additional access, submit a request to your SAP security team to grant the necessary authorizations for the specific company code.
  
  
  
  Testing:
  
  After adjustments are made, log out and log back in to ensure that the changes take effect. Then, try to access the G/L accounts again.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to G/L accounts. Common objects include:
  
  F_BKPF_BES: Authorization for accounting documents.
  F_LFA1_APL: Authorization for vendor master data.
  F_SKA1_AKT: Authorization for G/L account master data.
  
  
  
  Transaction Codes:
  
  SU01: User maintenance (to check user roles).
  PFCG: Role maintenance (to modify or create roles).
  SU53: Display authorization check (to troubleshoot authorization issues).
  
  
  
  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 resolve the FN002 error and gain access to the G/L accounts as needed.