1.

Migrate your data to S/4 HANA :

a. Agenda:
 Introduction to Data Migration
 Data Migration Cockpit (DMC) for SAP S/4HANA & Pre-requisites
 Migrating Your Data with SAP S/4HANA Migration Cockpit (LTMC)
 Extending Pre-delivered Content Using Migration Object Modeler (LTMOM)
 Creating Custom Migration Object Using Migration Object Modeler (LTMO)
b. Introduction to Data Migration:

Three different approaches to move to SAP S/4HANA.

Bring your business processes to the new platform

▪ A complete technical in-place conversion of an
existing SAP Business Suite ERP system to SAP
S/4HANA.

▪ Adopt new innovations at your own speed

New implementation / re-implementation

Reengineering and process simplification based
on latest innovations
▪ Implement innovative business processes with
best-practice content on a new platform

▪ Perform initial data load

▪ Retire old landscape

Value-driven data migration to the new platform

▪ e.g. consolidation of current SAP Business Suite

landscape into one global SAP S/4HANA system or

selective data migration based on legal entities.

Introduction to Data Migration:

The matrix below shows tools available in various data migration scenarios:

Target Source SAP S/4HANA SAP S/4 HANA Cloud

SAP R/3 SAP Data Service (SAP DS) SAP S/4HANA Migration Cockpit

SAP ERP SAP Information Steward For SAP S/4HANA Cloud Private
Option, usage of Migration
SAP Rapid Data Migration content Object Modeler is also available

ANY ERP SAP S/4HANA Migration Cockpit (MC)

with SAP S/4HANA Migration Object
Modeler (MOM)

The LSMW (Legacy System Migration Workbench) function is still available within SAP S/4HANA, (on
premise edition) but not considered as the migration tool. LSMW might propose incorrect migration
interfaces that cannot be used in SAP S/4HANA anymore.

The Legacy System Migration Workbench (LSMW) should only be considered as a migration tool for SAP
S/4HANA for objects that do not have interfaces or content available after carefully testing for each and
every object. The use of LSMW for data load to SAP S/4HANA is not recommended and at the customer’s
own risk.

Data Migration Cockpit for SAP S/4HANA & Pre-requisites:

Data Migration Tool for SAP S/4HANA & Pre-requisites:

1. Tool of choice for migration to

SAP S/4HANA
▪ Part of SAP S/4HANA and SAP “
S/4HANA Cloud (included in these
licenses)
▪ Ready-to-use solution
▪ Support for customers with new
implementations
2. Preconfigured migration content
specific to SAP S/4HANA
▪ Comprehensive set of preconfigured
migration objects, such as customers,
suppliers, and so on
▪ Automated mapping between source data and SAP S/4HANA target values

3. Integrated in SAP Activate

methodology
▪ Proven methodology integrated in
SAP Activate roadmap: Transition to
SAP S/4HANA
▪ Part of the SAP Model Company service
▪ Best practices
4. Easy and safe migration.
▪ Step-by-step guidance through the
migration process
▪ Template files for each migration
object
▪ Data validation to ensure high-data
quality and consistency
▪ Mass data transfer with the help of a
staging solution
5. . Flexible and extendable
▪ Migration object modeler for custom-
specific requirements
▪ Ability to extend existing SAP migration
objects
▪ Integration of custom-specific objects
6. . Flexible and extendable
▪ Migration object modeler for custom-
specific requirements
▪ Ability to extend existing SAP migration
objects
▪ Integration of custom-specific objects
Data Migration tool for SAP S/4HANA

Data Migration Cockpit (DMC):

Actions on Basis team / Security Team:

• To transfer data using the SAP S/4HANA migration cockpit, role SAP_CA_DMC_MC_USER is
required. To use the SAP S/4HANA migration object modeler (transaction LTMOM),
role SAP_CA_DMC_MC_DEVELOPER is required.

• The corresponding role for each migration object is also required.

• For additional considerations, find below details of SAP Note 2481235. SAP S/4HANA Migration
Cockpit (on-premise) - restrictions and extensibility of pre-delivered migration objects.

• Refer SAP note: 2537549 for collective details for data migration cockpit where we can find all
the SAP note details which are required to be checked as a part of pre-requisite check.

• RFC connection to be established using SM59 Transaction in case of DMC using Direct SAP
Extraction from Source system.

• DBCO – DB Connection to be established for HANA DB and Data migration cockpit connection.

Note: We should not have Staging SCHEMA user name same as any other Schema User name which is
already created (Eg. SLT Staging Schema cannot be used as DMC Schema) else Start Transfer will not be
executed and conflict happens.

• HANA DB should be ready with a DB USER created.

Actions on the User using Data migration cockpit:

• Maintain the Created DB connection in table “DMC_C_WL_DBCO_OP” – This is required in case

when We use DMC using Staging database to get Staging tables created in DB.
 • We should update Hosts File with the LTMC – web service path so when we execute Tcode LTMC
it opens in web browser. We will find this Hosts file at path : C:\Windows\System32\drivers\etc

• At end of this document there are also few more SAP Note details and Error list which are
commonly found in Data migration cockpit

Data Migration Tool for SAP S/4HANA:

T Code: LTMC

SAP S/4HANA migration cockpit – Preconfigured migration content

 Preconfigured content and mapping for each migration object, e.g. Customer, Bank Master,
etc…
 Predefined templates (Microsoft Excel XML files) for each object
 Automated mapping between template and target structure
 Migration programs are automatically generated – no programming required by the customer
 Available for private and public cloud and on-premise versions

Data Migration Tool for SAP S/4HANA:

T Code: LTMOM

SAP S/4HANA migration cockpit – SAP S/4HANA migration object modeler

SAP S/4HANA migration object modeler

is Part of the SAP S/4HANA migration cockpit

▪ Design functionality to easily integrate custom objects and enhancements

▪ Integration of newly created objects

- Custom objects

- SAP standard objects that are not yet

in the scope of the SAP S/4HANA
migration cockpit
▪ Customer-specific enhancements

(e.g. add new fields) to SAP standard

objects delivered with the SAP S/4HANA
migration cockpit

▪ Available for on-premise and private cloud

Process:

Migrating Your Data with SAP S/4HANA Migration Cockpit (LTMC)

Flat File Based Load Method:

Steps :

1. Starting the cockpit

• On-Premise : Using Transaction Code LTMC

• On Cloud : Manage Your Solution  Migrate Your Data

2. Downloading templates

• Once you Create new Project, you will have object list which are available in LTMC

• Click on Object you want to Migrate

• Download the template from button shown below

3. Filling the XML template

• All * Fields are Mandatory

• All fields Details can be found in Tab ‘Field List’

• Different Tabs available for different View/set of data

4. Upload the File

• Upload the filled xml file using Upload File Button

• Once Uploaded, we will have to activate the file using Activate Button. Without
activation the file won’t be available for Start Transfer

5. Start Transfer : This will have 4 important Step

a. Validate Data

b. Convert Value

c. Simulation Import

d. Execute Import

Step : Validate Data

In the step Validate Data, the system checks the consistency of the files. If the system detects
any inconsistent values. (for example, if mandatory values are missing), you must correct them
before proceeding to the next step.
 Step : Convert Values

Some data may need to be converted before it can be transferred to SAP S/4HANA. In this
step, you can convert such data.

• Simulate Import

In this step, the target system validates the data. No data is posted to the target
system.

If there are Errors/Warnings occurred in Simulation step, it will get displayed in

Notification area.

• Execute Import

In this step, the data is posted to the target system.

Once Import is Successful Transfer status will be set to ‘Finished’.

Execution Log will also be displayed in Notification are which can be downloaded as excel for further
audit purpose.

Creating Your Own Migration Object Using LTMOM:

You can create your own custom object which is not available in LTMC. Currently SAP provided only 53
objects (in 1709) so using LTMOM you can migrate other objects too.

Process is similar to what we had seen in Extending pre-Delivered objects. You will need Function
Module (not necessarily Z).
Steps

 You have to create a migration project using T code: LTMC

 Call Transaction code LTMOM

 Go to Menu Migration Object Migration Object using  User Defined

User-defined Migration Object

Give an Object id(No Z_ required, example MYOBJ) and description. Currently only the option Migration
from File by calling Function Module is supported.

Enter the Name of the Function Module (Example BAPI_MATERIAL_SAVEREPLICA).

Parameter for the Return is the Table-Parameter which contains the BAPIRET2-Error Messages (see
/NSE37)

Parameter for Simulation see Function Module Description, usually there is an option like TESTRUN,
where ‘X’ means no Update.

Define Source Structure / Add Fields to Source/Excel Spreadsheet

In the Section ‘Source Structure’ it is possible to add new Fields to existing structure and add new
Structures.

choose ‘Add Field’ to add fields at the end of the structure. choose ‘insert Field’ to insert the field at the
cursor position.

add new Source Structures (Optional)

Foreign Key Relationship: You can maintain foreign Keys for Key fields like MATNR or KUNNR.

for example, if we want to add custom fields to the Material BAPI. The BAPI has an Input Parameter for
Customer Fields which matches the Structure BAPIE1PAREX.

Enter Field name, Datatype and Length and Description (Description is shown in generated Excel
Template). i usually use CHAR Fields for the Excel/Input Structure and they also can be longer than the
target SAP Field.

Press on Button ‘Generate Runtime Object’.

next Time you Generate an Excel Template in LTMC, you will also see the new fields.
Target Structure

This comes from the assigned Function Module so there is nothing to be changed here.

Structure Mapping

Each target structure you want to use/fill needs to be assigned to at least one source structure (can also
be more than one). this is done by drag and drop.

Field Mapping

Drag and drop the source field to your target field.

Some BAPIs have ‘X’ Field Structures, where you have to Mark the Used Fields with an ‘X’. here you can
select from a list of existing mapping rules, or create a new mapping rule. For each Value-Mapping in
LTMC, there is a Rule available.

Mapping Rule

Similar process explained.

Now Save & Activate the Object.

Your Custom Object in Migration Cockpit is now ready to be used for migration.

 Go to LTMC, you will see new object is added in projects Object list.

 Download the Template & fill the data.

 Select Object, Upload  Activate  Data File

 Now Start Data Transfer using Transfer button in a same way which we perform for a standard
Objects.