Migration Cockpit

Definition

Working environment for the migration to new General Ledger Accounting.

Use

The General Ledger Migration Cockpit is based on the most frequent standard scenarios for the migration. It is the framework in which you create your special migration scenario, guiding you through each migration step. The cockpit provides a process flow structure (process tree) containing the activities performed during the migration and it also provides a monitor enabling you to monitor the status of the migration. The process flow structure is created in your SAP system once you create a migration pack.

To start the Migration Cockpit , call transaction CNV_MBT_NGLM.

Besides the cockpit, the SAP General Ledger Migration Service contains two service sessions that are delivered remotely:

  • Session for scenario validation and system analysis

    This session is used to check whether the migration scenario you have selected and ordered is adapted to your system configuration. In this way, the session ensures that you apply the correct migration approach.

  • Session for the test validation

    This session is used to perform technical plausibility checks in a migrated test system to ensure the integrity of the data after it has been migrated.

For more information on these service sessions, see SAP Service Marketplace at http://service.sap.com/GLMIG.

Structure

The Migration Cockpit offers the following to assist you in performing the migration activities as part of a structured and efficient process:

  • Migration Overview

    When you call transaction CNV_MBT_NGLM, the migration overview screen ( Migration Server Overview ) appears. From here, you can perform all activities that do not belong to a specific migration pack. For example, you can create a project or migration pack or register selected users.

    On the overview screen, all projects and packs found for the current client are listed. You can access any of the objects listed, provided you have appropriate authorization and are registered for the object in question.

  • Process Flow Structure (Process Tree)

    Once you have created a new migration pack, the cockpit appears for this pack. It contains the process flow structure, a list of the activities that need to be performed for that migration pack, as well as a monitor providing the information you need in order to monitor the progress of the migration. From the cockpit, you can also access logs detailing the activities performed in this pack.

Activities

The following types of activities are available:

  • Activities that are executed

    On the basis of the requirements pertaining to the activity in question, this function either starts a program in the background or calls a selection screen in which you make the required entries. To perform a function, select the desired activity and choose Execute .

  • Activities requiring confirmation

    Once you have read the documentation for an activity and have undertaken all necessary measures, select the activity in the process flow structure and choose Execute . A dialog box appears, enabling you to confirm completion of the activity. Activities that require confirmation are used for documentation purposes.

  • Activities for information purposes

    These activities only contain documentation but no functions. The documentation contains important information about the current status of your migration project and tips regarding activities that do not appear in the process flow structure.

User Roles and Registration Functions

The Migration Cockpit has the following user roles:

  • Lead

  • Guest

Depending on whether role SAP_NGLM_MASTER or role SAP_NGLM_USER is assigned to a user, the system automatically assigns the role Lead or Guest in the Migration Cockpit . SAP delivers the roles SAP_NGLM_MASTER and SAP_NGLM_USER with the Migration Cockpit .

Moreover, the Migration Cockpit contains registration mechanisms for the different organizational levels in the project. This is particularly useful when more than one migration is performed in parallel in a system environment and when not all users are involved in all of the migrations.