Data Migration – Abdallah Galal
Moving data once from one or more legacy systems to destination system
Legacy systems: SAP or not SAP
Destination system: SAP S4HANA
Not used to replicate data, but to migrate data
Data replication: existing and update to date in 2 systems
So whenever we did a change in master data system, move immediately to transaction systems
Used also in reporting system (transactions will be used in reporting)
Types of data available in SAP:
1. Configuration data
What we maintain when we change the configuration of the system
Define company code
Change process configuration
Not included in the data migration
2. Master data
We create them once, use it in the different transactions
Ex customer master data, vendor master data, G/L account master data, employee, product
included in the data migration
3. Transaction data
Actual transactions we do
Ex purchase orders, accounting entries, sales orders, production orders
included in the data migration
data migration process:
1. Data extraction
Choose data objects which we want to transfer to the new system
Customer master data, G/L accounts, G/L account balances, G/L account open items
Extract from legacy system
2. Data cleansing
Clean the data, check mistakes, missing, duplicates (critical & important)
3. Data transformation
Change data format of the old system to the format of the new system
4. Data loading
Load the transformed and cleansed data
5. Data verification
Verify the data loaded to the destination system was done in right way, we do reconciliation to
check
Data migration tools:
1. LTMC
Legacy Transfer Migration Cockpit
On SAP Firori
To load data from excel files
2. LSMW
Legacy System Migration Workbench
To load data from excel files
From SAP GUI to SAP Fiori: /n/ui2/flp
Data migration
Click on create
1. Migrate data directly from SAP system
Source SAP and destination is SAP
2. Migrate data using staging tables
From excel sheets
Display next available
Local: staging tables will be created in SAP S4HANA, it won’t be created in another database
Remote: in another database, it will ask for a connection string (connection to another SAP S4
HANA database)
Step 2: development package
Local package:
can’t be transported to another system.
Working directly on production and upload directly
Standard SAP:
Use demo (testing system), then migration project, then test, then transport the migration
project to production environment
Other package:
While data migration, SAP will create staging tables. SAP needs a development package
These tables will be filled by our excel sheets.
Step 3: migration objects
FI – G/L account
Supplier
Customer
FI – Accounts payable open item
FI – Accounts Receivable open item
FI – G/L account balance and open/line item
Click on arrow
N.B.: filter in search bar works on both sides of the page: search in available migration objects
and selected migration objects
Review
Add
N.B.: Predecessor objects are mandatory and will be added.
Data migration application is recent/new – very well documented
Create project
Ready for processing
Monitoring (system preparing the objects in the system)
Beside object if we click on the no of tables, it will show the tables
Technical ID: is the ID of the table in the system
Table status: ok
If we click on the table name, it will show fields and its explanation (accepted values in each
field)
Click on object
Tables
History
Migration object dependencies (successor)
Beside object – mapping tasks: 1 open
1. Download template
Introduction sheet
Field list (orange mandatory – blue optional) min requirements
Fields with * are mandatory
Click on object
Dropdown
2. Upload file
Upload
Validated and import file completed
Instances = values mean the no of G/L accounts we are opening
3. Prepare – prepare staging tables
4. Mapping tasks (recommend some mapping)
6 digits will be completed by more zeros
Confirm
5. Simulate the data uploaded
Check without any records, just a simulation
Start simulation
Schedule an activity to simulate all the lines
Options:
- Random 10% - kind of sampling
- Random 500
- All instances
- Custom selection
Select on the checkbox FI – G/L account
Up right click on instances
Click on the checkbox of “chart of Account”
N.B.: correction can be done after migration
6. Migrate
Options:
- Random 10% - kind of sampling
- Random 500
- All instances
- Custom selection
Start migration
To check
Tcode: se16h in SAP GUI
7. Create correction file
Go = refresh
Select the uploaded file
Actions: transfer data to staging tables (overwrite the data)
Replace duplicates with instances from file
Transfer data
Simulate again or migrate – start migration
Monitoring
