How To Fix FQ809 - Coding block not possible: G/L account not filled

SAP Error Message - Details

• Message type: E = Error

• Message class: FQ - Payment Requests and Payment Program

• Message number: 809

• Message text: Coding block not possible: G/L account not filled

What causes this issue?

To be able to display the coding block, you need a G/L account. The
corresponding field, however, does not have an entry in it in the line
item you have chosen.

System Response

The coding block cannot be displayed.

How to fix this error?

First set the G/L account. You do this by making an FM account
assignment from which the G/L account is derived.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FQ809 - Coding block not possible: G/L account not filled ?

  The SAP error message FQ809, which states "Coding block not possible: G/L account not filled," typically occurs in the context of financial transactions, particularly when dealing with document postings in the SAP system. This error indicates that the system is unable to process a transaction because the General Ledger (G/L) account has not been specified or is missing in the relevant coding block.
  Cause:
  
  Missing G/L Account: The most common cause of this error is that the G/L account field is not filled in the transaction or document you are trying to post.
  Incorrect Configuration: There may be issues with the configuration of the financial document types or the account determination settings.
  Transaction Type: The transaction type being used may not be set up to allow postings without a G/L account.
  User Input Error: The user may have inadvertently skipped the G/L account field while entering the transaction.
  
  Solution:
  
  Check G/L Account Entry: Ensure that the G/L account field is filled in the transaction. If you are entering a manual journal entry or a similar transaction, make sure to specify the correct G/L account.
  Review Configuration: If you are an SAP administrator, check the configuration settings for the relevant document types and account determination settings to ensure they are set up correctly.
  Transaction Type Settings: Verify that the transaction type you are using allows for the entry of a G/L account. You may need to adjust the settings if necessary.
  User Training: If the issue is recurring due to user error, consider providing additional training or documentation to users on how to properly enter transactions in SAP.
  Debugging: If the issue persists, you may need to debug the transaction to identify any underlying issues in the code or configuration that could be causing the error.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB50 (G/L Account Document Entry) or F-02 (General Ledger Posting) to understand where the error might be occurring.
  User Roles and Authorizations: Ensure that the user has the necessary roles and authorizations to post transactions involving G/L accounts.
  
  If the problem continues after following these steps, it may be beneficial to consult with your SAP support team or a professional with expertise in SAP Financials for further assistance.