Subsequent Implementation of Ledgers (Scenarios 7 and 8)

Use

You already use new General Ledger Accounting in your production system, and now you want to do the following:

  • Implement an additional accounting principle

  • Portray an additional reporting view in a separate ledger

  • Replace the account approach with the ledger approach

  • Discontinue using a special purpose ledger that you do not use for parallel accounting

  • Assign an existing company code to an existing ledger

    Note Note

    The subsequent implementation of a ledger always entails the assignment of a company code to the ledger. Consequently, the decisive time for the implementation of a ledger is not the time when the ledger is created but rather the time when a company code is assigned to the ledger.

    End of the note.

In each of the above cases, you need to add a non-leading ledger. The SAP General Ledger Migration Service assists you in doing this.

To portray an additional accounting principle or an additional reporting view, you need to implement an additional ledger. For this, you use scenario 7 in the Migration Cockpit.

To replace the account approach with the ledger approach, you use scenario 8 in the Migration Cockpit.

Note Note

If, apart from wanting to use scenario 7 or 8, you also want to use scenario 6 (to implement document splitting subsequently), you need to perform two projects consecutively.

End of the note.

Integration

Scenarios 7 and 8 help you in particular when you want to add a ledger in classic Asset Accounting (FI-AA).

Prerequisites

The following prerequisites must be met:

  • New General Ledger Accounting is active in your system.

  • The currencies required in the new ledger are already updated in the leading ledger.

    If this is not the case, you need to request from the System Landscape Optimization (SLO) a service for adding a new currency before you implement the new ledger. (See also: support.sap.com/slo.)

  • The General Ledger Accounting scenarios required in the new ledger as well as any customer fields are already assigned to at least one of the existing ledgers from which data can be copied. If data is copied from an existing ledger that is a non-leading ledger, the company codes that are relevant for the new ledger are also assigned to this existing ledger.

  • The Migration Cockpit is required to build the data of a subsequently implemented ledger.

Key Features

One ledger in new General Ledger Accounting is the leading ledger. In general, this ledger is used to portray group accounting. To portray different accounting principles in parallel, you can use other ledgers in addition to the leading ledger to portray different postings to the same accounts as required by the different accounting principles. Using ledgers for parallel accounting purposes is referred to as the ledger approach in new General Ledger Accounting.

With scenarios 7 and 8, you assign the company codes to the new ledger on the migration date or before the first postings are made in the new fiscal year. As a consequence, all ledger-independent documents from phase 1 (see Phase Model for the Migration) can be posted to the new ledger, and only the documents that had already been posted at the time of the assignment then need to be migrated later.

The system explicitly prevents updates from being made to old fiscal years.

Both scenarios contain functions for building opening balances for the new ledger.

Constraints

You cannot use scenarios 7 and 8 for the following purposes:

  • To introduce new account assignments

  • To introduce additional currencies

  • To implement new scenarios for General Ledger Accounting

  • To change the leading ledger

    You can only add a non-leading ledger; it is not possible to change the leading ledger.

  • To post documents from FI-SL subsequently

You cannot implement document splitting subsequently in scenarios 7 and 8. Instead, you have to do this in a separate project using migration scenario 6.

If you create a new ledger with a non-calendar fiscal year, the same restrictions apply as those for migration scenarios 4 and 5.

You cannot use migration scenario 8 to replace an existing account approach with the ledger approach in the component SAP Treasury and Risk Management (TRM).

Activities

The following sections describe the activities necessary