SAP LTMOM Migration Object Modeler

SAP S4 Hana Finance
SAP LTMOM Migration Object Modeler

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/
SAP LTMOM Migration Object Modeler

Adjust source structure for material migration object (transaction LTMOM)
FI - Accounts payable open item
SAP enables data migration to SAP S/4HANA for customers coming from any legacy system. SAP
S/4HANA customers can take advantage of reliable migration approaches built into SAP
S/4HANA using the SAP S/4HANA Migration Cockpit together with a set of predefined data
migration objects.
Data recovery is an essential part of any enterprise resource planning system. And SAP is no
exception to the rule. In fact, SAP offers several tools for performing data
migrations: LSMW, LTMC, SHDB, IBIP or the application Fiori Migrate Your Data. In addition, as
SAP releases new versions, new data collection features are emerging. These tend to be more
and more simple for the user. Sometimes, some configuration is still required, especially if the
SAP application has customer specificities not covered in the standard. To make these
adjustments, there is a tool: SAP LTMOM Migration Object Modeler, which can meet this need.
Migrate Your Data - Migration Cockpit
With this app, you can migrate business data to SAP S/4HANA. You can migrate data directly
from certain SAP source systems, or you can use staging tables to migrate data.
Key Features
You can use this app to:
▪ Create migration projects to migrate data, and to monitor the status of the migration.
▪ Select the migration objects that are relevant for your migration scenario (the app uses
migration objects to identify and transfer the relevant data).
▪ Process any mapping tasks for the migration objects.
▪ Simulate the migration before migrating your data to SAP S/4HANA, and monitor the
status of the simulation process.
▪ Migrate your data to SAP S/4HANA, and monitor the status of the migration.
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/
Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)
1|P a g e
Creating Migration Projects
Context
You use migration projects to facilitate the transfer of data from a source system to SAP
S/4HANA. You use a migration project to specify the data that you want to transfer, and to
monitor the status of the migration.
Typically, you first create a project in a test system which is a copy of the SAP S/4HANA
production system. The more the data in the test system resembles the data in the production
system, the more precise your test will be.
For each test transfer, you create a new migration project in the test system that includes any
corrections or refinements identified in the previous test. When you are finally ready to transfer
your data to the SAP S/4HANA production system, you create a project in the production
system.
To create a migration project, proceed as follows:
1. In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing
the Migrate Your Data app in the Fiori Launchpad.
2. Choose Create and then Migrate Data Using Staging Tables. The system displays
the New Migration Project screen. Creating a project involves three steps. In the first
step you specify general data for the project. In the second step you specify a
development package for your project. Finally, in the third step, you select the relevant
migration objects.
2|P a g e
3. Under General Data, you specify the following information:
▪ Name
The name of the project.
3|P a g e
▪ Database Connection
If you are using files to fill the staging tables with data, choose the option Local
SAP S/4HANA Database in the Database Connection field. The system will
generate the staging tables in the internal schema of the SAP S/4HANA system.
Note that you could also fill these staging tables with data by using your
preferred tools if required. If you want to fill the staging table with data by using
your preferred tools into a different schema in a remote HANA database, select
the option Remote SAP HANA Database and enter a valid database connection
to the staging system by choosing one from the search help list. The system will
generate the staging tables there. You need to create a database connection in
transaction DBCO, and manually add it to table DMC_C_WL_DBCO_OP in the
SAP S/4HANA system. Note that you can also use files to fill the staging tables
with data if you choose this option
4|P a g e
4. Choose the button Step 2.
5. Under Development Package, you specify a development package for your project. If
you are unsure about which option to use, we recommend contacting your system
administrator.
Note
5|P a g e
Note that if you use a local development package ($TMP), it is not possible to transport
the project to another system in your system landscape using the Change and Transport
System (CTS).
6. Choose the button Step 3.
7. Under Migration Objects, the system displays a list of available migration objects. Select
the migration objects that are relevant for your project.
6|P a g e
You can view the following information for the listed migration objects:
▪ Name
The migration object name.
▪ Predecessor
You can check whether the migration object has any predecessor objects
(objects which must be processed before the migration object).
▪ Documentation
To view detailed documentation for the migration object, select

the Documentation link.
7|P a g e
8|P a g e
9|P a g e
8. Review your settings, and choose Create Project to create your project.
10 | P a g e
11 | P a g e
How to use the SAP LTMOM Migration Object Modeler functionality? This is what we will
answer in this guide.
12 | P a g e
SAP LTMOM : Migration Object Modeler
SAP LTMOM: Migration Object Modeler is the tool for SAP consultants. It is the tool that will
allow to adapt the migrations according to the specificities and the needs of the customer.
To launch this feature, you just need to execute the LTMOM transaction code itself. Once
executed, this is the home page of the functionality:
When should I use it?
The LTMOM functionality is not mandatory. Indeed, if the SAP application does not have any
customization fields (also called ZFIELDS), or if the standard template fits perfectly, then
LTMOM will not be necessary.
As mentioned above, the data upload templates offered by SAP via the new functionalities (e.g.
the Fiori Migrate Your Data application) are composed of standard fields. It is therefore
impossible to maintain specific, non-standard fields in these templates. In this case, the LTMC
and Migrate Your Data functions are ineffective. The LTMOM Migration Object Modeler
functionality comes into play at this point to configure the migration project according to the
specificities.
13 | P a g e
I need to adjust/add some standard fields in the source structure for FI - Accounts
payable/receivable open item
AWTYP
AWSYS
AWKEY
14 | P a g e
What are the different steps?
Select the migration project
First, the first step is to select the migration project where configuration is required:
15 | P a g e
16 | P a g e
Project selection
A project contains one or more sub-projects, in our example below a single sub-project
named ZSIN_MIG_M1U . This sub-project can contain one or more migration objects. In our
example, it contains 7 different objects:
Below, the view at the Object Type level Z_OPEN_ITEM_AP_M1U:
17 | P a g e
Configuring the Source Structure
Within each Object Type, we always find the same composition:
• Global Data
• Source Structures
• Target Structures
• Structure Mapping
• Field Mapping
During this second step, we will set up the Source Structure.
The Source Structure is simply the Excel template that the user must complete for the injection.
In addition, each of the columns in the Excel template corresponds to a field defined in the
"Source Structure".
18 | P a g e
19 | P a g e
20 | P a g e
Thus, it is possible here to delete and/or add fields according to your needs. To add a field,
simply activate the "Change" mode and add 3 entries.
AWTYP
AWSYS
21 | P a g e
AWKEY
22 | P a g e
23 | P a g e
24 | P a g e
Save
25 | P a g e
26 | P a g e
Target structures
Structure Mapping
27 | P a g e
Performing Field Mapping
The next step consists in performing the Field Mapping. In other words, this means establishing
the relationship between the source field and the target field. To do this, simply select the field
to be linked in the left-hand "source structure" area and drag & drop it directly onto the field
in the right-hand "target structure" area:
28 | P a g e
29 | P a g e
30 | P a g e
31 | P a g e
32 | P a g e
33 | P a g e
Thus, when downloading the new template, it will be composed of 3 columns.
34 | P a g e
Generate the Runtime Object
Once the field is added to the list, it is time to save and generate the Runtime Object. To do
this, click on the "Generate Runtime Object" button (or use the keyboard shortcut ALT + F1) at
the top left of the screen.
35 | P a g e
Once generated, the migration object is set to "Generated.
Generate Runtime Object

Thus, at this precise moment, by downloading the Excel template proposed by SAP, 3 columns
will be present at the very end of the table. Because the Excel template is equivalent to the
36 | P a g e
Source Structure, a modification made on the Source Structure directly induces the same
modification in the Excel template.
37 | P a g e
38 | P a g e
To conclude, we have seen that the LTMOM functionality was indispensable when the basic
Template provided by SAP required a particular adaptation.
Finally, when the latter is modified, data can be loaded directly into SAP.
39 | P a g e
40 | P a g e
41 | P a g e
•
Data Migration
• Migrate Your Data - Migration Cockpit
o Migrate Data Using Staging Tables
▪ Roles and Authorizations
▪ The Migration Process
42 | P a g e
▪ Creating Migration Projects

▪ Transferring Projects from One System to Another
▪ Using a Project in a Different Client
▪ The Migration Project Screen
▪ Project Settings
▪ Job Management
▪ The Migration Object Screen
▪ Downloading Template Files
▪ Transferring Data to Staging Tables
▪ Viewing Migration Object Instances
▪ Preparing the Staging Tables
▪ Mapping Tasks
▪ Simulating the Migration
▪ Migrating Data to SAP S/4HANA
▪ Monitoring the Status of the Migration
▪ Creating Correction Files
o Migrate Data Directly from SAP System
o SAP S/4HANA Migration Object Modeler
o Read Access Logging Configurations in Migration Cockpit
• Migration Cockpit (Transaction LTMC) - Deprecated
• Migration Objects for SAP S/4HANA
• Video Library for Data Migration
The Migration Project Screen

When you open a migration project, the system displays the Migration
Project screen. On the Migration Project screen, you trigger the steps that are
required to transfer the data for each migration object to the target SAP S/4HANA
system.
For each migration object, these steps are:
1. Uploading a template file for a migration object (if using template files to fill the
staging tables with data).
2. Preparing the staging tables.
3. Processing any open mapping tasks.
4. Simulating the migration to the target SAP S/4HANA system (optional).

43 | P a g e
5. Migrating the data for the migration object to the target SAP S/4HANA system.
These steps are relevant for each migration object that is part of your project. If a
migration object has a predecessor object, the predecessor object must be processed
first. In the Migration Object column, you can view whether a migration object has a
predecessor object.
The Migration Project screen contains the following columns:
▪ Migration Object
In this column, you can view the name of the migration object. You can also
view any predecessor objects. To view detailed information about a migration
object, click a migration object name in this column. The system displays
the Migration Object screen.
▪ Data
In this column, you can view the number of staging tables associated with each
migration object. You can also view the number of migration object instances
that exist in the staging tables.
▪ Mapping Tasks
In this column, you can view the number of open and completed mapping
tasks for each migration object.
▪ Simulation
In this column, you can view the number of migration object instances that
have been simulated successfully, and the number of instances for which
errors exist.
▪ Migration
In this column, you can view the number of migration object instances that still
have to be migrated to the to the target SAP S/4HANA system, as well as the
number of migration object instances that have been migrated successfully,
and the number of instances for which errors exist.
▪Migration Progress
44 | P a g e
In this column, you can view the status of the migration. If the migration has
not started for a migration object, the text Migration Not Started is displayed.
If the migration has started for a migration object, you can view the following
percentage values:
▪ Percentage of instances migrated successfully
▪ Percentage of instances with errors
▪ Percentage of instances not yet started
▪ Action
In this column, you can trigger an action for a migration object. For example,
you can upload a file or start the simulation process.
Additional Information
Monitoring
To view a log of all activities, choose the Monitoring button. The system displays
the Monitoring screen. You can view the active activities (for example Migration
Started) and completed activities (for example Migration Completed).
Settings
You can view the current settings for your project at any time by choosing
the Settings button. The system displays the Project Settings screen, where you can
also change settings for the project, for example you can add additional migration
objects. For more information, see Project Settings.
Mapping Tasks
You can view a list of all mapping tasks for all the migration objects in your project.
For more information about tasks, see Mapping Tasks.
Job Management
To adjust the maximum number of background jobs that are used for the migration
project, choose the Job Management button.
45 | P a g e
Finishing a Project
When you have finished your migration project, you can set the status of the project
to Finished. When you set the status of a project to Finished, no further changes are
possible. However, you can still view the project. To set the status of a project
to Finished, choose the Finish button.
When you set the status of a project to Finished, you can specify a data retention
period. The retention period is the length of time (in days) that the project and all
associated data is kept in the system after you have set the status of the project to
Finished. To do this, set the option Data Retention Period to On. The data will be
deleted from the SAP S/4HANA system when the data retention time expires. If you
set the option Data Retention Period to Off, then the project and all associated data
will be kept in the system indefinitely. If required, you can change the retention time
for finished projects. To do this, open the relevant project and choose
the Settings button. You can find the settings for retention time on the Technical
Information tab.
46 | P a g e
47 | P a g e
48 | P a g e
49 | P a g e
50 | P a g e
51 | P a g e
52 | P a g e
53 | P a g e
54 | P a g e
55 | P a g e
56 | P a g e
57 | P a g e
58 | P a g e
59 | P a g e
60 | P a g e
61 | P a g e
62 | P a g e
63 | P a g e
64 | P a g e
65 | P a g e
66 | P a g e
67 | P a g e
68 | P a g e
69 | P a g e

SAP LTMOM Migration Object Modeler

Uploaded by

Document Information

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 LTMOM Migration Object Modeler

Uploaded by

Copyright:

Available Formats

SAP S4 Hana Finance

SAP LTMOM Migration Object Modeler

SAP LTMOM Migration Object Modeler

Migrate Your Data - Migration Cockpit

You can use this app to:

▪ Process any mapping tasks for the migration objects.

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Creating Migration Projects

To create a migration project, proceed as follows:

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

3. Under General Data, you specify the following information:

The name of the project.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

4. Choose the button Step 2.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

6. Choose the button Step 3.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

The migration object name.

To view detailed documentation for the migration object, select

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

SAP LTMOM : Migration Object Modeler

When should I use it?

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

What are the different steps?

Select the migration project

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Below, the view at the Object Type level Z_OPEN_ITEM_AP_M1U:

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Configuring the Source Structure

Within each Object Type, we always find the same composition:

During this second step, we will set up the Source Structure.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Directeur SAP SCM & Cloud Solutions (Concur, EnableNow)