SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For File - Staging

SAP S/4HANA 2020 - Migration Cockpit
Getting started with the migration object modeler

Migrate data using staging tables
October, 2020
Version 1.0
PUBLIC
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
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, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Document History
Revision Date Change
1.0 03.11.2020 Release for customer

Agenda
SAP S/4HANA Migration Cockpit (Short recap)
Migration object modeler
Getting started
Copying and extending delivered content
Creating own migration objects
Rules & translation objects
Tips & tricks
Simulation & debugging
Further Information

SAP S/4HANA migration cockpit
Short recap
SAP S/4HANA migration cockpit at a glance
Data migration to SAP S/4HANA: easy, safe, and accelerated
Key facilitators
▪ Out-of-the-box
▪ Available for SAP S/4HANA and SAP S/4HANA Cloud, included in licenses
▪ Preconfigured migration objects
▪ No developer skills required
▪ Step-by-step guidance through the migration process
▪ Preconfigured migration objects and rules
▪ Automatized cross-object value mapping
Migration object modeler for custom requirements

Powerful and easy-to-use state-of-the-art modeling environment (SAP S/4HANA
only)

SAP S/4HANA migration cockpit – different migration approaches
This presentation deals with this migration approach

Transfer data using files
▪ Download template file for relevant migration object
▪ Populate file with relevant business data
▪ Upload file to the SAP S/4HANA migration cockpit
Combined into
Migrate data using
staging tables
Transfer data using staging tables in Fiori UI
▪ Staging tables are created automatically
▪ Populate staging tables with business data
▪ Transfer data from staging tables to target SAP S/4HANA system
Transfer data directly from SAP System Migrate data directly from SAP
▪ Transfer data from SAP ERP source system to target SAP system
S/4HANA system
▪ Access source system via RFC connection in Fiori UI
▪ Supports data migration scenarios from other applications

SAP S/4HANA migration cockpit – migrate data using Staging Tables
Fiori App Process & content Data load

Migrate Your Data
API based
MS_Logistics
SAP S/4HANA Cloud

Staging Tables
Excel XML template files

SAP S/4HANA EX 2102*
or other tools of choice SAP S/4HANA OP 2020
SAP S/4HANA OP 2020: +115
*Current state of planning

Migration objects

Complete overview presentation
SAP S/4HANA Migration Cockpit 2020 / CE2008

Introduction
Typical Questions:
▪ How can I adapt the delivered content to my customers' needs?
▪ Is it possible to adjust the existing SAP migration objects?
▪ 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

Flexible and extendable
Easily integrate custom objects and enhancements into the migration

project
▪ Customer-specific enhancements to SAP standard objects delivered with the

- Easily adjust input structure
- Map structures and fields
- Add or change migration object selection criteria (Direct Transfer)
▪ Integration of newly created objects
- Custom objects
- SAP standard objects that are not yet in the scope of the SAP S/4HANA migration cockpit
- Use standard APIs or code your function module
Transaction:
LTMOM
Migration object modeler for direct transfer
Migration Object Modeler (Direct Transfer)

Getting started
Transaction & role
To start the migration object modeler you use transaction /nLTMOM.
NOTE:
To run the necessary transaction your user needs the following role:
SAP_CA_DMC_MC_DEVELOPER

SAP Logon settings for the screenshots
In this presentation the following SAP Logon setting was used:

▪ Blue Crystal 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
Accept Belize theme option is marked.

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.

Migration object detail screen - overview
On the Migration Object Details Screen you get the information, for which
approach the migration object was created. Projects, which were created
with transaction LTMC are classified as “old” as of 2020.
▪ Migrate Data Using Files (old)
▪ Migrate Data Using Staging Tables (old)
▪ Migrate Data Using Staging Tables

Migration object detail screen - details
Functionalities
Migration Object Detail Screen
▪ It is possible to define the active view for a

migration object in the migration object detail
screen. You can change this view in the Fiori App
too.
▪ It is possible to maintain max no. of data transfer

jobs. Alternatively you can use the Job
Management Screen in the Fiori App to change
the maximal number of jobs for a specific
migration object.
▪ Application component for customer specific

objects is supported.

Migration project / migration object detail screen – client dependency
Client Dependency
Migration Project / Migration Object Detail Screen
▪ Projects created in Fiori App can only be seen and

changed in the client where the project was
created.
▪ The client information can be seen either in the

migration project or the migration object detail
screen.
This does not apply for projects created with LTMC.

Global data
For each migration object, you can specify Global Data that contains code that defines ABAP variables and ABAP types for
later use. You can also specify code-related elements, such as macros if required.
For migration object delivered by SAP, you get information on name, first release, used API and Wrapper and the migration
object change history.

Source structures
Under Source Structures, you can display and 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’

Source structures – download XML file
The XML template file can be downloaded via LTMOM (in source structure definition)
The button to download the XML file is available in the header

section, if the Source Structures screen is selected as of 1909.

Source structures – views
SAP provides predefined views for migration objects. You can use these views to adjust the fields that are available in the
template file and in the staging tables.
Example for template file: If you change a field from Visible to Not Visible and save, the field will not be displayed in the relevant template file.
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

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.

Target structures – function module
Under Target Structures, you can double-click the root structure to view detailed information about the function module
that transfers the business object instance to SAP S/4HANA.
As of SAP S/4HANA 2020 CDS behavior definitions are supported in addition
Forward navigation to SE37/SE38 on target structure screen is possible as of 1909

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)

Getting Started with the migration object modeler
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 functionality
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.

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 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 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.
Variables
You can create variables for migration objects. The advantage of creating variables is that only one operation is needed (for
example by a rule at a BEGIN_OF_LOOP event) to calculate the variable. Rules that are later used at record level can then
access this variable, and use the variable in their code accordingly. Without variables, the rules would need to calculate the
variable for each record again and again.
For variables, the following options are available:

▪ Elementary Type
An elementary type is defined as a data type of fixed or variable length
that is neither structured nor a table type or reference type.
▪ Structure
A structure is a complex type and consists of components that can have
any type (data element, structure, table type or reference type).
▪ Table
A table is defined as a tabular array of data in the ABAP Dictionary
Where-Used List
You can use a where-used list to view information about the rules where
the variable is used.
Link to Click-Through-Tutorial
Migration object modeler –
getting started
Learning Hub Subscription necessary (SAP Learning Hub Solution Editions)

General information
As long as you use the delivered migration objects with their delivered settings, SAP ensures the correctness of
the migration object.
As soon as you start to adapt the delivered migration object, please take care, that SAP only
supports content issues based on the original template. For further information on support for
extended pre-delivered migration objects, please check the following SAP Note 2481235.

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.

Creating a migration object from a template – example Cost center
In the “Create Migration Object from Template” Wizard you get a list of migration
object templates, which you can choose. Migration objects, which are already part
of the migration project are not listed anymore.
Cost Center copied from Template
Fields cannot be changed. They are not

marked as Custom Field.

Creating a migration object from a template – custom view
If you want to change the view of a migration object you

can create a custom view and adapt it to your needs.
Custom View: As a default mandatory fields are marked as

required, all other fields are marked as visible, but you can
change them to your specific needs.
Change the Active View of your migration object to

Custom Scope, so that your view settings are used.

Creating a migration object from a template – content update
Content update
If a migration object must be updated, the system will prompt you to do so. To update a migration object with content
from SAP, choose Update Object.
Note that if a migration object must be updated by SAP, and it contains any custom modifications, you should
save any modifications that you want to keep for future use before proceeding.
You can choose the option Ignore Content Updates.
If you choose this option, the system will permanently ignore content updates for the migration object. To enable
content updates again for the migration object, you must delete the existing object and copy it again from a template.

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.
For projects created with the new Fiori App (as of 2020): You can copy a migration object
from another client or from a project, which was created with transaction LTMC.

Copy a migration object – example
Example: Copy a cost center migration object
In the Copy Migration Object Screen you can choose from which project
and migration object a copy should be done. The client and Mass transfer
ID will be filled automatically based on the target project.
Cost Center copied from another cost center migration object
The new created migration object is

treated as an own migration object.
Updates and Modification is Not
Applicable.
If you want to completely disconnect from content upgrades for a specific migration object, you should also
copy the linked includes in the target structure section to your customer namespace and assign them.
Copy a migration object and deleting a migration object
Example: Copy a cost center migration object

Cost Center copied from a cost center migration object
Fields can be changed (e.g. data type,

length,…). The fields are marked as
Custom Field.
Deleting a Migration Object

You can delete a migration object from your project. In the migration object, in the menu, choose Migration Object ->
Delete Migration Object. You can also delete a migration object by right-clicking the migration object in the hierarchy
and choosing Delete Migration Object.
If the staging tables are filled with data, (e.g. one or more files have been uploaded for a migration
object), then the migration object cannot be deleted.
Add new source structure to a lower level
For a migration object, source structures are organized in a hierarchy. You can add additional structures to
the hierarchy, and remove structures from the hierarchy.
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
You can 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.
▪ Improves performance during design time when dealing with a complex object and makes modeling easier.

Structure mapping preview
Structure mapping
To map a source structure to a target structure, drag

a source structure from the left-hand side to the
relevant target structure on the right-hand side.
The suffix << Name of Source Structure, will be

added.
You can check whether any errors exist for the

mapped structures.
You can view how the function module populates the

target structures with data in the Structure Mapping
Preview.

Structure mapping dialog box
Structure mapping dialog box

To view how a source structure is mapped to a target structure, double-click a target structure.
An access type specifies how the system

accesses the target structure. For example, the
system can access all lines of a table, or just a
single line of a table. An access type has an
associated mapping type.
You can check the documentation for more information on the access type, mapping
type and data path type.

Field mapping
Field mapping
To map a field from a source structure to a

target field, drag the relevant field from the
source structure field to the target structure
field. The resulting mapping operation is a
simple 'MOVE' operation.
For more complex requirements, you can
use rules (e.g. CVT_KOKRS)

Field mapping
Functionalities
A mapping check can be performed, which lists incomplete mappings (i.e. missing parameters) as
errors as well as source fields, which haven't been assigned to any target field yet as warnings.
In the field mapping section, source fields that are

not mapped are identifiable with a different icon.

Migration object modeler –
adding an additional field

Creating an own migration object
General Information
As soon as you start to adapt the delivered migration object or create an own migration object,
please take care, that SAP only supports content issues based on the original template. For
further information on support for extended pre-delivered migration objects, please check the
following SAP Note 2481235.

Creating a user-defined 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 restrictions, a function module or (CDS) behavior definition
must populate the target structure with data.

Creating a user-defined migration object - example
Example
If you use the migration object cost center, you can only create the description of the cost center in one language. If you
need to add descriptions for additional languages, you need to create your own migration object to handle this. In our
example we will create a migration object to add description in additional languages to a created cost center.
Used BAPI for the own migration object: BAPI_COSTCENTER_CHANGEMULTIPLE
If you use Standard APIs, delivered by SAP, please check, that they are released for customer.
As of SAP S/4HANA 2020 besides function module, (CDS) behavior definition can be used to transfer data to SAP
S/4HANA. Examples for migration objects, which use (CDS) behavior definitions, are ECM – Change Master and
QM – Quality Info Record in SAP S/4HANA Cloud.

Creating a user-defined migration object – wizard
1. Enter a name, define the target structure using, select the relevant settings and confirm your entries.
The Mass Transfer ID will be added automatically.
Choose the target structure: Function Module.
Enter BAPI_COSTCENTER_CHANGEMULTIPLE
In the field Parameter that Returns Result you

can select the function module parameter,
which returns the messages. In our example:
RETURN.
To enable simulation mode, specify the

parameter of the function module that
activates this mode in field Parameter for
Simulation. In our example: TESTRUN and
Value for Simulation X.
Creating a user-defined migration object – wizard
2. The new migration object will be created. In our example: Z_KOSTL_TXT_OM1
The fields Modified and Update Available are

not applicable for own created migration
objects.
The Custom Scope view is automatically

assigned as Active View.

Creating your own migration object
Creating a user-defined migration object – source structure
3. Create the relevant source structure. For a migration object, source structures are organized in a hierarchy. You can add
additional structures to the hierarchy, and remove structures from the hierarchy.
Choose Append Structure to Lower Level.
Enter a name and description.
Add the necessary fields.
To add source structure fields by using a text-

file, choose Upload Source Structure List.
Maximal key length: The sum of all field length for the keys on the top level source structure
including separators must not exceed 200 characters.
Creating a user-defined migration object – structure mapping
4. Maintain the structure mapping.
To get an overview of all existing

Drag the source structure to the target structure mappings for the migration
structure. Start with the HEADER. A source object, choose Structure Mapping
structure (or structures) must be mapped to a Preview.
target structure in order to map the fields of
the source structure to the fields of the target
structure (in the area Field Mapping).
If a target structure has the suffix << Name of Source Structure,

this means that a source structure is mapped to this target
structure.
Creating a user-defined migration object – field mapping: rule
5. Maintain the field mapping by adding a rule.
To assign a rule to a target field right-click the

field and choose Assign Rule.
You can either choose an existing rule or create an own rule. If

you choose the Assignment Proposal button, the system
proposes a rule.
Select the relevant parameter value from the drop-down menu.

Creating a user-defined migration object – field mapping: MOVE operation
6. Maintain the field mapping via drag and drop.
To map a field from a source structure to a

target field, drag the relevant field from the
left-hand side to the target structure field on
the right-hand side. The resulting mapping
operation is a simple 'MOVE' operation.
If a field from a source structure has been mapped to a target field, the system displays a green
icon beside the name of the field.
Creating a user-defined migration object – field mapping: filter
7. Show fields with mapping. Don‘t forget to save your changes.
Filter on Show Fields With Mapping to have

an overview, which rules you have assigned.
Rule Assignment for our example Cost Center Text

Source Target Structure Target Field Rule
Field
KOKRS R_CONTROLLINGAREA CONTROLLINGAREA CVT_KOKRS
KOKRS R_COSTCENTERLIST COSTCENTER CVT_KOTSL

KOSTL
LANGU R_LANGUAGE LANGU CVT_SPRAS
VALID_FROM R_LANGUAGE VALID_FROM MOVE
VALID_TO R_LANGUAGE VALID_TO MOVE
KTEXT R_LANGUAGE NAME MOVE
LTEXT R_LANGUAGE DESCRIPT MOVE

Creating a user-defined migration object – generate runtime object
8. Generate the runtime object to check for errors.

Creating Your own migration object
Creating a user-defined migration object – rule proposal
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.

Creating a user-defined migration object – rule proposal II
▪ On the Rule Proposals Overview, 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.
Creating a user-defined migration object – rule proposal III
Select the rules

you want to use
The system displays the information 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.

How-to-Guide: How to create an own migration object
Good to know
▪ User guide on how to create an 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 modules
Good to know
If you want to create an own migration API please read as a starting point the documentation linked in SAP Note 2590165 .
Direct link to documentation: https://www.sap.com/documents/2020/05/44a27c28-977d-0010-87a3-c30de2ffd8ff.html
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 SAP
S/4HANA migration object modeler.
▪ The function module should not throw exceptions, this could lead to log of data sets.
▪ 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.
▪ If internal numbering is used, the new keys should be returned.

Migration object modeler -
creating an own migration object

General information
As soon as you start to adapt the delivered migration object or create own rules and translation
objects, please take care, that SAP only supports content issues based on the original
template. For further information on support for extended pre-delivered migration objects,
please check the following SAP Note 2481235.

Short recap
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 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.
Short recap
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 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.
Creating user-defined rule and translation object - example
Example
We will create a field-based rule (ZCVT_KOKRS), which will call the translation object for controlling area
(MAP_KOKRS_OWN). In addition we will add an own message and an own pattern within this rule.
Translation objects cannot be assigned directly to a target field. You need to assign a
translation object to a field-based rule or call the translation object in your field-based rule
and then assign the rule to the corresponding target fields.

Creating a user-defined rule
Create a user-defined rule
If you have specific requirements that are not covered by the delivered content, you can create your own rule.
Right-click Translation Objects, and choose

Create Translation Object.
Rules can be created on subproject level or on migration object level. If you create them on
migration object level, the rule is only available for this single migration object.
Creating a user-defined rule – name, description and parameters
1. Enter a technical name for your rule, a rule description and maintain the import and export parameter.
Enter a technical name for your rule in the customer namespace, e.g. ZCVT_KOKRS.
Enter a description for your rule.
Enter an import parameter name,

e.g. I_PARAM.
Enter an export parameter name,

e.g. E_PARAM.

Creating a user-defined rule – rule properties
2. Decide, which rule type you want to create. A rule can be based on a translation object, a fixed value or it can be a free
code rule.
By default, Free Code rule is

suggested. Press the change button
to see and select your preferred
choice:
▪ Free code
▪ Translation Object
▪ Fixed Value

Creating a user-defined rule – based on translation object
3. If you choose Translation Object, you need to enter the related translation object. In our example we assigned
MAP_KOKRS. Do not forget to save your changes.
If you choose translation object

as rule type and assign the
relevant translation object, you
cannot enter additional coding, if
this is necessary.
Import and Export Parameter are

suggested automatically.

Creating a user-defined rule – based on free code
4. If you want to add additional own coding for the translation object, you need to choose free code and enter your own code
including the call of the translation object.
Open the editor to enter your own

coding.
Syntax Check and Pretty Printer is

available.
Pseudo code to call the translation

object MAP_KOKRS. The suffix _S
means, that the translation object is
created on subproject level and can
be used in the whole project.

Creating a user-defined rule – free code example I
Example Coding (part 1):
To change the export parameter with a

masking rule, you first assign the import e_param = i_param.
parameter to the export parameter.
"If import value starts with 'US' change export value

You add an own pattern. Example to start with '00' instead.
pattern: ‘US’ should change to '00’. if i_param(2) = 'US'.
e_param(2) = '00’.
" Warning Message, that value has been changed

You can print own warning message, allog_msg 'W' 'AD' '010'
that the value has been changed. 'Controlling Area has been changed from' i_param ‘to’
e_param ‘’.
If no pattern is assigned, the mapping

tasks should be called to maintain a else.
value mapping.
Creating a user-defined rule – free code example II
Example Coding (part 2):
Suffix _S, means, that the translation " Use Template TRANSLATE (pseudo code)
object had been created on subproject
level. Otherwise, if the translation
object was created on migration object " call translation object MAP_KOKRS_S
level you must add _M.
mwb:translate(['MAP_KOKRS_OWN_S']
Pseudo code to call a translation [e_param]

object.
[i_param]).
endif.
Save your changes and do a syntax check.

Creating a user-defined rule – assign to target field
5. Assign your own created rule to the relevant target field.
Save your changes and generate the migration object to check for any syntax errors.

Creating a user-defined translation object
Create a user-defined translation object
If you have specific requirements that are not covered by the delivered content, you can create your own translation
objects to specify how values from a specific field in the source system must be translated / mapped to the target values
during the data migration.
Right-click Translation Objects, and choose

Create Translation Object.
Translation rules can be created on 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.
Creating a user-defined translation object – name, description and parameters
1. Enter a technical name for your translation object, a description and maintain the import and export parameter.
Enter a technical name for your rule in the customer namespace, e.g. ZMAP_TEST.
Enter a description for your

translation object.
Enter an import parameter name, a

data type and the parameter length.
Enter an export parameter name, a

data type and the parameter length.

Creating a user-defined translation object – value range
2. Add a value range for the export parameter, if applicable. You can also choose Case-Sensitive for the parameters, if
necessary.
Choose the Add button to add a value

range.
If this indicator is set, the system You can choose the following options
differentiates between capital and to determine the value range:
lower-case letters for the input. If this ▪ Use Domain
indicator is not set, then the input will ▪ Use Value Table
be converted to upper case. ▪ Use Search Help
▪ Do Not Use Value Range
If you mark the flag Validate

Parameter Value against Domain
the system checks, whether the
parameter is valid. If the parameter is
part of the range of values defined for
the domain, then it is considered
valid.

Creating a user-defined translation object – additional settings
3. Choose additional settings for the source fields. Do not forget to save your changes.
If the source field contains its initial value then the initial
value is ignored by the translation object.
If the value of the source field is not yet available in the

conversion table (mapping task), the system creates an
entry in the conversion table using the value of the
import parameter and an initial value for the export
parameter.
If a value of the source field does not exist in the

conversion table, the system can use one of the defined
parameters to determine the target value. In our
example the first import parameter will be used as
suggested value for the target field.
Check the system documentation for further information on the different settings.

Creating a user-defined translation object – assign to field-based rule
4. Create an own field-based rule and assign your own created translation object to this rule.

Creating a user-defined translation object – assign to target field
5. Assign your own created rule with your own created translation object to the relevant target field.

Tips & tricks
Migration object modeler (File/Staging)
Export / import projects
Before SAP S/4HANA 2020: You export / import projects using transaction LTMC.
As of SAP S/4HANA 2020 but only for projects created with the Fiori App: You export / import projects using
transaction LTMOM (migration object modeler).
SAP S/4HANA 2020 – migration object modeler
You first export a project from a system and save the
project as a zip file. You then import the zip file into the
other system. Mapping values, job settings, event
logs, staging tables and records in staging tables will
not be exported.

What’s new with 2020: Export / import projects in LTMOM
If the project you are importing does not exist in the system, a new
project will be created with the relevant project settings.
If the project you are importing already exists in the system, the existing
project settings will be overwritten with the exception of the following:
▪ Database connection
▪ Job settings
▪ Retention period settings
Check the report information on further details.
Non modifiable systems / production systems

It is not possible to create or modify projects in production system. You cannot, for example, remove a migration object. If
you need to make such an adjustment, you can adjust the project in the source system and transfer it again to the target.

What’s new with 2020: Use project in different client
For projects created with new Fiori App the following applies:
It is possible to use a project in a different client. The project is not copied, but only available in the new client.
If the staging tables are located in a remote system (Remote SAP S/4HANA Database):
▪ Clear field /1LT/PROCESSED or delete data from staging table
If the staging tables are located in the local ABAP schema (Local SAP S/4HANA Database):
▪ Staging tables are client-specific => you need to populate the staging tables with data again
Note that all mapping tasks are deleted. This means that you need to download the mapping tasks
before you proceed. You can then upload the mapping tasks in the new client.
This functionality is not available for projects created with LTMC.

What’s new with 2020: reset transfer status
It is possible to reset the transfer status for a migration object: The report DMC_MC_FM_RESTART_HANDLE resets the
transfer status of all selected records in the staging tables or uploaded MS Excel XML files.
Check the report information

on further details.
This functionality is not available for projects created with LTMC.

What’s new with 2020
1. Mapping Download/Upload: The mapping values can only be seen in the Fiori App and not in the translation objects
in LTMOM anymore. You can download/upload the value mappings in the Fiori App.
2. Finished projects: Theses projects cannot be accessed in change mode.
3. A project log entry is created if any of the following lifecycle events occur in LTMOM
▪ Create Migration Object from Template
▪ Create User defined Migration Object
▪ Copy Migration Object
▪ Reset Migration Object
▪ Update Migration Object
▪ Delete Migration Object

What’s new with 2020
Projects created in transaction LTMC:
▪ Are classified as “old” in the migration object modeler (LTMOM)
▪ Can still be changed and worked with in the migration object modeler in SAP S/4HANA 2020, but can only be used in
transaction LTMC

Corrections with 2020
Corrections
The checkbox Convert Parameter Value to Upper Case was removed from the Translation Object Value Range dialog.
This functionality was merged with the checkbox Case Sensitive, which is available as an attribute for every parameter of
a translation object.
With this it's now possible to control whether an inbound or outbound parameter is persisted in
upper case format or not.

Tip: Download metadata
You can download a metadata CSV file per migration object in LTMOM or in the Fiori App.
This button is available on the source

structure screen.
Metadata for a specific migration

object with all necessary information
on the source structure.

Tip: Where used list
Where used lists are available for rules, translation objects, fixed values and variables.
For a field-based rule you can choose the button Where-
Used List to view information about the rules or target
fields where the field-based rule is used.
When you try to generate a migration object that uses unreleased rules the system displays an
error message. You can use the where-used list to determine where the rule is used.
Tip: Project view and migration object view
You can easily switch between project view and migration object view.
Choose the button Display Selected Object in

Object Browser to switch from the project
view to the migration object view, if you have
selected a migration object.
Choose Switch to Higher Level to switch from

the migration object view to the project view.

Tip: Structure mapping and field mapping screen
You can change the position of structures on the structure mapping and field mapping screen
The position of the source structures and target

structures can be switched via menu entry
Settings -> Switch Position of Structures.
The user selection is persisted in
parameter DMC_SRC_CONT_RIGHT.

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

Simulation & debugging
Simulating and debugging a migration object
Simulate import of a migration object
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
Prerequisites for debugging
▪ You have populated the staging tables with values from

the source system.
▪ The migration object was generated successfully
▪ A simulation parameter is defined in activity Target
Structures API
▪ 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)
Simulate Import of a migration object
Additional information on the simulation functionality 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 case sensitive and you’ll not be able to select
anything in lower case)
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
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.
Debug errors and delete debugging run
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.
The system will save the relevant information about the first
erroneous record that was encountered in the staging table and
creates a simulation run (with the name you specify) that contains
this information.
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)
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.
For projects created with transaction LTMC
You can simulate the import of a file migration object for projects created with transaction LTMC
since 1809. Prerequisite is, that you have downloaded a template file and filled it with data. The process
is the same as shown in the slides before. Some functions may not be available depending on the
release (e.g. view records that will be simulated).
You can simulate the import of a staging migration object for projects created with transaction
LTMC since 1809 FPS01. The process is the same as shown in the slides before. Some functions may
not be available depending on the release (e.g. view records that will be simulated).
Downport for lower releases for projects created with transaction LTMC
SAP Note 2665339 contains program DMC_MC_SIMULATE_IMPORT_STAGING to perform an import

simulation for a staging migration object (project created with transaction LTMC) 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 (project created with transaction LTMC) for 1709 FPS01 or FPS02.
Further information
Data Migration Landing Page on SAP S/4HANA SAP Help Portal
SAP S/4HANA migration cockpit – further training material
*
* openSAP Course based on 1909
SAP S/4HANA migration cockpit - In-App Help now available
Open the In-App Help from any screen in the migration cockpit
Navigate directly to
the SAP Help Portal
documentation
View additional
information for
certain fields
SAP S/4HANA migration cockpit community
One-stop shop – free access

▪ Latest news
▪ Blogs
▪ Q&A section
https://community.sap.com/topics/
s4hana-migration-cockpit
FAQ
Preconfigured SAP S/4HANA sandbox system
Demo scripts for SAP S/4HANA migration cockpit available
SAP S/4HANA trial system (external link):

https://www.sap.com/cmp/oth/crm-s4hana/s4hana-on-premise-trial.html
Demo scripts for SAP S/4HANA migration cockpit

• File approach (bank)
• File approach (material)
• LTMOM - file approach (cost center texts)
• Staging approach (G/L accounts)
• Direct Transfer approach (cost centers and activity types)
• LTMOM – Direct Transfer approach (cost center texts)
• Direct Transfer approach (material)
• Direct Transfer approach (vendor, CVI)
https://blogs.sap.com/2019/04/23/sap-s4hana-fully-activated-
appliance-demo-guides/
System access for externals

External CAL: https://cal.sap.com/catalog#/solutions/52c66f34-9174-4692-b64d-4c34b955d9bc
SAP S/4HANA migration cockpit Tip:
Run Report DMC_NOTE_ANALYZER
SAP Notes and KBAs
Check SAP Note 2596411
Composite SAP Note for Collective SAP Note for Collective SAP Notes for
migration cockpit Direct Transfer File/Staging
CA-LT-MC CA-LT-MC CA-GTF-MIG
2538700
2780378 Collective SAP Note and FAQ for SAP
2747566
Composite SAP Note for S/4HANA migration cockpit
SAP S/4HANA migration cockpit File/Staging (Cloud)
Composite Note for
(all releases) Transfer Data Directly from SAP System
2537549
Collective SAP Note and FAQ for SAP
S/4HANA migration cockpit
File/Staging (on premise)
SAP S/4HANA SAP S/4HANA SAP S/4HANA Cloud SAP S/4HANA
Thank you.
sap_s4hana_migration_cockpit@sap.com
► Video: Migrate Data using Staging Tables

► Video: Migrate Data Directly from SAP System
► Video: Migration Object Modeler http://bit.ly/2BHmUHm
► Community Topic Page https://community.sap.com/topics/s4hana-migration-cockpit/
► Click through tutorials SAP S/4HANA migration cockpit
Find a comprehensive FAQ list in the SAP S/4HANA migration cockpit Community:
https://www.sap.com/documents/2020/03/2c4c6691-8a7d-0010-87a3-c30de2ffd8ff.html

SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For File - Staging

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

SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For File - Staging

Uploaded by

Copyright:

Available Formats

SAP S/4HANA 2020 - Migration Cockpit

Getting started with the migration object modeler

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

Revision Date Change

1.0 03.11.2020 Release for customer

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

SAP S/4HANA Migration Cockpit (Short recap)

Migration object modeler

Copying and extending delivered content

Creating own migration objects

Rules & translation objects

Tips & tricks

Simulation & debugging

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

Migration object modeler for custom requirements

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

This presentation deals with this migration approach

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

Fiori App Process & content Data load

SAP S/4HANA Cloud

Excel XML template files

SAP S/4HANA OP 2020: +115

*Current state of planning

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

SAP S/4HANA Migration Cockpit 2020 / CE2008

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

Migration Object Modeler:

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

Flexible and extendable

Easily integrate custom objects and enhancements into the migration

▪ Customer-specific enhancements to SAP standard objects delivered with the

Migration Object Modeler (Direct Transfer)

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

To start the migration object modeler you use transaction /nLTMOM.

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

In this presentation the following SAP Logon setting was used:

Note: Depending on the theme you have chosen, the screens in

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

You can select either the migration object screen or the

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

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

Migration Object Detail Screen

▪ It is possible to define the active view for a

▪ It is possible to maintain max no. of data transfer

▪ Application component for customer specific

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

Migration Project / Migration Object Detail Screen

▪ Projects created in Fiori App can only be seen and

▪ The client information can be seen either in the

This does not apply for projects created with LTMC.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

The button to download the XML file is available in the header

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

You can change the view of a

 You can choose the following options:

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

Forward navigation to SE37/SE38 on target structure screen is possible as of 1909

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 27

Generate Runtime Object Display Generated Function Group