Data Migration Plan v1.1 - 20100607
Data Migration Plan v1.1 - 20100607
Data Migration Plan v1.1 - 20100607
Ver.1
7 June 2010
© Emergys Corp.
Prepared by : B. KATHIRAVAN
[email protected]
Reviewed by : T. JAYAKUMAR
[email protected]
Master Data
Transactional Data
LSMW R2R Objects & Templates
Data Migration Strategy: ETLV
• Extract Data from Source System
• Transform Data for the Target System
• Load Data in to the Target System
• Validate the Data Loads
When and Where – Data Load Cycles
Data Migration – Activity and Status Reporting
Back-up Charts
• Template for Data Mapping
• Preload Checklist
• Data Migration Status Summary Sheet
• Weekly Status Report
Note :
Templates Owner B. KATHIRAVAN
Client
Maintain Log of Data Extraction for each object
Control Totals on the number of Records extracted
Sampling of extracted data for accuracy and confirmation to mapping
Maintain screen shots of sample data for validating after completion of data
load into SAP
Load the extract files in shared space
Emergys
Accept Input data from shared space
Validate for confirmation with field order and format as per baseline Template
Both
Maintain Access restrictions to shared space
Persons Responsible
– Emergys SMEs / Client SMEs (Mapping for Process)
– Emergys Data Team / Client IT team (Template/Tools)
Emergys
– Check-in Baseline Templates for each Cycle at Confluence Space
– Identify Data Impacts for any Process or Configuration changes
– Maintain and Version control for changes to Data Mapping Templates
Client
– Develop and Maintain Baseline Templates for each Cycle with respect
to Legacy system
Record data extract and conversion logic
• Data Cleansing – Identify and Document the process
Log of additional data elements manually added
Using the automatic programs to load data into SAP system. In Case of
exceptions, manual load may be required.
Persons Responsible
Emergys Data team
Emergys
– Maintain List of Data Migration Program (LSMW) objects
– Source files to be read only from Shared space
– Verify number of records read and tally with input count
– Verify number of records converted into intermediate format
– Create and Run the Batch or Direct Input Program
– Maintain screen shots of Batch or Direct Input Program results
– Load Error report and Analysis into shared space for Client-IT
– Repeat the above steps until successful execution of data load
– Log results into the Summary sheet
Client
– Obtain Error report and correct data
Validate the Master Data in SAP and confirm that it reflects the desired
values
Persons Responsible
Emergys SMEs / Client SMEs
Emergys data team / Client IT team
Client
– Verify reports and tally number of records migrated for each object
– Random checking of migrated data using SAP transactions and capture
screen prints – SMEs
• Execute and validate for the Sample data identified in extract process
– Execute Listing reports and compare with input data
– Log results of validation for audit trail
Cycle 1: DEV/210
– Realization
– Sand Box
Cycle 2: QAS/300
– Integration / UAT
– Test Box
Cycle 3: PRD/400
– Go Live
– Production Box
• Assumptions tab contains high level assumptions like if it’s proposed to use Internal
numbering or transfer legacy material number as the Material number SAP system
also
• Material Master Basic tab contains the format in which the input data is to be
provided
• Field definitions tab contains the detailed mapping structure for each field and its
impact to the SAP process
• Other tabs lists out the important configuration data used to reference the material
specific to Client
Preload Validation Checks on each input data file before loading the same into SAP
Verify the File received and type of the file as reported by Client IT team
Convert the file into Tab Delimited text type if received as Excel data
Visual verification of the same to confirm the content is as per the appropriate template format
Verify and change the name of the file to match the specification in the data upload program
Ensure the file is placed in the appropriate directory as expected by the data upload program
Following validation checks are done at the start of each Data Load Cycle
Receive notification from Project Manager on the readiness of SAP Client and its details
Verify all Data upload Program (LSMW) objects are available in the client
Random Checks of a few tables using SE16 to ensure that Master and Transaction data tables are
empty
Confirm with Project Manager the client specific Configuration objects to be loaded initially are
loaded
• All Master and Transaction objects as identified for Data Migration activity
shall be included in the sheet