How To Fix FISA_LOC390 - G/L account data for company code &1 and G/L account number &2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: FISA_LOC - FI Localization for KSA

• Message number: 390

• Message text: G/L account data for company code &1 and G/L account number &2 not found

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 FISA_LOC390 - G/L account data for company code &1 and G/L account number &2 not found ?

  The SAP error message FISA_LOC390 indicates that the system could not find the General Ledger (G/L) account data for a specific company code and G/L account number. This error typically arises in the context of financial transactions or reporting when the system is trying to access account information that is either missing or incorrectly configured.
  Causes:
  
  Missing G/L Account: The specified G/L account number does not exist in the system for the given company code.
  Incorrect Company Code: The company code specified may not be correctly associated with the G/L account.
  Inactive G/L Account: The G/L account may be inactive or not set up for the specified company code.
  Configuration Issues: There may be issues in the configuration of the G/L account in the chart of accounts or in the company code settings.
  Authorization Issues: The user may not have the necessary authorizations to access the G/L account data.
  
  Solutions:
  
  
  Verify G/L Account Existence:
  
  Check if the G/L account number exists in the system for the specified company code. You can do this by navigating to the G/L account master data in the SAP GUI (Transaction Code: FS00).
  
  
  
  Check Company Code Assignment:
  
  Ensure that the G/L account is properly assigned to the correct company code. This can also be checked in the G/L account master data.
  
  
  
  Activate G/L Account:
  
  If the G/L account is inactive, you may need to activate it or create a new G/L account that is active and properly configured.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the chart of accounts and ensure that the G/L account is correctly set up for the company code in question.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the G/L account. This may involve checking user roles and permissions in the SAP system.
  
  
  
  Consult Documentation:
  
  If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  FS00: G/L Account Master Data
  OBY6: Define Company Code
  OBD2: Assign G/L Accounts to Company Codes
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  
  User Forums: Consider visiting SAP community forums or user groups for additional insights and solutions from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the appropriate solution.