How To Fix FAGL_SWITCH_LEAD_LDG106 - Documents exist in company code &1 as of fiscal year &2

FAGL_SWITCH_LEAD_LDG106 - Overview

• Message type: E = Error

• Message class: FAGL_SWITCH_LEAD_LDG - Technical Changeover of Leading View in General Ledger (New)

• Message number: 106

• Message text: Documents exist in company code &1 as of fiscal year &2

What causes this issue?

The future leading ledger is not implemented in company code &V1&.
However, postings in the fiscal year (&V2&) relevant for the ledger
switch exist in this company code.

System Response

The switch project cannot be activated.

How to fix this error?

Implement the future leading ledger in all company codes in which it is
missing. To do this, use the SAP General Ledger Migration service. For
more information, see <LS>SAP Service Marketplace </>at <LS>
http://service.sap.com/GLMIG </>and SAP Library under <ZK>General Ledger
Accounting (FI-GL) </>-> <ZK>Configuring General Ledger Accounting </>->
<ZK>Migration to General Ledger Accounting </>-> <ZK>Migration
Scenarios </>-> <ZK>Migration Scenarios for Subsequent Implementation of
Functions </>-> <ZK>Subsequent Implementation of Ledgers (Scenarios 7
and 8) </>-> <ZK>Subsequent Implementation of an Additional Ledger
(Scenario 7)</>.

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.

FAGL_SWITCH_LEAD_LDG106 - Details

• The SAP error message FAGL_SWITCH_LEAD_LDG106 indicates that there are existing documents in a specified company code for a given fiscal year, which prevents the system from switching to the new General Ledger (G/L) accounting. This typically occurs when you are trying to activate the new G/L functionality in SAP, but there are still financial documents that have not been processed or cleared in the specified company code and fiscal year.
  
  Cause:
  
  Existing Documents: There are financial documents (like invoices, journal entries, etc.) that exist in the specified company code for the fiscal year mentioned in the error message.
  Open Items: There may be open items in accounts that have not been cleared or processed.
  Inconsistent Data: The data in the system may not be consistent with the requirements for switching to the new G/L.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify Existing Documents:
  
  Use transaction codes like FB03 (Display Document) or FBL1N/FBL3N/FBL5N (Vendor/Customer/GL