Solution : https://service.sap.com/sap/support/notes/1158830 (SAP Service marketplace login required)
Summary :
When planning or executing a new G/L migration, it's crucial to maintain security by continuing to update the GLT0 table along with new G/L tables during the transition. While migrating to new general ledger (G/L) accounting, transaction FAGL_ACTIVATION will simultaneously keep classic G/L totals records updated. It is critical to note that the READ_GLT0 parameter should not be activated in live systems with new G/L accounting to avoid incorrect account assignments and inconsistencies from valuation reports drawing data from GLT0. Additionally, appropriate settings for the user parameter FAGL_READ_GLT0_USER are advised, with strict limitations on manual postings and reporting. SAP's Note 1155999 introduces the CLASSIC_BAL_FS10N parameter for evaluating GLT0 balances through FS10N, requiring the WRITE_GLT0 indicator to be active. Post-migration, it is recommended to deactivate the GLT0 updates at fiscal year-end to prevent data variances and follow specific IMG paths to ensure the deactivation.
Key words :
write classic general ledger, read classic general ledger, financial accounting global settings, classic general ledger accounting, classic general ledger, general ledger accounting, incorrect account assignments, local currency changeover, cross-application activity, create message fagl_ledger_cust 084
Related Notes :
| 1619168 | Overview of different migration scenarios |
| 1339877 | FI-GL (new): Euro currency changeover and WRITE_GLT0 |
| 1155999 | FS10N: Displaying 'classic' balances when new G/L is active |
| 1021174 | FS10N: Drilldown -> differences despite Note 970096 |