How To Fix FGL_PRE_CHECK006 - Real-time integr. CO-FI: Ledger group &1 does not contain leading ldgr &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FGL_PRE_CHECK - Pre Transition Check FI-GL

• Message number: 006

• Message text: Real-time integr. CO-FI: Ledger group &1 does not contain leading ldgr &2

What causes this issue?

In the customizing of the real-time integration of CO-FI the ledger
group &V1& is used.

System Response

The ledger group &V1& doesn't contain leading ledger &V2&.
This means that the leading ledger can't 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: In other words, CO has to store its data in a G/L ledger. This
G/L ledger must be the leading ledger.
The customizing migration program evaluates the customizing of the
real-time integration of CO-FI in order to check whether the leading
ledger contains all CO postings: That is, primary postings from FI and
secondary postings from CO (such as repostings and allocations between
cost centers).
<ZH>After the migration, the secondary postings from CO will also be
posted into the leading ledger</>.

How to fix this error?

Keep in mind that these additional postings into the leading ledger will
affect the data displayed in financial reports.

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 FGL_PRE_CHECK006 - Real-time integr. CO-FI: Ledger group &1 does not contain leading ldgr &2 ?

  The SAP error message FGL_PRE_CHECK006 indicates that there is an issue with the integration between Controlling (CO) and Financial Accounting (FI) in the context of real-time integration. Specifically, the error states that the specified ledger group does not contain the leading ledger.
  Cause:
  This error typically occurs when:
  
  The ledger group specified in the error message does not include the leading ledger that is required for real-time integration between CO and FI.
  The configuration of the ledger groups in the system is incorrect or incomplete.
  The leading ledger is not assigned to the specified ledger group in the configuration settings.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Ledger Group Configuration:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to Financial Accounting (New) > General Ledger Accounting (New) > Ledger > Define Ledger Groups.
  Verify that the leading ledger is included in the specified ledger group.
  
  
  
  Assign Leading Ledger:
  
  If the leading ledger is not assigned to the ledger group, you will need to add it.
  Ensure that the leading ledger is correctly configured and assigned to the appropriate ledger group.
  
  
  
  Check Company Code Settings:
  
  Ensure that the company code is correctly assigned to the ledger group and that the leading ledger is active for that company code.
  
  
  
  Review Real-Time Integration Settings:
  
  Check the settings for real-time integration between CO and FI to ensure that they are correctly configured.
  This can be found under Controlling > Integration with Financial Accounting.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, perform a test to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Leading Ledger: The leading ledger is the primary ledger used for financial reporting in SAP. It is essential for ensuring that all financial transactions are recorded accurately and consistently.
  Ledger Groups: Ledger groups are used to group different ledgers for reporting and integration purposes. They allow for flexibility in financial reporting and can include multiple ledgers.
  Real-Time Integration: This feature allows for immediate posting of financial transactions in both CO and FI, ensuring that data is synchronized across modules.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or functional team for further investigation or to check for any additional configuration settings that may be affecting the integration.