Scribd
Upload
58 views2 pages

Subsequent Implementation of A New General Ledger

Uploaded by

huokeqiang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
58 views2 pages

Subsequent Implementation of A New General Ledger

Uploaded by

huokeqiang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SAP Note

1378630 - Subsequent implementation of a new general ledger


Component: FI-GL-MIG (Financial Accounting > General Ledger Accounting > general ledger migration),
Version: 3, Released On: 12.01.2022

Symptom
You use General Ledger Accounting (new), and you want to implement a new ledger as of a
future fiscal year. You are not sure why you require the migration service for scenario 7.

Other Terms
General Ledger Accounting (new), FI-GL (new)

Solution
You must execute several steps in a predefined sequence to ensure you have consistent data
in the new general ledger as of the new fiscal year.
1. You must ensure that all documents of the new fiscal year that are relevant for the
new ledger to be inmplemeted are updated in this ledger. However, you are not permitted
to update documents for the old fiscal year (for example, closing entries) in the new
general ledger. The closing of the old fiscal year usually takes several weeks of the
new calendar year. During this time, postings are also made for the new fiscal year.
After you create the new ledger and assign the relevant company codes to this ledger,
there must be a differentiation between documents of the old and new fiscal year during
the update. This differentiation is made automatically based on migration customizing
for scenario 7.
2. You must create an opening balance in the new ledger. To do so, you must transfer the
balance carryforward values from a suitable source ledger after the year-end closing in
the source ledger to the new ledger. Relevant reports are available for a transfer like
this as part of migration scenario 7. The opening balances for accounts managed on an
open item basis must correspond to the account assignment levels (for example, segment)
relevant to the new ledger with the total of all existing open items. For this reason,
the opening balances are determined by totaling all existing open items, and are set in
the new ledger. In the majority of cases, you cannot manually post these balance
carryforward values because many of these accounts (for example, reconciliation accounts
for customers or vendors) cannot be posted to manually. For all accounts not managed on
an open item basis, a second report is used to transfer balance carryforward values from
a suitable source ledger.
3. As a result, you may also have to create a new valuation area in Asset Accounting in
connection with the implementation of a new ledger. Migration scenario 7 supports the
execution of all required steps for the correct creation of a valuation area of this
type that is compatible with the new ledger.
In SAP ERP, in General Ledger Accounting (new) with migration scenarios 7 and 8, you can
subsequently implement a new ledger and subsequently switch from the accounts approach to
the ledger approach. These migration scenarios are supported in classic Asset Accounting,
but not in Asset Accounting (new).
Note the following: The SAP General Ledger Migration service does not provide a service for
the SAP S/4HANA system. To receive the current update of the available scenarios for the SAP
S/4HANA system, create an incident with the component FIN-MIG-GL.
This document refers to
SAP Component Title
Note/KBA

2405554 FI-GL-MIG- Incompatibility between Standard Migration Scenarios (Scenario : 7 & 8) and active New Asset
TL Accounting

2403248 FI-AA FI-AA (new): Availability of RAFABNEW

1619168 FI-GL-MIG Overview of the different migration scenarios

This document is referenced by


SAP Note/KBA Component Title

1619168 Overview of the different migration scenarios

You might also like