SAP ABAP IMG Activity FAGL_VC_FAGL_MIG_A (Define and Assign Migration Plan)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-GL (Application Component) General Ledger Accounting
     ⤷ FAGL_MIG_CUST (Package) Customizing for Migration
IMG Activity
ID FAGL_VC_FAGL_MIG_A Define and Assign Migration Plan  
Transaction Code S_AC0_52000508   (empty) 
Created on 20050217    
Customizing Attributes FAGL_VC_FAGL_MIG_A   Define and Assign Migration Plan 
Customizing Activity FAGL_VC_FAGL_MIG_A   Define and Assign Migration Plan 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FAGL_VC_FAGL_MIG_A    

Use

Here, you define a migration plan to migrate your data into New General Ledger Accounting. The migration plan contains all company code and ledger objects that are to be migrated together for the company codes and ledgers assigned to the migration plan.

Requirements

Standard settings

SAP does not deliver standard migration plans. Nevertheless, the Migration Cockpit contains two templates that you can copy and adjust.

Activities

To define a migration plan, proceed as follows:

Create Migration Plan:

  1. Enter a technical key and a name for your migration plan. Do not use any special characters.
  2. Specify a migration date and select the type of migration plan.

    The system sets the indicator determining whether a migration plan has started or has already ended. If you do not use the standard programs for creating worklists, you can use the IMG activity Activate Migration Plan to mark them as started.

Make Assignments:

  1. To each migration plan, you assign the company code(s) and ledger(s) containing objects that you would like to be migrated together. Note the following:
    • The last day of the fiscal year variant of the company code or ledger must agree with the migration date (minus a day). For more information and an example, see under Migration Date.
    • You can assign company codes and ledgers to several migration plans. However, you cannot assign the same combination of company code and ledger to more than one migration plan at the same time, independently of whether the migration plans have already started. There must be no more than one migration running for each combination of company code and ledger. Only once the migration in question has ended can you assign the same combination of company code and ledger to a different migration plan.
    • Once you have assigned company codes and a ledger to a migration plan, you cannot change the migration type and the migration date. However, provided the migration has notyet started, you can delete all assignments, which then allows you to make changes to the properties of the migration plan.
  2. Save your entries.

    Note:
    Note that, when you delete a migration plan, you automatically delete all the assignments with it.

Activate Validation:

You make this setting for your migration plan if you want to use document splitting.
You can also call up this table in the section on validation under Define Validation.
For more information, see Validation of Document Splitting.

Example

Business Attributes
ASAP Roadmap ID 152   Design data acquisition 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG FAGL_VC_FAGL_MIG_A 0 HLA0006520 Basic Functions 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_FAGL_MIG_A C - View cluster SM34  
History
Last changed by/on SAP  20050217 
SAP Release Created in 600