Subsequent Implementation of an Additional Ledger (Scenario 7)

Purpose

You use this process when you already use new General Ledger Accounting in your production system and want to implement an additional, non-leading ledger subsequently (migration scenario 7).

Prerequisites

To be able to build the data of a subsequently implemented ledger, you need to use the Migration Cockpit with scenario 7 .

For a full list of the prerequisites, see Subsequent Implementation of Ledgers (Scenarios 7 and 8) .

Process Flow

As with all migration scenarios, an additional ledger is implemented subsequently using the phase model , which comprises phases 0 to 2:

The following table provides a summary of the activities that are necessary in the different phases:

Phase 0

Preparation

Phase 1

Phase 2

Migration

  • Plan the subsequent implementation of an additional ledger (especially for phase 2)

  • Create a new ledger (such as L1) and a new ledger group (such as L1)

  • Make Customizing settings for the migration

  • Assign company codes to the new ledger

  • Prepare FI-AA

  • Make year-end closing postings in the old fiscal year

  • Make ordinary postings in the new fiscal year

  • Close the old fiscal year

  • If necessary, build the missing general ledger view for the new ledger

  • Copy opening balances from a suitable source ledger (for accounts not managed on an open item basis)

  • Build balance carryforward from accounts managed on an open item basis as well as reconciliation accounts for the new fiscal year

  • Make any necessary adjustments to Customizing settings for FI-AA and other components

  • If none yet exist, build new depreciation areas (for FI-AA, foreign currency valuation, and other components)

For the migration date and the activation date, the following applies:

  • The migration date is always the first day of the current fiscal year or of a future fiscal year. If you use Asset Accounting, the migration date must not fall before a depreciation run that has already been performed. We recommend opting for the first day of a forthcoming fiscal year.

    If you cannot follow this recommendation, it is not possible to portray the asset values by period in the new ledger before the activation date because the asset values in the new ledger are summarized for the current period in Asset Accounting.

  • The activation date falls after year-end closing for the old fiscal year.

    As of the activation date, the old fiscal year must be closed for postings. In this way, the values for the balance carryforward can no longer be changed, and the balances and items of the new ledger can now be built completely. You can then use the new ledger to create periodic reports.

    In the transition phase from the first day of the fiscal year and up to the activation date, postings can be made to the old fiscal year as well as to the new fiscal year. Once the Customizing settings for the migration and for the ledger have been made in the production system, postings in the new fiscal year are updated online to the new ledger. Ledger-specific postings can be made to the new fiscal year. However, ledger-specific postings that only contain the subsequently implemented ledger cannot be made to the old fiscal year. This reduces the effort required to build the documents (in migration phase 1) in the subsequently implemented ledger.