WP05 Exercises MigrationObjectModeler 5.3 PDF

Migration Object Modeler
S/4HANA Migration Cockpit
April 2022
Version 5.3
Based on S/4HANA 2021
Migration Cockpit exercises – Migration Object Modeler (based on S/4HANA 2021)
Introduction ................................................................................................................................................... 3
Preparation and login details ........................................................................................................................ 3
Exercise 1: Create a new migration object ................................................................................................... 4
Exercise 2: Simulate the data import using the newly created object ........................................................ 13
Exercise 3: Create a new migration object for cost center text .................................................................. 20
Exercise 4: Migrate Cost Center ................................................................................................................. 39
1.1 Check data in the Source System .................................................................................................. 39
1.2 Create the project and adapt the data selection ............................................................................. 41
1.3 Select data from the ERP source system and check the selection result ...................................... 46
Exercise 5: Migrate Products ...................................................................................................................... 48
1.4 Check data in the Source System .................................................................................................. 48
1.5 Create the project and adapt the data selection ............................................................................. 50
1.6 Select data from the ERP source system and check the selection result ...................................... 57
2
Introduction
In this document you will find all the steps to complete the exercises related to the S/4HANA Migration
Cockpit hands-on.
This set of exercises is focused on the creation of new objects in Migration Cockpit using the Migration
Object Modeler functionalities.
Preparation and login details

In order to be ready for the exercises make sure you have access to the system as per the Cheat Sheet
you received.
During the execution of the exercise you will use the following tools.
- SAP GUI
o The Migration Object Modeler works best from the SAP GUI so we suggest to use this client
for all the steps involving transaction LTMOM.
o The login details are specified in the cheat sheet and you can use the SAP GUI installed
already in the terminal server.
- Web Browser: Chrome
o All the following exercise can be executed with the web browser. We suggest to use Chrome
since we tested all the exercises with it.
o The different applications, transactions and Web Dynpro you will be using during the
exercises are published in the FIORI Launchpad as tiles for your convenience. The
launchpad is accessible using the icon in the desktop (see after).
- HANA Studio
o The HANA Studio is installed in the terminal server you are using for the exercises and your
cheat sheet contains all the details to login.
To quickly access the SAP Fiori Launchpad you can also use the icon on the desktop.
3
Exercise 1: Create a new migration object

In this first exercise you will start creating a new migration object in Migration Object Modeler (LTMOM).
As an example, we will create an object that already exists and it is the bank master data in a
simplified way.
The overall purpose is to make sure you know how to create the object and what are the
different types of rules you can possible use. For this reason you will be focusing on a
rather simple object that already exists trying to reproduce the different rules and mappings.
Login to SAP GUI and call transaction

LTMOM.
Select “Project” in the drop-down menu.
Press button to see the list of

available projects and select one of the
existing projects you have previously
created.
NOTE: If you have not created a project

previously you first need to access the
Migration Cockpit and create a new
empty project with the option “Transfer
Data from File”. Afterwards back to
transaction LTMOM select the newly
created project.
4
Click on More >> Project >> Create

Migration Object >> User-defined >>
Migrate Data Using Files/Staging Tables
Make sure your project is selected.
Define the following parameters:
Migration Object ID: BANK_DATA_XX

(leave Z_ at the beginning and replace
XX with your group number)
NOTE: Leave the prefix Z_Z before the
name.
Description: Bank Master Data
Define Target Structure Using: Function
Module
Press “Next”.
In the next screen provide the following
configurations:
Name of Function Module:

DMC_MIG_BANK
For the configuration “Objects for

processing Business Objects instances”
leave selected “Process one instance at
a time”.
INFO. These settings specify how the

function module processes the data
from a specific source, (for example the
data from a file). Two options are
available:
Process One Instance at a Time: The

system can pass data to the function
module one instance at a time. This
means if N records must be read, the
function module will be called N times.
5
Note that this can negatively impact

performance.
Process Multiple Instances at Once: The

system can pass all the records to the
function module at once. This means
that the function module is called only
once.
In the section “Custom Include Program”
select the parameter RETURN for
“Parameter that Returns Result” using
the match code.
INFO. If the function module encounters

errors when processing the passed
data, it should return appropriate
feedback in the form of messages to the
user. Here, you can specify the return
parameter that contains such error
messages.
Parameter That Returns Result: The

return parameter that contains the
messages.
Include for Handling Return Parameter:

The name of the include file that handles
the return parameter.
In section “Simulation Settings” eneter
the parameter name:
I_CHECK_BEFORE_SAVE and value X
for simulation.
INFO. If you want to simulate a data

transfer without writing data to the target
system, you can specify the relevant
settings here. The following options are
available:
Parameter for Simulation: The
parameter of a function module that
refers to the simulation or the writing of
data.
Value for Simulation: If the data transfer
is started in test mode and you specify a
simulation value here, the simulation
value is shown as a result.
Value for Writing Data: If the data
transfer is not started in test mode, and
you specify a value here, then this value
will be written as a result.
6
Confirm that all parameters have been

set correctly.
Press to create the object.
Now that the object is created you can

start adding the content.
Click the button “Display <-> Change”

on the top (1)
First you will work on the source

structure. Double click on the “Source
Structure” entry in the left column (2).
Right click on “Source Structure” in the

middle and select “Append Structure to
Lower Level” (3).
Specify “S_MASTER_DATA” as name
and “Sender bank master data” as
description.
Confirm the message with Yes.
In the resulting screen you can now

define the fields in this new data
structure.
Define the fields as showed in the

picture using the right part of the screen.
HINT: Pay attention to select the “Key

fields” column as shown.
7
Now you will define how this structure is

related to the standard object view.
To do that right click on the structure in

the middle part of the screen and select
the option “Change View”.
INFO. You can use these views to

adjust the fields that are available in the
template file for the migration object. For
each source structure field, you can
choose whether it is visible, required, or
not visible in the customer view. You
can change these attributes in edit
mode. You can use these views to
adjust the fields that are available in the
template file for the migration object. For
each source structure field, you can
choose whether it is visible, required, or
not visible in the customer view. You
can change these attributes in edit
mode.
Set the structure as required as well as
the 2 fields BANKCOUNTRY and
BANKKEY.
Press to make sure your work

is saved up to this point.
You can now click on the “Target

Structures” to have a look on this.
This structure is automatically derived

from the function module you have
selected at the beginning and you can
see the same here in the right column.
Nothing to do here.
INFO. Here you can get an overview of

the target structures associated with the
migration object. Note that structures
can be single fields, multiple fields, or
8
tables. You can check the attributes of

the field associated with the target
structure (for example the data type and
length).
You can now switch to the “Structure
Mapping” part where mapping can be
created simply with drag and drop.
Drag the source structure in the middle

column to the target structures in the
target to create the 4 mappings as
shown in the picture:
• Migration of Bank
• Bank country key
• Bank keys
• Bank address

Finally, you can focus on the fields
mapping.
Double-click on the “Field Mapping” area

on the left column.
INFO. In the field mapping area, you can

map fields from the source structure to
fields in the target structure. In the
following steps you will learn three
different ways to map the source
structure to the target structure and
assign the necessary rule. The first
possibility is to assign an already
existing rule to the target structure field.
Right click on the field “Bank country

key” and select “Assign Rule”.
Here a pop-up tells you that a rule
proposal exists.
Select “Yes” to accept the proposal.
Note: this is a new feature available

since S/4HANA 1809.
9
Rule called “CVT_LAND1” will be

automatically selected.
Define the import parameter

BANKCOUNTRY as per picture.
Press to confirm.
Now right click on the field “Bank keys”

and select “Assign Rule”.
Use the function “CVT_BANKL” and in

this case assign 2 different input
parameters for BANKCOUNTRY and
BANKKEY.
Press to confirm.
INFO. The second possibility to assign a

rule is to use Drag and drop. To map a
field from a source structure to a target
field, drag the relevant field from the
right-hand side to the target structure
field on the left-hand side. The resulting
mapping operation is a simple 'MOVE'
operation - that is, the values of the
source field will be moved to the target
field.
Drag and drop the field BANKNAME to

the right in the corresponding Name of
bank and verify that the rule MOVE is
defined as per the picture.
INFO. The third possibility to assign a

rule is to Create an own rule as ABAP
code.
Right click on the field City in the right

column and click “Assign Rule”.
10
Define a name for your function. To

avoid overlapping use the following
naming convention:
Z_CITY_MOVE_<A01User ID> (e.g.

Z_CITY_MOVE_A01 for user
STUDENTA01).
Click on the icon IV_CITYto

create the function.
Confirm the “Save Data” pop-up with
“Yes”.
Define a description for your rule.
Define 2 parameters, 1 as Import and

another one as Export as shown in the
picture.
Insert this “really complex” code:
IF NOT IV_CITY is initial.

MOVE IV_CITY to EV_CITY.
ENDIF.
Press to confirm the rule.
Press to come back to the

previous screen.
Provide the parameter value

“S_MASTER_DATA-CITY” for your new
rule that you can select pressing the
match code / value help button on the
right.
Click to confirm the rule.
11
Once back verify that the rule has been

defined correctly after the “City” field.

You have now completed the object.

You will notice that the runtime objects
are not yet generated from the status in
the top.
To generate the object press “Generate

Runtime Object” in the top bar.
After the generation run you will see the

new status as “Generated”.
In the bottom part you can also check
the message to make sure there are no
errors.
The warning message can be ignored.

Now it is very important to exit from edit
mode and then from transaction LTMOM
otherwise the object will remain locked
by your user.
You can do this by switching to display

mode again or alternatively by clicking
the < button and exit from the
transaction.
Congratulations you have now complete the creation of the custom object. In the next exercise you will use
this to simulate and debug a data import.
12
Exercise 2: Simulate the data import using the newly created

object
In this exercise you will use the newly created object to import data in the system. We will do that using
the simulation option available since 1709 FPS01.
This simulation mode can be used since version 1709 FPS01 onward implementing SAP Note 2630183
(2630183 - Run an import simulation for a file migration object).
Now that the object has been created you can find it in the Migration Cockpit under your
project and you can import the data.
You will now try the import using the simulation functionality to get familiar with the
procedure. This allows you to simulate the import and troubleshoot the different steps
performed in a debug mode.
The first step is to get the file template

that will be required to start the
simulation.
To do that go to your project in Migration

Cockpit and look for a new object called
“Bank Master Data”.
Select the new object (1) and click on

Download Template (2).
Check the download folder and locate
the file.
Open Excel on the Remote Desktop and

once you are in Excel Open the file you
have just downloaded to start editing it.
13
Insert one or more records as an

example in the sheet “Sender bank
master data”.
Make sure to use:

- “Germany” as country (first column)
- A number composed by 8 digits as
key (second column)
- A bank name of maximum 60
characters (third column)
- A city name in Germany (fourth
column).
Save the changes confirming the

message about the format and close the
file.
Back in Migration Cockpit click on

Upload File
Click on Upload and select the xml file
you have just modified.
You can also drag and drop the file in

the white area.
Confirm that the data is successfully

transferred to the staging table.
Now go back to the main project screen

and select the option Prepare (if not yet
executed).
Confirm the message to start the

preparation task and activate the
Consistency Check.
Now back to the main project screen

you should see 1 error related to
missing mappings.
Now to solve the error select the option

Mapping Tasks.
14
Click on the first mapping task “Mapping

of Bank Key”.
Confirm the value.
Now select the second mapping task

“Mapping of Country/Region Key” and
specify the value DE for Germany and
confirm.
Go now to SAP GUI and login to the

system and access the object you just
created in transaction LTMOM.
Switch to change mode.
Now we can start the simulation.
To do that click on button “Simulation”

while you are on the new migration
object you created.
15
In the next screen you see your

migration object already selected.
There are also some additional

parameters that we will explore in the
next steps.
The section “Number of Records for

Simulation” allows you to select a subset
of records from the staging table for the
simulation.
Selection can be done for:

- All records
- The first N records
- Specific records that you manually
select from the table
In our case we only have 1 record so

you can leave the default selection.
The next options in the screen allow you
to set a breakpoint during the execution
and you can do that at 2 different points:
Before Conversion
If you choose this option, a breakpoint is
set before the conversion takes place.
Before Posting:
If you choose this option, a breakpoint is
set before the data is written to the target
system.
You can try select “Before Conversion”

to try this option.
If required, you can debug errors in the
SAP S/4HANA target system. You do this
by using so-called simulation runs. If you
want to use this option, select the option
Save Data if Errors Occur and enter a
name for the simulation run in the
Simulation Run field.
16
The system will then save the relevant

information about the first erroneous
record that was encountered in the file.
This system creates a simulation run (with
the name you specify) that contains this
information.
Note: If all records can be processed

successfully, no record will be saved and
the specified simulation run will be deleted
from the system after the simulation run
has finished.
Note: If a translation object does not

contain all required conversion entries for
a record, the record is not handed over to
the writer module that updates the target
system. Such records are not classified as
erroneous records. If this occurs, the
simulation run will display information
messages that state that conversion
entries were missing.
To debug the error in the target system,

you can then run the report Debug Error
for Simulation Run
(DMC_MC_MIGOBJ_EXEC_SINGLE_OL
O) in the target system. You can access
this report from the menu by choosing
Goto -> Debug Error. You specify the
name of the simulation run, and the
system will open the ABAP Debugger at
the location before the data of the saved
erroneous record is written to the target
system. Note that you can delete the
simulation runs from the target system
when you are finished by using report
Delete Simulation Runs
(DMC_MC_MIGOBJ_EXEC_OLO_DELET
E). You can access this report from the
menu by choosing Goto -> Delete Run.
Do not select this option for this

exercise.
The last section is called “View Records
That will be Simulated”
You use this report to simulate the

import of data from staging tables. If
required, you can view these records
before they are simulated. You can view
these records before they are converted,
or after they are converted.
For our simulation select “View Records

After Conversion”
17
Click now on button “Execute” to start

the simulation.
The ABAP Debugger session will start

and the simulation is now paused at the
first break point before the conversion
happens.
You can now proceed step by step using

the “Single Step” button on the top (F5).
The source data is initially stored in

structure “_IT_S_MASTER_DATA” and if
you double click on it (few instructions
after the breakpoint) it will be added to
the list of variables in the right bottom
corner.
From there you can double-click on the

variable name to see the content.
You can also use the button Continue to
proceed with all the steps.
18
When you have completed the debug of

this phase you can proceed with the
execution by pressing the button
“Continue” (F8).
You will be seeing the Data Editor where

you can preview data as previously
selected.
You can click on the different structures

in the left to see how the data looks like
after conversion.
Once you completed the analysis select

More and then Cancel or the button
back.
Remember: no data will be loaded into

S/4HANA with the simulation so you can
repeat it as many time as you want.
Congratulations you have now completed the exercise.
19
Exercise 3: Create a new migration object for cost center text

In the following exercises, you will learn how to create your own migration object to upload cost center texts (for
already created cost centers), create your own translation object and map the source structure fields to the target
structure fields of the SAP S/4HANA system with the migration object modeler.
You will now use everything you learned in the previous exercises with a more complex
object that does not yet exists in the system.
This object is related to the text translations for the cost center object. When the cost center
is created the texts related to name and description can be maintained in the original
language. After these additional languages can be added but there is no migration object
available to do this.
Using SAP GUI login to your client using

a language other than English (for
example German typing DE)
Call transaction KS03.
Enter controlling area ‘A000’ and press

the button to continue.
Select cost center US10_ADM1 and

click on the first button (master data in
English) to see the details.
You can see the name and description
fields filled if you have logged-in using
English as a logon language, but you
won’t see any value in any other
language.
In the example picture here, the result if

your login in German.
NOTE: by creating the next object we

want to import additional texts for the
cost centers so names and descriptions
can be imported for multiple languages.
You can now log-off and login with your

preferred language.
20
Call transaction LTMOM and select your

project.
NOTE: In the following steps, you will

copy the migration object Cost Center to
your migration project, so that the rules
that are used in the migration object
Cost Center are available in the
migration project. You can use these
pre-delivered rules (if necessary) and do
not have to create your own rules.
To do so first of all click on More >>

Project >> Create Migration Object >>
From Template and then select Migrate
Data Using File/Staging Tables
Confirm the project name that is already

selected or select your own project from
the list.
21
Select object “CO - Cost Center” from

the list and confirm.
Now this standard object is part of you

project.
Click on the icon to switch back to

the migration project level.
Now you will create your custom object

for cost center text.
To do so first of all click on More >>

Migration Object >> Create Migration
Object >> User Defined and then select
Migrate Data Using File/Staging Tables
22
Specify a name for the new object using

the following pattern:
Z_ZKOSTL_TEXT_<XX>
Where <XX> is your group ID.
Select “Function Module” as a target

structure.
Provide a description and click to

continue.
Enter function module name:
BAPI_COSTCENTER_CHANGEMULTI
PLE
Select RETURN as a parameter for the

return result.
Remind: The function modules used by

the SAP S/4HANA migration object
modeler contain parameters that use the
structure BAPIRET2 to return messages
to the SAP S/4HANA migration object
modeler. Messages can include any
information or warning messages, as
well as any error messages that caused
the function module to fail and not
complete the transfer. Messages could
also include success messages. The
SAP S/4HANA migration object modeler
uses such messages in order to
determine whether the business object
instance was transferred successfully. In
addition, it uses the messages to
prevent the transfer of the same
business object instance more than
once.
23
Note: The SAP S/4HANA migration

cockpit can call the function module in a
so-called simulation mode. In this mode,
the function module performs additional
checks based on the data that is passed
from the SAP S/4HANA migration
cockpit during the activity Simulate
Import. No data is written to SAP
S/4HANA.
To enable simulation mode, specify the
parameter of the function module that
activates this mode in field Parameter
for Simulation. For information about the
parameters, see the documentation for
the specific function modules.
Depending on the function module, a
specific value must be set to
differentiate between the simulation and
real processing of the data. The
corresponding values can be specified
in field Value for Simulation and Value
for Writing Data. For information about
the values, see the documentation for
the specific function modules.
Note that not all function modules
support the simulation mode. In this
case, the SAP S/4HANA migration
cockpit performs the extended checks
without calling the function module.
In this case use the parameter

TESTRUN and Value ‘X’ for the
simulation.
Press to confirm and create the

object.
Now you object is created and all the
sections visualized on the left end side.
Let’s start by defining a source structure.
Click on the button to switch to change

mode (1).
Double-click on “Source Structures” (2).
24
In the middle column right click on the

“Source Structure” node and select
“Append Structure to Lower Level”.
Define “S_CSKT” as structure name and

provide a description.
Confirm by pressing “Continue” and

confirm also the warning message with
“Yes”..
You can now use the “Full Screen

on/off” button to better visualized the
screen.
Define the 7 fields as shown in the

picture here.
Please remind to set the first 5 fields as

Key Fields in the first column!
Now back to the structure on the left

right click on the “Cost Center test” node
and select “Change View”.
25
Change the configuration for the first 6

fields to make sure they are set as
required.
Now Save your project.
Next step is the structure mapping and

to manage that in the left column double
click in Structure Mapping.
In order to make the mapping easier we

will refer to the technical names.
To activate the visualization of technical

names go to More >> Settings >>
Technical Names On/Off
Now let’s start by dragging and dropping

the source structure S_CSKT from the
left-hand side to the node HEADER in
the target.
26
Now for the second mapping let’s use

another method.
Double-click on the
R_CONTROLLINGAREA.
In the resulting screen click on “+”

button.
Specify the Source Structure and set

that Access Type is “Mapping only” and
Mapping Type “1:1 Relation”.
Confirm with .
Now select and double-click on target

structure R_LANGUAGE.

button.

Confirm with .
Select and double-click on target
structure R_COSTCENTERLIST.

button.

27
Confirm with .
Now you should see the mapped
structures in the target structure as a
suffix.
Refer to the picture to check the

correctness.
To double-check the correct structured
mapping click on the button .
Check the result and compare it with this

picture.
Make sure to have the same result

before proceeding.
Click the button < (Back) to come back

to the main screen.
28
Now the last step is to map all relevant

field.
Double-click Field Mapping.
Now in the field mapping screen press

the last button on the right side and
select Rule Proposals.
In the resulting screen you see all rules

proposals.
First select the rule CVT_SPRAS (1) for

the language (second one). Since there
are multiple rules proposals you need to
decide which one to use.
Click on Deselect All Rule Proposals (2)

so you can only select the ones you
really want to use.
Now select the first 3 rules (3).
Confirm.
Confirm the message.
29
Double-click on the
CONTROLLINGAREA field now to
define the input parameter.
Select now the parameter KOKRS from

the help and confirm by pressing
Continue.
As a result, you should now see

something like the picture here.
Double-click now on the LANGU field.
Select the source field LANGU as the

input parameter.
30
Choose Continue
Finally double-click on COSTCENTER

to define the parameters for the third
rule you have automatically assigned.
To search for the right import parameter,

open the list of Parameter Value for
IV_KOKRS and select S_CSKT-
KOKRS; then do the same for
IV_KOSTL and S_CSKT-KOSTL.
Choose to continue.
31
Drag and drop the following fields:

- DATAB to VALID_FROM
- DATBI to VALID_TO
Scroll down the list on the right side until you

see the NAME and DESCRIPT fields.
Drag and drop the following fields:

- KTEXT to NAME and
- LTEXT to DESCRIPT
Save your changes.
32
Select Filter -> Show Fields with

Mapping.
As you can see, a green icon is

displayed for all target fields you have
mapped. You can also find
the assigned rule (MOVE or
CVT_SRPA, …).
To check if the generated programs have no

syntax error, you can generate the programs
required to read data from the source system
and to transfer data to SAP S/4HANA.
Choose Generate Runtime Object.
33
As a result you should see the object

correctly generated with only few
warning messages that can be ignored
since they are about target structures
not mapped from the source.
Now that the object is generated, we

can try to import data.
In Migration Cockpit you will now see

the new object as part of your project.
Select the number 1 on the field Tables.

You can see here the staging table that
has been already generated in the target
HANA database.
Take a note of this table name because

you will need the same few steps later.
Open the HANA Studio.
Open the SAP HANA Administration

console.
34
You should already have a connection

to the database HXE@HXE with the
user staging master.
In case you don’t right click on the left

column and select “Add System…”
Host Name: hxehost.kmudemo.site

Instance Number: 90
Mode: Multiple Containers
Tenant Database: HXE
User : STAGING_MASTER
Password : Welcome2022
Choose File and then Import…
Expand SAP HANA Content and select

Data from Local File.
Press Next.
35
Select your connection with user

STAGING_MASTER (it should be the
only one available).
Press Next.
(1) Click Browse and select the

source file named
“CostCenter_Import.csv” from
the folder C:\temp\Data
Migration
(2) Click on Select Table and select
the staging table you have
previously noted down from the
schema STAGING_MASTER
expanding the section tables.
You can also use the search
function to easily find the table
using the name.
Press Next.
In this screen you define the mapping

from the file columns into the table.
36
Click on the mapping button and choose

the option One by One.
Since the columns in the file have the

same order as the table this is sufficient
to obtain the right mapping.
Click Next.
Here you can review the source file and
the target table (that should be empty at
this point).
Click Finish to start the import.
Verify that the import is completed

successfully by checking the lower part
of the screen in HANA Studio and
double-clicking the Import flat file job.
Now back to Migration Cockpit click on

Mapping Tasks.
37
Resolve all mapping tasks.
Click on Simulate.
You can simulate all records in this case

as there are only few.
If you get simulation errors they are
probably related to further missing
mappings.
Click again on Mapping Tasks and

confirm the remaining values.
Once the simulation is successful, click
on Migrate to perform the final migration.
Now that the import is completed we can
check the entries in the system to verify
the result.
Login to the S/4HANA system in SAP

GUI using another language (German,
Spanish, Italian or French) and in
transaction KS03.
Now select controlling area A000 and

cost center US10_ADM1. Press enter to
see the master data.
Now the text loaded from Migration

Cockpit is visible here.
You can check all texts by calling
transaction SE16 and specify table
name CSKT and press .
In the field KOSTL specify the cost

center. For example US10_ADM1
Press Execute and you will see all the

entries loaded for this work center (“D”
for German, “F” for French, “I” for Italian
and “S” for Spanish).
Congratualations you have successfully completed the exercise!
38
Exercise 4: Migrate Cost Center

In this exercise you will select cost centers from company code 0001 (which is assigned to controlling
area 0001). This time you do not want to select all cost centers but restrict the selection to the
cost centers KSDTC1 to KSDTC5. Which begin with KSDT.
Therefore, you should go to the modeling environment (Migration Object Modeler) and do the
respective settings. The migration object modeler offers the standard select option dialog for each
field of the source table of the respective migration object data model, in this example table CSKS.
Please note that as soon as you change the selection for a migration object, it becomes your
responsibility to care for the consistency of the items to be selected.
In the following exercise you first check the existing records in the source system. Then you create a
new project in the SAP S/4HANA system (Fiori) before you go ahead adapting (modeler) and
executing (Fiori) the selection.
1.1 Check data in the Source System

Explanation Screenshot
Connect to system ABA and

choose Client: 800. Click
Connect.
This opens the SAP GUI on
your PC.
Use the login data from your

cheat sheet.
following login data:
To check which cost centers

exist in the system, enter
KS13 in the transaction field.
Confirm your entry by

pressing the Enter key.
39
1. Enter 0001 in the field for

Controlling Area.
2. Click Continue .
1. 1. Enter 1 in the "from" field.
2. 2. Enter ZZZZZZZZZZ in the

"to" field.
3. 3. Click Execute .
In the source system there

are 7 Cost Centers.
You want to select only the

Cost Centers which begin
with KSDT to be transferred
to the S/4HANA system.
This means: 6 Cost centers.
40
1.2 Create the project and adapt the data selection
Go to your FIORI
launchpad.
You probably have still
the FIORI open.
Click the tile Migrate Your

Data.
Create a new project as you

did in the other exercises.
Type in, respectively chose:
Name:
00_Project_Cost_Cente
r
Scenario: SAP ERP to SAP
S/4HANA
Connection to Source
System: ABACLNT800
Dev.Package: $tmp
Company code: 0001
Flag migration object: CO-

Cost center and move to
the Selected Migration.
Click “Review”.
Do not add the predecessor
objects.
Click “Do Not Add“.
Click “Create Project”.
Click on your project

00_Project_Cost_Center
.
41
Besides the project creation,

no other actions have taken
place so far.
To change the selection, you

use the migration object
modeler (LTMOM) which is
the modeling layer.
To open the modeling
environment, firstly you
need to access the
S/4HANA system via SAP
Logon.
Open your SAP Logon.

Choose system S4R
(S/4HANA system).
Use the logon data from the

cheat sheet.
Enter transaction ltmom in

the transaction field and
confirm your entry by
42
You are now in the modeling

environment (LTMOM) of
the Migration Cockpit.
Open the first drop-down

box and select the entry
Project by clicking it.
Enter your project name
r in the second box.

Please note: bringing up the

project definition takes
some time.
Change from display mode

to edit mode by clicking
Display <-> Change
You should see Change

Project
00_Project_Cost_Center.
Expand the row

"S4_CO_COST_CENTER" by
clicking the arrow.
Then double-click on
“Source Tables”. This opens
a window on the right-hand
side.
43
Make sure you have the

display of Technical
Names turned on.
In the window at right-hand

side, double-click in the first
row on CSKS. It opens an
additional section on the
right side.
Click on the tab selection

criteria.
Сlick on the arrow in
row KOSTL (Cost Center)
and column Selection.
This brings up a popup

which will enable you to
delimitate the selection in
table CSKS.
Now, only cost center IDs

which begin with KSDT
should be selected when the
selection is executed in the
Migration Cockpit (which is
the execution layer).
1. 1. Enter KSDT* in the input

field.
2. 2. Click on the arrow
to execute to selection.
44
Click Copy .
If you see the green cross

, the selection
completed successfully.
Click OK.
Now you should see that the

arrow in the Table Details
CSKT changed to green
under KOSTL raw, Selection
column.
1. Click Save .
2. Click Back .
Note: Please leave the

LTMOM transaction
otherwise you will lock
yourself when executing the
selection!
45
1.3 Select data from the ERP source system and check the selection
result
After you have defined that the selection of cost centers shall be restricted to the ones where the IDs
begin with KSDT, you will now execute the selection itself.
Go to the Migration Cockpit

(FIORI) and into your
project
r.
Click Select Data.

Click Start Selection.
Selection is completed.
Click 6 in order to see the

selected instances.
Six cost centers have been

selected from the ERP
source system.
Company code "0001" was

defined in the project
settings. Controlling Area
"0001" is assigned in the
customizing of your source
system to Company Code
"0001". From this Company
code, only the Cost centers
which begin with KSDT have
been selected (you defined
this in the modeler layer /
LTMOM).
46
Congratulations! You have

successfully finished the
exercises!
47
Exercise 5: Migrate Products

In this exercise we will select and migrate Trading Materials from a specific plant.
1.4 Check data in the Source System

Connect to system ABA and

choose Client: 800. Click
Connect.
This opens the SAP GUI on
your PC.
Use the login data from your

cheat sheet.
following login data:
You are now in

system ABA.
Enter in transaction
code bar SE16N in
order to have a look at
the existing Materials
in the source.

pressing the enter key.
Ent Enter table MARC in the

input field.
And in
Maximum No. of Hits field:
“99.999” .
Enter in field
PLANTS: “1000” .
Click Execute .
Cli
48
Now we know that we have

6’994 Products defined in
Plant 1000.
As a hint:
49
1.5 Create the project and adapt the data selection
Go to your FIORI
launchpad.
You probably have still
the FIORI open.
Click the tile Migrate Your

Data.
Create a new project as

you did in the other
exercises.
Type in, respectively

chose:
Name: Products_Ext_xxx
Scenario: SAP ERP to SAP

S/4HANA
Connection to Source
System: ABACLNT800
Dev.Package: $tmp
Company code: 1000
Flag migration object:

Product and move to the
Selected Migration.
Click “Review”.
Do not add the
predecessor objects.
Click “Do Not Add“.
Click “Create Project”.
Click on your project

Products_Ext_xxx.
50
Besides the project

creation, no other actions
have taken place so far.
To change the selection,

you use the migration
object modeler (LTMOM)
which is the modeling
layer.
To open the modeling
environment, firstly you
need to access the
S/4HANA system via SAP
Logon.
Open your SAP Logon.

Choose system S4R
(S/4HANA system).
Use the logon data from

the cheat sheet.
Enter transaction ltmom in

the transaction field and
confirm your entry by
51
You are now in the

modeling environment
(LTMOM) of the Migration
Cockpit.
Open the first drop-down

box and select the entry
Project by clicking it.
Enter your project name
Products_Ext_xxx in the
second box.

Please note: bringing up

the project definition takes
some time.
Change from display mode

to edit mode by clicking
Display <-> Change
You should see Change

Project Products_Ext_xxx.
52
Expand the row

"S4_MM_MATERIAL_N" by
clicking the arrow.
Then double-click on
“Source Tables”. This
opens a window on the
right-hand side.
Make sure you have the

display of Technical
Names turned on.
In the window at right-hand

side, double-click in the
first row on MARA. It
opens an additional section
on the right side.
53
Click on the tab selection

criteria.
Сlick on the arrow in
row MTART (Material
Type) and column
Selection.
This brings up a popup

which will enable you to
delimitate the selection in
table MARA.
Now, only Trading

Materials (HAWA) should
be selected when the
selection is executed in
the Migration Cockpit
(which is the execution
layer).
3. 1. Enter HAWA in the input

field.
4. 2. Click on the arrow
to execute to selection.
Click Copy .
54
Click OK.
Now you should see that

the arrow in the Table
Details MARA changed to
dark blue under MTART,
Selection column.
1. Click Save .
Double-click on MARC to
add the next selection
criteria.
We want to limit to Plant

1000.
55
Enter Plant 1000 and click

OK.
Click on Save.
Leave transaction
LTMOM.
56
1.6 Select data from the ERP source system and check the selection
result
Go to the Migration
Cockpit (FIORI) and into
your project
Products_Ext_xxx.
Click Select Data.

Click Start Selection.
Selection is completed.
2605 instances were

selected.
You can stop here. The Hint:

purpose of the exercise Plant 1000 does not exist in our target system (1010)
was to use more than Sales Org 1000 does not exist in our target system (1010)
one criteria. Division 00 should become 10
You can continue with Valuation area 1000 and 1200 do not exist (1010)
the mapping and try to
migrate as many as What do you need to do in order to load more than 3 items ?
you can (Challenge).
Congratulations! You have

successfully finished the
exercises!
57

WP05 Exercises MigrationObjectModeler 5.3 PDF

Uploaded by

Copyright:

Available Formats

WP05 Exercises MigrationObjectModeler 5.3 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WP05 Exercises MigrationObjectModeler 5.3 PDF

Uploaded by

Copyright:

Available Formats

Migration Object Modeler

S/4HANA Migration Cockpit

Preparation and login details ........................................................................................................................ 3

Exercise 1: Create a new migration object ................................................................................................... 4

Exercise 4: Migrate Cost Center ................................................................................................................. 39

1.1 Check data in the Source System .................................................................................................. 39

Exercise 5: Migrate Products ...................................................................................................................... 48

1.4 Check data in the Source System .................................................................................................. 48

Preparation and login details

Exercise 1: Create a new migration object

Login to SAP GUI and call transaction

Select “Project” in the drop-down menu.

Press button to see the list of

NOTE: If you have not created a project

Click on More >> Project >> Create

Make sure your project is selected.

Define the following parameters:

Migration Object ID: BANK_DATA_XX

Name of Function Module:

For the configuration “Objects for

INFO. These settings specify how the

Process One Instance at a Time: The

Note that this can negatively impact

Process Multiple Instances at Once: The

INFO. If the function module encounters

Parameter That Returns Result: The

Include for Handling Return Parameter:

INFO. If you want to simulate a data

Confirm that all parameters have been

Press to create the object.

Now that the object is created you can

Click the button “Display <-> Change”

First you will work on the source

Right click on “Source Structure” in the

Confirm the message with Yes.

In the resulting screen you can now

Define the fields as showed in the

HINT: Pay attention to select the “Key

Now you will define how this structure is

To do that right click on the structure in

INFO. You can use these views to

Press to make sure your work

You can now click on the “Target

This structure is automatically derived

INFO. Here you can get an overview of

tables. You can check the attributes of

Drag the source structure in the middle

Press to make sure your work

Double-click on the “Field Mapping” area

INFO. In the field mapping area, you can

Right click on the field “Bank country

Select “Yes” to accept the proposal.

Note: this is a new feature available

Rule called “CVT_LAND1” will be

Define the import parameter

Now right click on the field “Bank keys”

Use the function “CVT_BANKL” and in

INFO. The second possibility to assign a

Drag and drop the field BANKNAME to