Sie sind auf Seite 1von 2

The main steps of the data conversion are:

Organization of the data conversion (Project manager & data conversion coordinator)
Data conversion plan
The WBS with workload estimates
The calendar planning with resources loading

Going on with the Business Objects data conversion (The resource responsible of the Business Object DC)

Data Purging and Cleansing


Mapping and conversion rules

Extract and Load Programs from rules


Data and Rules Adaptation (adjusting rules and programs following testing)

Load Unit Testing (unitary testing - small volume of manual data)


Extract and Load Full size testing (data test and validation - large volume with real extracted data)

Full data loading into ACCEPTANCE SYSTEM


Full data loading into PRE PRODUCTION SYSTEM

Validation of converted data and Key User + Business Objects Owner Signoff
Full conversion into PRODUCTION SYSTEM and final Signoff

Data Conversion Guidelines


1. Prepare the Legacy Database
a. Clean the data on your legacy system. It is easier to start from a sound legacy system than
trying to fix inconsistencies during the conversion. Delete obsolete data and make the rest of it
coherent. These two steps are called data purging and data cleansing.

2.

3.
4.
5.

This can be done without specific knowledge of SAP and can begin way before the project
Kick Off.
Before the last migration test run, take into account the customizations of the new system
a. Because both the organizational structure and the actual customizing influence the data you
transfer for business objects, finalize all customizations before the last test run. Customizing
changes after the final transferay result in additional required fields, this requires preparing
and transferring more data.
Reduce the amount of historical data to be transferred
Small is beautiful the first time you transfer data, begin with a few records of a business object
Play it safe it is suggested that a system backup (or client copy) is performed after transferring a
significant amount of data. The backup allows you to secure a specific level you have reached during
the data conversion process.

Step 1. Data Conversion Plan


What
Which business objects will be converted from the legacy system into SAP
(Masterdata, Transactional, Historical Data)
Where
Where are the data, which Legacy Systems are involved for the extraction.

How much
How

Estimate the number of records to be ultimately loaded into SAP.


There are two aspects to be considered :

The way data is extracted from the Legacy System


Automatically extracted from the Legacy system without manual intervention.

Manually filled spreadsheet


Combination of an automatic Legacy System extraction + Manual Entry into a
spreadsheet

The way data is injected into SAP :


Automatic data transfer from a flat file into SAP

Who

Manually entering data with online transactions into SAP

Combination of both
Who is involved on each Business Object :

Key user (Functional responsible of BO conversion : Rules, manual data corrections, test,
validations)
Consultant

Responsible of data cleaning and purging in the Legacy System


Responsible of the extraction

Responsible of loading data in SAP


Business Object Manager (Hierarchic owner who is responsible of day to day use and
integrity of information and the one which will be signing off for data acceptance )

Step 2. WBS

Suggested WBS content for data conversion

Volumes
Quantity of records
Quantity of fields
% Manual fields

Business Objects Mapping & Conversion


Data Purging and Cleansing

Mapping and conversion rules


Extract and Load Programs from rules

Data and Rules Adaptation (adjusting rules and programs following testing)
Load Unit Testing (unitary testing - small volume of manual data)

Extract and Load Full size testing (data test and validation - large volume with real extracted data)

Acceptance load and validation

Full data loading into ACCEPTANCE SYSTEM


Full data loading into PRE PRODUCTION SYSTEM

Validation of converted data and Key User + Business Objects Owner Signoff
Full conversion into PRODUCTION SYSTEM and final Signoff

Total
Total - at best (total in Person/Days of each business object)

Total - most probable (total at best + 20 to 25% buffer)

Step 3. Calendar Planning


To do the calendar planning, using MS-Project or other planning tool, you will enter the tasks and complete it
with the following information :
1* Tasks efforts in Person/Days
2* Tasks dependency
3* Names of the resources assigned to each task and the percentage of their availability on it
4* Non working days and Holiday.