How To Fix FINS_ACDOC_CUST099 - No suitable G/L ledger found for CO

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 099

• Message text: No suitable G/L ledger found for CO

What causes this issue?

There is no G/L ledger that has the same fiscal year variant for all
company codes that are assigned to a controlling area.

System Response

This means that the system can't determine a G/L ledger which could act
as ledger for CO data for all company codes.
Background:
In SAP S/4HANA Finance FI and CO share the same persistence for storing
postings: CO data is stored in a G/L ledger. The customizing migration
program evaluates the ledger settings to find a G/L ledger that can be
used for this purpose.
For some reports it's necessary that this ledger is the same for all
company codes.

How to fix this error?

You have the following options:
Either adjust the fiscal year variants of the controlling area, or
Define a ledger with a suitable fiscal year variant for all company
codes; then assign the CO version 000 manually to this ledger for all
company codes.

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 FINS_ACDOC_CUST099 - No suitable G/L ledger found for CO ?

  The SAP error message FINS_ACDOC_CUST099 indicates that there is no suitable General Ledger (G/L) ledger found for a Controlling (CO) document. This error typically arises when there is a mismatch or misconfiguration between the G/L accounts and the controlling area settings.
  Causes:
  
  Missing G/L Ledger Configuration: The G/L ledger may not be properly configured for the controlling area in question.
  Inconsistent Settings: The settings for the G/L account may not align with the controlling area settings, such as the ledger type or the account assignment.
  Inactive Ledger: The ledger that is supposed to be used may be inactive or not assigned to the company code.
  Document Type Issues: The document type used may not be compatible with the controlling area or the G/L account.
  Missing Assignment: The G/L account may not be assigned to the appropriate ledger in the configuration.
  
  Solutions:
  
  
  Check G/L Account Configuration:
  
  Go to the G/L account master data and ensure that the account is assigned to the correct ledger and controlling area.
  Verify that the account is active and properly configured.
  
  
  
  Review Controlling Area Settings:
  
  Check the settings of the controlling area in transaction code OKKP. Ensure that the G/L ledger is assigned correctly to the controlling area.
  Make sure that the ledger type is compatible with the controlling area.
  
  
  
  Verify Document Type:
  
  Ensure that the document type being used is compatible with the G/L account and controlling area settings.
  
  
  
  Check Ledger Assignment:
  
  Use transaction code OB22 to check the assignment of ledgers to company codes and ensure that the relevant ledger is active and assigned.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB22: Configuration for G/L account assignment to company codes.
  OKKP: Configuration for controlling area settings.
  FS00: G/L account master data maintenance.
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on G/L account and controlling area configuration.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary changes to resolve it.