How To Fix FQME120 - Bank account &1 (technical ID) is not associated with a G/L account

SAP Error Message - Details

• Message type: E = Error

• Message class: FQME - Financial Quantity Management: Manual Entry Message Class

• Message number: 120

• Message text: Bank account &1 (technical ID) is not associated with a G/L account

What causes this issue?

The bank account is not associated to a G/L account due to one of the
following reasons:
There is no connectivity path of the central system category in the bank
account master data.
The G/L account is not defined in the connectivity path of the central
system category in the bank account master data.

System Response

An initial balance import for this bank account is not allowed. The
report is used to import the
initial balance for bank accounts operated in the central system.

How to fix this error?

To import balances for bank accounts mapped to a remote system,
use transaction
<DS:TRAN.FQM21>FQM21 (Import Bank Cash Balances)</>
To import initial balances for bank accounts operated in the central
system, define G/L accounts in the connectivity path in the bank
account master data.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FQME120 - Bank account &1 (technical ID) is not associated with a G/L account ?

  The SAP error message FQME120 indicates that a bank account is not properly associated with a General Ledger (G/L) account in the system. This can occur during various financial transactions, such as when trying to process payments or manage bank accounts in the SAP system.
  Cause:
  The primary cause of this error is that the bank account specified in the transaction is not linked to a corresponding G/L account in the system. This can happen due to:
  
  Configuration Issues: The bank account may not have been set up correctly in the system.
  Missing Assignments: The necessary assignment between the bank account and the G/L account has not been made.
  Data Entry Errors: There may be a typo or incorrect bank account number being used in the transaction.
  
  Solution:
  To resolve the FQME120 error, you can follow these steps:
  
  
  Check Bank Account Configuration:
  
  Go to the transaction code FI12 (or use the appropriate path in your SAP version) to check the configuration of the bank account.
  Ensure that the bank account is correctly set up and that all required fields are filled in.
  
  
  
  Verify G/L Account Assignment:
  
  In the bank account configuration, check if the bank account is assigned to a G/L account.
  If it is not assigned, you will need to create or modify the assignment. This can typically be done in the same configuration screen.
  
  
  
  Use Transaction Code OB40:
  
  You can also use transaction code OB40 to check and maintain the assignment of bank accounts to G/L accounts.
  Ensure that the bank account in question is listed and correctly linked to the appropriate G/L account.
  
  
  
  Check for Data Entry Errors:
  
  Review the transaction where the error occurred to ensure that the correct bank account number is being used.
  Correct any typos or incorrect entries.
  
  
  
  Consult Documentation:
  
  If you are unsure about the correct G/L account to use, consult your organization's financial documentation or speak with your finance team.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to ensure that the error has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FI12 (Bank Master Data), OB40 (G/L Account Assignment), and FBL1N (Vendor Line Item Display) for further investigation.
  User Roles: Ensure that you have the necessary permissions to make changes to bank account configurations and G/L account assignments.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message, as there may be updates or fixes provided by SAP.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in financial accounting within SAP.