Unit 1: Getting Started With The Migration Object Modeler

Week 2: Migration Object Modeler (File/Staging)
Unit 1: Getting Started with the Migration Object

Modeler
Getting Started with the Migration Object Modeler
SAP S/4HANA migration cockpit – file and staging approach (recap)
Data provisioning Process & content Data load
Template file upload

API-based
Staging* SAP S/4HANA Cloud
SAP S/4HANA
SAP S/4HANA Cloud 1911: 100+

SAP S/4HANA 1909: 80+
Migration objects *Available for on-premise as of 1709 FPS02, available for cloud on request
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
Introduction
Typical Questions:
▪ How can I adapt the delivered content to my customers' needs?
▪ Is it possible to adjust the existing SAP migration objects? SAP S/4HANA
▪ I am missing a field in my Excel template or staging table – how can I add this field?
▪ How can I adjust the selection of data for the direct transfer approach?
▪ How can I create my own migration objects to transfer customer-specific data?
Migration Object Modeler: Modeling Environment of the SAP S/4HANA Migration Cockpit

Modeling environment of the SAP S/4HANA migration cockpit
Flexible and Extendable
Easily integrate custom objects and enhancements into the migration project SAP S/4HANA
▪ Customer-specific enhancements to SAP standard objects delivered with the SAP S/4HANA
migration cockpit
– Easily adjust input structure (file/staging)
▫ Add new fields
▫ Hide a field in the template
– Add or change migration object selection criteria (direct transfer)
– Map structures and fields
▪ Integration of newly created objects:
– Custom objects Transaction:
– SAP standard objects that are not yet in the scope of the SAP S/4HANA migration cockpit LTMOM
– Use standard APIs or code your function module
▪ Available for SAP S/4HANA and included in this license
Focus of this week – file and staging approach
Unit 1: Getting Started with the Migration Object Modeler

Unit 2: Copying and Extending Delivered Content SAP S/4HANA
Unit 3: Creating your Own Migration Object

Unit 4: Creating your Own Translation Objects and Rules
Unit 5: Simulating and Debugging a Migration Object

Transaction and role
To start the migration object modeler, use transaction

/nLTMOM.
NOTE:
To run the necessary transaction, your user needs the following role:
SAP_CA_DMC_MC_DEVELOPER

Demo
Migration Object Modeler

Getting Started (based on 1909)

SAP Logon settings in the demo system
In the demo system the following SAP Logon

setting was used:
• Corbu Theme
• “Accept SAP_Fiori visual theme” unmarked
Note: Depending on the theme you have chosen,

the screens in the migration object modeler may
look different, especially if the SAP_Fiori option is
marked.

Transaction and role
To start the migration object modeler, use transaction

/nLTMOM.
NOTE:
To run the necessary transaction, your user needs the following role:
SAP_CA_DMC_MC_DEVELOPER

Migration object or migration project overview
You can select either the migration object screen

or the migration project screen.
When you open a project, you can view all objects

that are assigned to your project in one central
location, for example you can view all the
migration objects and rules for a project.

Source structures
Under Source Structures, you can adjust the source structure so that your data can be transferred to the
SAP S/4HANA system.
Example: You can add a new field and specify the relevant information for the field.
Choose ‘Insert Field’

As of 1909
Source structures – Download XML file
The XML template file can be downloaded via LTMOM as well (in source structure definition).
The button to download the XML file is available in the

header section if the Source Structures screen is selected

Target structures
Under Target Structures, you can get an overview of the target structures associated with the migration
object.
Structures can be single fields, multiple fields, or tables.
Example: Before you add a new field to the source structure, you can determine which target structure the source field
should be mapped to.

Structure mapping
Under Structure Mapping, you can check how the source structure is mapped to the corresponding target
structure.
As a prerequisite, the source structure must be mapped to a target structure before you can map the fields
of the source to the target structure (see Field Mapping).

Field mapping
Under Field Mapping, you can map fields from the source structure to fields in the target structure.
Simply drag the relevant field from the left-hand side to the target structure field on the right-hand side.
If a field from a source structure has been mapped to a target field, the system displays a green icon, and a
red icon if it has not been mapped.
Filter for mapped/ unmapped fields

Additional information
Information
Generate Runtime Object Display Generated Function Group
▪ Generate Runtime Object: In this activity, the application generates the programs required to read data
from the source system and to transfer data to SAP S/4HANA.
▪ If required, you can view the function modules (internal SAP programs) that facilitate the transfer of data to
the SAP S/4HANA system. To view the function modules, choose Display Generated Function Group.
▪ To view additional information and documentation on the migration object modeler you can choose the
Information icon.

Documentation
Information button
Depending on the migration

approach, different
documentation is shown when
you click the information button.

Outlook

Unit 2: Copying and Extending Delivered Content
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.
Unit 2: Copying and Extending Delivered Content
Copying and Extending Delivered Content
Creating a migration object from a template
Create a migration object from a template

▪ The available functionality is the same as when you
select a migration object in a migration project in the SAP
S/4HANA migration cockpit.
▪ Link to the delivered SAP content is still available
▪ If SAP updates the delivered content, this migration
object will be updated. You can ignore the content
update.
▪ You cannot make changes to the delivered fields
(e.g. change the length of a character field), but you can
add additional fields, which are then marked as customer
fields.

Copying a migration object
Copying a migration object

▪ The link to the delivered SAP content is no longer
available.
▪ The migration object is similar to a migration object you
created yourself.
▪ If SAP updates the delivered content, this migration
object will not be updated.
▪ You can make any changes you want to this migration
object, as all fields are marked as customer fields (similar
to a migration object you created yourself).
▪ Migration objects can be copied from a staging migration
project into a file migration project and vice versa.

Creating a migration object
Create a user-defined migration object

If you have specific requirements that are not covered by the
migration objects provided by SAP, you can create user-
defined migration objects.
Will be shown in detail in Unit 3

Change view of source structure / source structure fields
You can change the

view of a source
structure or source
structure field
▪ You can choose the following options: visible, not visible, required
▪ At least one field must be visible if the corresponding structure is visible
▪ A warning is shown if a key field is set to not visible

Add new source structure to a lower level
For a newly added structure, you must establish a

foreign key relationship to a structure at a higher
level. To do this, choose the Foreign Key
Relationships button.
The foreign key relationship models how the structures in a migration object relate to each other.
For each primary key field in the foreign key (child) table, at least one relationship to the check (parent) table
must exist (either to a key field or to a non-key field).

Exclusion of fields/structures in the target structure
Exclusion of fields/structures in target structure settings
▪ Reason: Improves performance during design time when dealing with a complex object and makes
modeling easier
▪ Exclude target structures, which are optional in the corresponding function module and which are not
mapped to any source structure. These target structures no longer appear in the UI of LTMOM.

Favorite list
You can add projects and migration objects to favorite lists, which are available when you
start transaction LTMOM.

Demo - Copying and extending a migration object

Copying and Extending a Migration Object (based on 1909)
Steps shown in the demo:

(1) Adjust bank master migration object
− Add field Post_Bank (Char, 16) to migration object bank
− Change view of bank master fields Bank branch and Bank group
to not visible
− Download the template
(2) Create a migration object from a template (Cost center)
(3) Copy a migration object (G/L account)

Outlook

Unit 3: Creating Your Own Migration Object
Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Creating Your Own Migration Object
Creating Your Own Migration Object
Creating a migration object
Create a user-defined migration object

If you have specific requirements that are not covered by
the migration objects provided by SAP, you can create
user-defined migration objects. These user-defined
migration objects have the following restriction: A function
module or (CDS) behavior definition must populate the
target structure with data.

How-to guide: How to create your own migration object
Good to know
▪ User guide on how to create your own migration object available.

▪ This guide contains information about how to create your own migration objects using the migration object
modeler for the migration approaches "Migrate Data Using Files" or "Migrate Data Using Staging Tables".
▪ How-To Guide: Creating a New Migration Object with the Migration Object Modeler (file/staging)
▪ Or check SAP Note 2852819

Prerequisites for creating your own function module
Good to know
▪ As a starting point, read the attachment for SAP Note 2590165 to create your own function module.
Important prerequisites
▪ The function module must not execute the COMMIT WORK command. The SAP S/4HANA migration
cockpit handles the COMMIT control.
▪ The function module must use the ABAP Dictionary structure BAPIRET2 as a structure to return messages
to the migration object modeler.
▪ The function module should provide a test run flag so that it can be run in test mode to simulate the
creation of data in the target system.

Demo – Creating your own migration object

Creating your own migration object (based on 1909)

(1) Create your own migration object to add different language
texts for already created cost centers
− Use API BAPI_COSTCENTER_CHANGEMULTIPLE
(2) Create / Upload source structure
(3) Map source structure to target structure
(4) Do the field mapping with automated rule proposal
(5) Download Excel template

As of 1809
Field mapping – Rule proposals I
Good to know
Expert function available to have an automated rule proposal for the target fields in the field mapping
screen. This feature is intended to help you with the creation of your own migration objects.
If you change the rules in delivered migration objects based on the rule proposals, there will be
no content support.

As of 1809
Field mapping – Rule proposals II
▪ On the Rule Proposals screen, you can view whether rule proposals exist for the fields in the target structure.
▪ Matching rule proposals are based on domain and data element assignments in the respective rule.
▪ In addition, if a field in a target structure has the same name as the field in the source structure, the system
proposes a MOVE rule.
Documentation on Rule Proposals available
The following status values are possible:

▪ Exactly one rule proposal exists (green LED icon)
▪ More than one rule proposal exists (yellow LED icon)
− If more than one rule proposal exists for a field, you can view them in the dropdown list.
As of 1809
Field mapping – Rule proposals III
Select the rules

you want to use
The system displays the information about where the field-based rule was created in brackets:
▪ (S): Subproject-Specific; the rule was created at subproject level and can be used by all migration objects
in that subproject.
▪ (M): Migration-Object-Specific; the rule was created at migration object level and can only be used by that
migration object.

Outlook

Unit 4: Creating Your Own Translation Objects and Rules
Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Creating Your Own Translation Objects
and Rules
Creating Your Own Translation Objects and Rules
Rules
You can use rules to change the values that are migrated from source fields to target fields.
Field-based rules: can be used to change the value of a

target field during the migration.
Event-based rules: custom coding can be inserted at
predefined points of processing an event (for example, at
Start of Loop or Start of Record).
Internal rules: can be called by field-based rules or event-
based rules. This allows you to separate code into different
modules, which can then also be shared by other field-
based rules or event-based rules.
Rules that are created on project/subproject level can be

used by all the migration objects in the project. Rules that
are only created on migration object level can only be used
for this specific migration object.
Translation object
A translation object defines how values from a specific field in the source system must be translated to target
values during the data migration. You need to assign a translation object to a field-based rule; it cannot be
assigned directly to a target field.
Example
The following values from the Country field in the source
system must be translated to different target values:
Germany → DE
United Kingdom → GB
America → US
In this case, you create a translation object called Country
and assign it to a field-based rule, and assign the rule to the
corresponding target field.
Translation rules can be created on project/subproject level

or on migration object level. If you create them on migration
object level, the value mapping is only available for this
single migration object.
Demo – Creating your own translation object and rule

Creating your own translation object and rule (based on 1909)

(1) Create a translation object for the controlling area (KOKRS) called
MAP_KOKRS_OWN
(2) Create a field-based rule (CVT_KOKRS_OWN)
− Call the translation object (MAP_KOKRS_OWN)
− Add your own message
− Add a pattern

Outlook

Thank you.
open@sap.com
Follow all of SAP

warranty.
Simulating and Debugging a Migration Object
As of 1809
Simulate import of file migration objects
Simulate Import in LTMOM Save First Erroneous Record for

Debugging
Only available in change mode
Debug Saved Record Delete Saved Record

Program: DMC_MC_MIGOBJ_EXEC_SINGLE_OLO Program: DMC_MC_MIGOBJ_EXEC_OLO_DELETE

As of 1809
Prerequisites for debugging – File approach
You need to download a file template using ▪ The migration object was generated successfully
either transaction LTMC or transaction LTMOM
(possible as of 1909). You can then enter
▪ A simulation parameter is defined in activity
values in the file that you want to simulate or Target Structures API
debug. ▪ The migration object is not locked by any other
user
▪ If the migration object is copied from a template, it
must not have any outdated objects (Update
Available  No)

As of 1809
Steps to execute a simulation run for debugging – File approach
Documentation on Simulation / Debugging
1. Choose the migration object

2. Select the filled template Excel-XML file
3. Choose Execute (F8)
The file that you upload is only stored

temporarily for the duration of the
simulation, and is then deleted from
the system.
Program: DMC_MC_MIGOBJ_EXEC_FILE

As of 1809
Breakpoints for debugging – File approach
You can choose two breakpoint options

▪ Before the conversion takes place
▪ Before the data is written to the target
system
Note: This option will not be visible for
productive systems

As of 1809
Debug in target system – File approach
Option to save data if error occurs

If you choose this option the system will
save the relevant information about the first
erroneous record that was encountered in
the file.
As of 1909 you can view the simulated

records
▪ You can view these records before they
are converted
▪ or after they are converted

As of 1809
Debug and delete debugging run – File approach
To debug the saved record in the target system, you can choose
Goto → Debug Error (program DMC_MC_MIGOBJ_EXEC_SINGLE_OLO)
To delete the saved simulation run choose
Goto → Delete Run (program DMC_MC_MIGOBJ_EXEC_OLO_DELETE)

Simulating and Debugging a Migration Object As of 1809
Simulate import of staging migration objects FPS01
Simulate Import in LTMOM Save First Erroneous Record for

Debugging
Debug Saved Record Delete Saved Record

Program: DMC_MC_MIGOBJ_EXEC_SINGLE_OLO Program: DMC_MC_MIGOBJ_EXEC_OLO_DELETE

Simulating and Debugging a Migration Object As of 1809
Simulate import of staging migration objects II FPS01
Additional information available
You can choose one of the following options

to decide which entries should be taken for
the simulation:
▪ Select All Records
▪ Select Max. Number of Records (random)
▪ Select Specific Records (there is currently
a technical restriction that the specific
selection is not case-sensitive)
Program: DMC_MC_MIGOBJ_EXEC_STAGING
Migration object modeler – Simulate import / downport for lower releases
SAP Note 2665339 contains program DMC_MC_SIMULATE_IMPORT_STAGING to perform an

import simulation for a staging migration object for 1709 FPS01 and FPS02 and for 1809.
SAP Note 2630183 contains program DMC_MC_SIMULATE_IMPORT_FILE to perform an import

simulation for a file migration object for 1709 FPS01 or FPS02.

Key takeaways
Migration object modeler: modeling environment of the SAP S/4HANA migration cockpit
Available for SAP S/4HANA

SAP S/4HANA
Transaction:
LTMOM
Flexible and extendable
Easily integrate custom objects and enhancements into the migration project
▪ Adapt the delivered content (SAP migration objects) to your needs
▪ Add a field in the Excel template or staging table
▪ Create your own migration objects to transfer customer-specific data
▪ Create your own rules to add customer-specific messages or masking/pattern rules
Outlook
Week 3: SAP S/4HANA Migration Cockpit – Direct Transfer Approach

Unit 1: Getting Started
Thank you.
open@sap.com
Follow all of SAP

warranty.

Unit 1: Getting Started With The Migration Object Modeler

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

Unit 1: Getting Started With The Migration Object Modeler

Uploaded by

Copyright:

Available Formats

Week 2: Migration Object Modeler (File/Staging)

Unit 1: Getting Started with the Migration Object

Data provisioning Process & content Data load

Template file upload

Staging* SAP S/4HANA Cloud

SAP S/4HANA Cloud 1911: 100+

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Flexible and Extendable

Unit 1: Getting Started with the Migration Object Modeler

Unit 3: Creating your Own Migration Object

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

To start the migration object modeler, use transaction

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Migration Object Modeler

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

In the demo system the following SAP Logon

Note: Depending on the theme you have chosen,

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

To start the migration object modeler, use transaction

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

You can select either the migration object screen

When you open a project, you can view all objects

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

The button to download the XML file is available in the

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Generate Runtime Object Display Generated Function Group

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

Depending on the migration

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

Week 2: Migration Object Modeler (File/Staging)

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

Create a migration object from a template

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Copying a migration object

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Create a user-defined migration object

Will be shown in detail in Unit 3

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

You can change the

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

For a newly added structure, you must establish a

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Exclusion of fields/structures in target structure settings

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Migration Object Modeler

Steps shown in the demo:

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Week 2: Migration Object Modeler (File/Staging)

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

Create a user-defined migration object

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

▪ User guide on how to create your own migration object available.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Migration Object Modeler

Steps shown in the demo:

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6