3730814 - Balance carryforward does not copy GC amounts to LC when changing LC to same as GC for Consolidation Unit in next year

When changing the local currency (LC) of consolidation units to USD (same as group currency, GC) in new year, some closing balances of GC line items are not copied to LC . 

A consolidation method was configured to carry forward GC to LC without translating LC with closing exchange rates, but some line items remain with LC = 0.

SAP S/4HANA Cloud Public Edition

1. Set up a consolidation unit with LC in the prior year (for example, LC = GBP in 2024) and GC = USD.
2. Change the LC to USD from the new year (for example, from 2025), resulting in LC = GC = USD.
3. Configure a consolidation method for the units.
4. Ensure there are prior-year postings (document in 2024) have amounts only in GC (LC is zero).
5. Run Balance Carryforward for the first period of the new year 2025.
6. Observe that  line items with GC-only amounts are not copied to LC (LC remains zero), creating LC vs GC mismatches.

This is expected results.

This is expected behaviors of current Group Reporting system. 

GC cannot be copies to LC after running BCF.

• refer to: 3146025 - Group Reporting: Different amount in LC and GC with the same currency in reported (released) data
• refer to: 3683805 - Balance carry forward does not carry group currency data
• refer to: 3670316 - Group Reporting: Multiple Group Currency scenario with LC = GC in standard (main) consolidation version

group reporting, balance carryforward, local currency change, lc equals gc, document type 18, gc-only posting, lc not copied, fs item mismatch, currency translation method, closing balances, lc=gc scenario, topside entries, consolidation unit, lc missing after bcf, gc to lc copy , KBA , FIN-CS-COR-BCF-2CL , Balance Carry Forward (Public Cloud) , Problem