Scribd
Upload
38 views2 pages

ECC To S4HANA

Uploaded by

livy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
38 views2 pages

ECC To S4HANA

Uploaded by

livy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SAP ECC6 MIGRATION MIGRATION

COCKPIT PROJECT/OBJECT

STAGING TABLE XML File


(SAP AGILE DATA
PREPARATION)

S/4 HANA CLOUD

MIGRATION
PROJECT
1) Migration Projects are used to facilitate the transfer of data from a source system to SAP
S/4HANA. In order to migrate data to SAP S/4HANA a migration project needs to be
created.
2) Migration Project enables to
a. Specify the source system
b. Specify the data that needs to be transferred
c. Monitor the status of Migration
d. Group migration activities to suit the project needs
3) Migration Project has a transfer ID associated with it. The transfer ID acts as unique
identifier per project in order to facilitate transfer of project specific settings between
environments in the landscape.

MIGRATION
OBJECT
1) Once the migration project is created is, all the migration objects available within the project
will be presented with:
a. Object Name
b. Progress
c. Link to object specific documentation
d. Dependent migration objects which should be loaded first to ensure the completeness
of the data.
2) The migration object needs to be selected.
Once the migration object is selected the following process needs to be followed:

M 1) Access the migration object documentation


I 2) Get ready for transfer
a. Using Files: Assign one or more Microsoft Excel XML files to each migration object
G that is relevant for the transfer. This is done by downloading the migration template
for the migration object, specifying the relevant data, and uploading the file.
R
b. Using Staging table: When the database connection to the source system database
A is specified at the time of migration project creation, the staging tables are created
automatically for the migration object. Add the data that is relevant for the
T
migration object to the staging tables either manually or using SAP Agile data
I preparation tool.
3) Activate the files that need to be transferred. Only files in Active state can be taken to the
O transfer process. This allows you to work with multiple files and choose scope of migration
N every time you initiate the transfer.
4) Transfer process consist of the following four stages:
a. Data Validation: data stored in the staging area is subjected to technical validation
for issues like lack of data in mandatory field, wrong data length or type, lack of
P
mapping of some key master/configuration data like country codes or units of
R measure.
b. Value conversion: define mapping rules to convert input values where validation
O encountered an error.
C c. Import simulation: in this step, the data stored in staging area is processed using
actual BAPIs which are used during “real” run of the import – the only difference is
E that the changes are not committed to the database. This allows for much deeper
functional validation of interdependencies like existence of material master in case
S
of purchase or sales order.
S d. Import execution: the data in staging area is submitted for posting in the SAP
S/4HANA system using relevant BAPIs. Successfully imported records are persisted in
the database.
5) Repeat this process for each migration object that is relevant for the project.

You might also like