How To Fix FAGL_SWITCH_LEAD_LDG123 - Update of classic G/L accounting (GLT0) is no longer possible

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 123

• Message text: Update of classic G/L accounting (GLT0) is no longer possible

What causes this issue?

In the settings for activating new General Ledger Accounting in
Customizing for <LS>Financial Accounting</>, <LS></> under <LS>Basic
Settings </>-> <LS>Tools </>-> <DS:SIMG.V_FAGL_ACTIVECCL></><LS>
Deactivate Update of Classic General Ledger (GLT0)</>, it has been
defined that, by default, balances in tables for classic General Ledger
Accounting (table GLT0) are to be updated in addition to the tables of
new General Ledger Accounting.
This default setting is there to enable you to use comparison reports
during the implementation phase of new General Ledger Accounting to
ensure that new General Ledger Accounting delivers correct results.
However, when the leading ledger is switched, this comparison is no
longer possible.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Deactivate the function for updating classic General Ledger Accounting
(GLT0) before you start a project to switch the leading ledger.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FAGL_SWITCH_LEAD_LDG123 - Update of classic G/L accounting (GLT0) is no longer possible ?

  The SAP error message FAGL_SWITCH_LEAD_LDG123 indicates that an update to classic General Ledger (G/L) accounting (specifically the table GLT0) is no longer possible. This typically occurs when a company has migrated to the new General Ledger (New G/L) functionality, which is part of the SAP S/4HANA suite or the newer versions of SAP ERP.
  Cause:
  
  Migration to New G/L: The primary cause of this error is that the system has been migrated from classic G/L accounting to the new G/L accounting. Once this migration is complete, the classic G/L tables (like GLT0) are no longer updated.
  Configuration Issues: There may be configuration settings that are not aligned with the new G/L setup, leading to attempts to post to the old tables.
  Data Consistency: The system may be trying to access or update data that is inconsistent with the new G/L structure.
  
  Solution:
  
  Check Migration Status: Ensure that the migration to the new G/L has been completed successfully. You can check the migration logs and reports to confirm this.
  Post to New G/L: Ensure that all postings are directed to the new G/L. This may involve changing the configuration in your posting documents or transaction codes to ensure they are compatible with the new G/L.
  Review Configuration: Check the configuration settings in the Financial Accounting (FI) module to ensure that they are set up for the new G/L. This includes checking the ledger settings, document types, and account determination.
  Consult Documentation: Refer to SAP documentation or notes related to the migration from classic G/L to new G/L for specific steps and considerations.
  Error Handling: If the error persists, consider using transaction codes like SLG1 (Application Log) to check for detailed error logs that can provide more context on the issue.
  
  Related Information:
  
  SAP Notes: Look for relevant SAP Notes that address this specific error message or provide guidance on the migration process. SAP Notes often contain important updates and fixes.
  Transaction Codes: Familiarize yourself with transaction codes related to G/L accounting, such as:
  
  OB52: To manage posting periods.
  OBY6: To configure the new G/L.
  FAGL_ACTIVATION: To activate the new G/L.
  
  
  Training and Documentation: Consider training sessions or documentation on the new G/L functionality to ensure that users are aware of the changes and how to operate within the new framework.
  
  If the issue continues after following these steps, it may be beneficial to consult with your SAP support team or a qualified SAP consultant for further assistance.