Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: FAGL_CL - Cash Ledger
Message number: 006
Message text: G/L account &1 &2 does not exist in G/L account master record
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.
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.
FAGL_CL006
- G/L account &1 &2 does not exist in G/L account master record ?The SAP error message FAGL_CL006 indicates that a General Ledger (G/L) account specified in a transaction does not exist in the G/L account master record. This error typically occurs when trying to post a transaction that references a G/L account that has not been created or is not active in the system.
Cause:
- Non-Existent G/L Account: The G/L account specified in the transaction does not exist in the system.
- Inactive G/L Account: The G/L account exists but is marked as inactive or has been deleted.
- Incorrect Account Number: There may be a typo or incorrect account number being used in the transaction.
- Company Code Issues: The G/L account may not be defined for the specific company code being used in the transaction.
- Chart of Accounts: The G/L account may not be assigned to the chart of accounts that is being used.
Solution:
- Check G/L Account: Verify that the G/L account number specified in the transaction is correct. Ensure there are no typographical errors.
- Create or Activate G/L Account:
- If the G/L account does not exist, create it using transaction code FS00 (G/L Account Master Record).
- If the account exists but is inactive, you may need to activate it or check its status.
- Verify Company Code: Ensure that the G/L account is set up for the correct company code. You can check this in the G/L account master record.
- Check Chart of Accounts: Make sure that the G/L account is assigned to the correct chart of accounts that is being used in your company code.
- Consult with Finance Team: If you are unsure about the account setup, consult with your finance or accounting team to ensure that the correct accounts are being used.
Related Information:
By following these steps, you should be able to resolve the FAGL_CL006 error and successfully post your transaction.
Get instant SAP help. Sign up for our Free Essentials Plan.
FAGL_CL005
No more than one payment-relevant item permitted per document
What causes this issue? You activated a cash ledger in the general ledger. In this case, only one payment-relevant item is permitted per document.Sys...
FAGL_CL004
Cash ledgers &1 and &2 are assigned to different totals tables
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_CL007
G/L account &1 in company code &2 is a reconciliation acct
What causes this issue? A reconciliation account cannot be defined as a general ledger account.System Response The system issues an error message an...
FAGL_CL008
G/L acct &1 in company code &2 is not relevant for financial transaction
What causes this issue? You want to define a G/L account, which is not relevant for financial transactions, as cash relevant. This is not permitted....
Click on this link to search all SAP messages.