OpenSAP s4h35 Week 1 All Slides

Week 1: Staging Tables Approach and Migration Object Modeler
Unit 1: Introduction to Data Migration

Introduction to data migration
Weekly learning objectives
By the end of this week, learners will be able to

▪ Explain data migration requirements and tools to support you in your project
▪ Comprehend the migration process in the SAP S/4HANA migration cockpit,
including executing a staging table project
▪ Understand special topics that are valid for SAP S/4HANA and
SAP S/4HANA Cloud, private edition
▪ Work with the migration object modeler in a staging table project
Check out the openSAP course “Migrating Data to SAP S/4HANA Cloud, Public Edition”.
This course focuses on SAP S/4HANA Cloud, public edition and deep dives into migrating data using
staging tables.
Week 2: Direct Transfer Approach

Week 3: Migration Object Modeler for Direct Transfer
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
Agenda
Data migration requirements in a “new

implementation” transition scenario
Supporting tools: SAP Activate methodology,

SAP Signavio Process Navigator, Data Migration
landing page
Overview of SAP S/4HANA migration cockpit

Transition paths recap
Approach Business Driver Transition Option Target
SAP S/4HANA Cloud,

System private edition
Start rapid conversion SAP S/4HANA
REUSE
with in-place conversion modernization
versus
REENGINEERING SAP S/4HANA Cloud,
with data migration Selective data private edition
Customer tailored Selective business transition SAP S/4HANA
process optimization
SAP S/4HANA Cloud,

public edition
New
SAP S/4HANA Cloud,
Business model implementation private edition
Highly standardized, with
best practices and based on innovation
a clean core SAP S/4HANA

Focus: new implementation
Approach Business Driver Transition Option Target
SAP S/4HANA Cloud,

System private edition
Start rapid conversion SAP S/4HANA
REUSE
with in-place conversion modernization
versus
REENGINEERING SAP S/4HANA Cloud,
with data migration Selective data private edition
Customer tailored Selective business transition SAP S/4HANA
process optimization
SAP S/4HANA Cloud,

Highly standardized, public edition
New
with best practices and SAP S/4HANA Cloud,
Business model implementation private edition
based on a clean core
innovation
SAP S/4HANA
Mapping Your Journey to SAP S/4HANA – A Practical Guide for Senior IT Leadership
Data migration requirements
What are the sources / sender systems of the data?

Number and type of source systems? Central master data management?
Which data is needed from your source to operate SAP S/4HANA the way you want?
Master data? Open items? Balances?
Migrate data “as is” or transform on the fly?

Data transformations needed? Data quality improvement necessary?
Who needs to be involved?

Decisions to be taken? Major stakeholder?
Bottom Line: Start as early as possible to ensure high quality data

Sources to support you in your migration process
SAP Activate Methodology SAP Best Practices Data Migration Landing Page
(Roadmap Viewer) via SAP Signavio Process on SAP Help
Navigator
▪ Access implementation guidance for ▪ Access documentation – Application
your digital transformation ▪ Access and download SAP Best Help
▪ View and download SAP Activate Practices content ▪ View additional slide decks and training
methodology assets and accelerators ▪ Power your project with ready-to-run information
▪ https://go.support.sap.com/roadmap business processes ▪ http://help.sap.com/S4_OP_DM
viewer/# ▪ https://me.sap.com/processnavigator

Facilitate migration projects with SAP S/4HANA migration cockpit
Out-of-the-box, included in
Guidance and simulation
SAP S/4HANA and SAP S/4HANA
for the migration process
Cloud license and shipment
Preconfigured SAP S/4HANA- Automated mapping

specific migration content SAP S/4HANA between source and target
Migration Cockpit
Integrated into SAP Lower migration time and costs

Activate methodology No developer skills required
Migration object modeler for

custom requirements
Data migration process with SAP S/4HANA migration cockpit
SAP S/4HANA Cloud,

public edition
SAP S/4HANA Cloud,

private edition
Select Get data Map and transform data Simulate Migrate
migration objects
Model and design to reflect custom SAP S/4HANA
requirements
SAP Business Legacy

Suite
Migration programs are automatically generated – no programming required

Migration approaches
Two different migration approaches, depending on the source system:
Migrate Data Using Staging Tables Migrate Data Directly from SAP System
(Direct Transfer)
▪ Staging tables are created automatically in the ▪ Connect source system (ABAP-based SAP source systems)
SAP HANA DB (either locally or in a remote system) via RFC connection
▪ Populate these staging tables with business data ▪ Selection
using: – Based on predefined selection criteria (for example,
– XML template files company code for ERP source system) and selected
– CSV template files migration objects
– SAP or third-party ETL tools – Can be adapted with the SAP S/4HANA migration object
modeler
▪ Supports data migration scenarios from
SAP ERP, SAP AFS, SAP APO SPP, SAP CRM, SAP EWM

Migration objects
Preconfigured SAP S/4HANA-specific migration content
What is a migration object?

▪ Represents a business entity in SAP S/4HANA, such as a customer, sales order, or invoice
▪ Encapsulates the logic to create the specific business entities through the corresponding APIs offered
by SAP S/4HANA
▪ Delivered by SAP based on SAP Best Practices configuration and ready for immediate use
▪ Categorized in master data and transactional data (no historical data)
▪ Contains rules for how values from source to target are handled – called “mapping”
What is migration content?

▪ Migration content is the sum of all migration objects
What about updates on migration objects delivered by SAP?

▪ Updates are shipped by SAP (e.g. a standard field was added) with a new release or via TCI notes
What it is designed for (in/out of scope)
Designed for:
▪ Initial load of data (master data, open transactional data, no historical data)
▪ Used in the context of a new implementation of SAP S/4HANA, SAP S/4HANA Cloud,
private edition, and SAP S/4HANA Cloud, public edition
▪ Transport projects from DEV-Q-PROD via CTS
▪ Direct Transfer: Source system can also be a non-Unicode system
Not designed for:

▪ Keeping data in sync across systems*
▪ Realizing a continuous exchange or flow of data*
▪ Establishing an integration scenario*
▪ Cleansing data
▪ Migrating data directly from SAP S/4HANA or SAP S/4HANA Cloud to SAP S/4HANA is
currently not supported.
* For this purpose, SAP products like SAP Master Data Governance, Central Finance, product data replication, SAP
Landscape Transformation Replication Server, or SAP Data Intelligence are available (list does not claim to be complete)
SAP S/4HANA migration cockpit does not migrate historical data
Do you remember the last time you moved house? ▪ SAP S/4HANA migration cockpit is designed for a new
implementation.
▪ No migration objects for historical data in migration
cockpit*:
▪ Only the data necessary for a smooth business start is
migrated.
▪ A comprehensive customer-specific evaluation makes sense.
Solutions like Business Warehouse or side-by-side
extensibility can be considered.
Examples:
▪ The migration of closed documents leads to postings which are already included in the balances; there are no longer
open items for those documents.
▪ For partially open items, only the remaining quantities or values should be migrated.
* Exception: FI – Historical balance migration object see SAP Note 2943035

Migration strategy – General considerations
It is important to determine how data is transferred from the legacy system to the new system as
early as possible.
There are many influencing factors that could drive the appropriate approach for a specific system.
Some factors to consider include, but are not limited to:
▪ Amount of business data to be transferred and converted

▪ Permitted business downtime
▪ Data changes in scope during migration
▪ Type of data in scope for migration
▪ Business data quality of the source system
▪ Check Customizing
Relevant Customizing in the target must be available (for example, organizational units, define document
type for migration, define accounts for migration, remove account blocks)

Key takeaways
In this unit you have learned

▪ Why data migration in a new implementation scenario is important
▪ About SAP S/4HANA migration cockpit as the tool of choice
It is one key task during the transition to SAP S/4HANA.

DATA MIGRATION IS NECESSARY
Unfortunately, it is often underestimated. It can’t be
done by just pressing a button.
Make sure to understand your data migration

requirements early and plan for them accordingly.

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 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/trademark for additional trademark information and notices.
Unit 2: Getting Started with SAP S/4HANA
Migration Cockpit – Staging Tables
Getting started with SAP S/4HANA migration cockpit – Staging tables
Agenda
Setup
System Demo

General setup
SAP Fiori app Process and content Data load

Migrate Your Data
API-based
Staging Direct Transfer

SAP S/4HANA Cloud,
private edition
Staging Tables
▪ SAP ERP 6.0

SAP
▪ SAP APO
▪ SAP AFS S/4HANA
+210 Migration objects +250 Migration objects
▪ Excel XML ▪ SAP CRM
▪ SAP EWM Staging Direct Transfer
▪ CSV template files
▪ ETL tools of choice

Focus: migrate data using staging tables
SAP Fiori app Process and content Data load

Migrate Your Data
API-based
Staging Direct Transfer

SAP S/4HANA Cloud,
private edition
Staging Tables
▪ SAP ERP 6.0

SAP
▪ SAP APO
▪ SAP AFS S/4HANA
+210 Migration objects +250 Migration objects
▪ Excel XML ▪ SAP CRM
▪ SAP EWM Staging Direct Transfer
▪ CSV template files
▪ ETL tools of choice

Demo

Functions to keep in mind
▪ Maintain required roles and authorization:

− SAP_CA_DMC_MC_USER (SAP S/4HANA system)
− SAP_BR_CONFIG_EXPERT_DATA_MIG (front-end server)
− Corresponding role for each migration object
▪ Follow guided procedure
▪ Fill staging tables with XML or CSV files
▪ Run the Prepare step whenever data is added to the staging tables
▪ Download mapping tasks/templates to hand over to business users
▪ Check monitoring to see running jobs, access to messages, and
download files
▪ Use cancel button in the monitor to cancel simulation or migration
if necessary
▪ Use mass processing in case you want to trigger actions for
specific instances

Available videos
Video
Migrate Data Using Staging Tables
Video
Using CSV Files to Fill Staging Tables
Link to Click-Through-Tutorial
SAP S/4HANA migration cockpit
Learning Hub Subscription necessary (SAP Learning Hub Solution Editions)

Key takeaways

▪ How to migrate data using staging tables

Demo details
1. Open SAP Fiori app Migrate Your Data – user with necessary roles
2. Create migration project
– Choose the Create button → “Direct Transfer” will be handled in unit 9
– Select Local SAP S/4HANA Database Schema connection
– Choose migration object bank, cost center (add depended object Profit Center), G/L account → check
exercises in Fully Activated Appliance
– Finish creating the migration project
3. Populate migration objects with data
– Download the template for migration object Bank
– Fill template with data manually
– Upload template and follow guided procedure
– Migrate data
4. Verify data in relevant app
NOTE: When you set the migration project to “Finished”, you can specify a retention period for the data.
Create project – General data
Name your project
Local SAP S/4HANA Database

System will generate staging tables in the internal
schema of the SAP S/4HANA system

Create project – Migration objects
You can use the search field
Add your migration object

via button or drag & drop
To proceed, review your entries

Create project
Use Edit to add other

migration objects
Create your project

Monitoring – Settings
You can view the current settings

To view a log of all for your project at any time by
activities, choose choosing the Settings button.
the Monitoring button.
Here you can change settings for
the project, for example, you can
add additional migration objects.

Trigger actions via dropdown list
Find the selected migration objects.
In case you need to add additional

ones later on, use the Settings button.
The system proposes the next action to be

performed. For example, “Upload File” after
creating the project.
Here, you start the action for one object only.

Download templates for multiple migration objects
You can download the templates for

several migration objects by
selecting them and then clicking
Download Template.
A messages toast appears

– check Monitoring for file download.

Mapping tasks
Certain migration objects use control parameter mapping tasks to

control specific data migration procedures – see example Product.
These mapping tasks appear before filling the staging tables with data.
Check them first before proceeding.

Mapping tasks (specify mapping values)
You can specify value

mappings and transform
values from the source
system to the target system.
Search help for target values

provides existing values in the
SAP S/4HANA target system.
Details about mapping tasks in KBAs 3003068, 3076466 and 3075948

Migration project screen – More buttons
Buttons for quick access

▪ Monitoring – to view a log of all activities
▪ Mapping tasks – all mapping tasks for your project
▪ Job management – adjust number of background jobs
▪ Settings – general settings, e.g. add new migration objects
▪ Finish project
See more details in application help.

Instance-based simulation, migration, deletion via mass processing
Mass Processing helps you do

trigger actions on selected instances.

Instance-based simulation, migration, deletion via mass processing
1 2
Select from possible actions:

▪ Simulate
Use filter options to select
▪ Migrate relevant instances.
▪ Delete Instances
3 4
Instance list based on

your selection criteria. Get a summary and
proceed with Start.

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

warranty.
Unit 3: Focus Topics
Focus topics
Agenda
Ways to fill the staging tables (XML, CSV and ETL tools)
System setup – local/remote DB
Correction files
Note analyzer (transaction CNV_NA_MC)
Transport concept

Focus topics
Ways to populate data
You can fill the staging tables by using:
or or
XML files* CSV files* your preferred ETL tools
There is a sample code for a file splitter tool that can help splitting big xml files. Details available
in GitHub. (Note that this is a sample code only!)
* The size limit for each file is 100MB. You can upload multiple files at once by using a zip file. Note that the combined size of all the files you
want to add to the zip file must not exceed 160MB. The maximum permitted size of the zip file is 100MB.
See KBA 2719524 for further information.
Focus topics
Filling the staging tables – CSV template file
Introduction
▪ More flexible way to populate the staging tables using CSV files
▪ Widely known and compatible format for sharing, uploading, and migrating data
▪ Faster file creation and modification due to the simple structure and nature of the CSV format
▪ Upload the CSV file that contains only the data that should be migrated (no need to put comma to fill the
empty fields)
▪ Use the naming logic during the CSV upload and the ZIP file will be mapped to the data structures
automatically, e.g. S_MARA#FreeText.csv
▪ Possible to upload several csv files with a ZIP folder
Help Portal: Downloading CSV template files

Focus topics
Filling the staging tables – XML or CSV?
XML CSV
▪ Using XML is a stable option for entering and ▪ You need to use a separate CSV file for each
editing values manually. data structure.
▪ All data is contained in one file. ▪ There is no built-in protection for data formats.
▪ More flexibility: you can upload a CSV file that
only contains the data that should be migrated
▪ It contains detailed information about the (no need to fill the empty fields) and also change
relevant data structures as well as instructions the order of the fields if required.
about how to enter data in the file.
Using CSV template files is an expert option. We

do not recommend using CSV files unless you
have a specific use case for doing so, for example
if you are automating the extraction of data from
database tables.
Help Portal: Downloading template files

Focus topics
Filling the staging tables – Where to find information?
Application Help
Transferring Data from XML Template Files to Staging Tables

Transferring Data from CSV Template Files to Staging Tables
Demo videos
XML upload
CSV upload
KBAs
Additional Information about Transferring Data from CSV Template Files to Staging Tables
Migration Cockpit: How to correctly fill data into XML template

Focus topics
Filling the staging tables – Other possibilities
Good to know
To fill the staging tables, you can either use an ETL tool or fill the data directly on the SAP HANA database.
There are several blog posts listed below that explain the different methods to load data into the staging
tables:
▪ Migrating data using staging tables and methods for populating the staging tables
▪ Using SAP Data Services to load data to the staging tables
▪ Using SAP HANA Smart Data Integration (SDI) to load data to the staging tables
▪ Using SAP HANA Studio to load data to the staging tables
▪ SAP S/4HANA migration cockpit – creating and using synonyms for renaming staging tables
We recommend that you look at the following materials and decide how you would like to populate the staging
tables:
▪ KBA 2733253 FAQ Migrate Data Using Staging Tables

Focus topics
System setup – Local SAP S/4HANA database schema
SAP S/4HANA
SAP S/4HANA 1 Select Local SAP S/4HANA

migration cockpit database schema*
for your migration project
Staging Staging ... Staging
table 1 table 2 table n
3 Fill staging tables with Staging table

Microsoft Excel XML or creation for selected
CSV templates files migration object Application
interface 5 Insert through
4 Read access API
6 Status update of
Legacy system record
Application data Application tables
Data
source(s)
* Staging tables reside within the SAP S/4HANA schema

Focus topics
Remote SAP HANA database connection
Remote SAP HANA Database Schema

▪ Select this option if you want to fill the staging table with data using your
preferred tools
▪ The system will generate staging tables in a remote SAP HANA DB
schema
Required Setup
SAP S/4HANA setup
▪ Create secondary database connection (transaction DBCO)
▪ Add the newly created connection to table DMC_C_WL_DBCO_OP
(transaction SM30). This ensures that the connection can be displayed in
the SAP S/4HANA migration cockpit.

Focus topics
System setup – Remote SAP HANA database schema
SAP S/4HANA or separate ODBC SAP S/4HANA

SAP HANA box*
Staging table creation

for selected
SAP HANA DB schema* migration object Select Remote SAP HANA
SAP S/4HANA 1
Database Schema**
Staging Staging ... Staging migration cockpit for your migration project
table 1 table 2 table 3 4 Read access
Status update
6
of record
Application
5 Insert via API
Extract data and fill staging tables Interface
3
through SAP or third-party tools, or
Microsoft Excel XML/CSV templates files
Legacy system Application tables
Application data
* Separate SAP HANA database schema is required, can also be on SAP S/4HANA target system
Data Source(s) ** Prerequisite: established secondary database connection

Focus topics
Comparison local – remote SAP HANA database connection
Connection Staging Tables located SAP HANA Enterprise SAP HANA Runtime
Edition License (REAB)
Local SAP S/4HANA DB Staging tables will be created in same Fill tables via* Fill tables via*
Schema SAP HANA DB schema as ▪ XML/CSV template files ▪ XML/CSV template files
SAP S/4HANA ▪ ABAP programming ▪ ABAP programming
Standard use case
Remote SAP HANA Staging tables will be created in a Tables can be accessed via DB layer Tables can be filled via**
Database Schema separate SAP HANA DB schema or filled via ▪ XML/CSV template files
▪ XML/CSV template files ▪ ABAP programming
Specific customer use ▪ ABAP programming ▪ Data Services
case ▪ Data Services ▪ SLT
▪ SLT ▪ 3rd party tools
▪ 3rd party tools
* This is the recommendation from SAP. However, if your system administrator provides access to the relevant tables, it is also
possible to use the tools listed for the remote schema for the local schema.
** Staging tables cannot be filled directly on database level, for example with SAP HANA Studio (SUR Software Usage Rights).
Focus topics
Legal statement on use of 3rd party tools to fill staging tables in REAB*
In addition to the standard options of using either a full-use-version of SAP HANA (i.e. SAP HANA, enterprise edition) or the
SAP tools provided as Runtime Software with SAP HANA, runtime edition, it is possible to utilize a 3 rd party ETL tool to
populate the staging tables for the SAP S/4HANA migration cockpit.
In this case, the staging tables will be created by the SAP S/4HANA migration cockpit in a dedicated schema, either in the
same database tenant where SAP S/4HANA is installed or a separate dedicated database tenant. Such a schema can then
be configured as a remote database connection enabling connectivity and filled by a 3 rd party ETL tool solely for the purpose
of consumption by the SAP S/4HANA migration cockpit.
For the avoidance of doubt, the tables may not be used for any kind of processing by SAP HANA outside of SAP S/4HANA
migration cockpit, including, but not limited to, calculation view modeling, custom SAP HANA Extended Application Services
(XS) applications, and other processing by SAP HANA engines. Furthermore, the use of such 3 rd party tools to populate
staging tables shall be limited to the timeframe during which a migration project is active in the SAP S/4HANA system
installed in the same SAP HANA database tenant.
* This information is officially published on help.sap.com – Data Migration Landing Page – Further Information (as of 2020 FPS02)
Focus topics
Correction files
After the migration, there is a possibility to generate a correction file that contains all the migration object
instances in the staging tables that have the status Error. You can find it on the Monitoring screen.
Help Portal: Creating Correction Files

Focus topics
Important SAP Notes – Note Analyzer
Before starting a project, use Note Analyzer to ensure all corrections are implemented –
SAP Note 3016862 (Transaction CNV_NA_MC)
Installation Guide SAP Note for SAP Notes for HotNews SAP
migration cockpit File/Staging S/4HANA 2022 FPS0
(Basis/Tool) (Content) and FPS1
SAP S/4HANA 2022, 2780378 2537549 3291483
Chapter 7
How to implement the latest corrections released for SAP S/4HANA migration cockpit
Check SAP HotNews: KBA 2342391: How to access and use the SAP HotNews application

Focus topics
System modifiability
Recap
As of SAP S/4HANA 2020, configuration is only possible in modifiable environments.
This includes project creation, adding a migration object to a project, and all configurations
in the migration object modeler.
No project creation, no adding a migration object to a project, and no configurations in the

migration object modeler.
It is not possible to modify projects in non-modifiable / production systems. If you need to

make adjustments (for example, add a migration object), you can adjust the project in the
development system.

Focus topics
Transport functionality
Introduction
▪ Functionality available as of SAP S/4HANA 2021.

▪ The transport functionality in the migration cockpit is designed to transport between systems.
▪ You assign a development package while creating a project (SAP Fiori app). This assignment cannot be
changed later!
▪ You have the possibility to add projects, migration objects, and rules to a transport request in the migration
object modeler (transaction LTMOM).
▪ Projects in non-modifiable systems (e.g., quality and production) cannot be further configured, they can only
be executed. Projects cannot be created there!
Details in SAP Note 3104790
Please note that instances in staging tables are not transported!

Focus topics
Transport functionality – Concept
Separation between design time and execution time activities
DEV Transport QAS Transport PRD

project project
Design time activities* Import change request and Import change request and
e.g. create project, select migration update DB connection update DB connection
objects (NO design time activities*) (NO design time activities*)
Execution time activities Execution time activities Execution time activities
Individual Adjust
transport manually in
of project DEV if
needed Same release, patch level respectively
SAP Notes level required!
SBX Import change request with project
and objects from DEV
and update DB connection
(NO design time activities*)
DEV: Development System
QAS: Quality System
Execution time activities * Design time activities are allowed in systems which are PRD: Production System
e.g. execute migration, edit mapping open for changes, usually DEV systems SBX: Sandbox System

Focus topics
Transport projects from one system to another
Add projects, migration objects and their elements to a transport request
Migrate Your Data app Migration object modeler (transaction LTMOM)

When creating a project you need to Choose the project and add it to a transport request
assign a development package: (all assigned migration objects, rules, fixed values, translation
objects, and variables will be added to the transport request):
Development package
cannot be changed at
a later point in time
For older releases, check SAP Note 3104790 and the SAP Community blog post:
SAP S/4HANA migration cockpit – File/Staging – How to get your project into another system
Focus topics
Key takeaways

▪ Different ways to fill the staging tables
▪ Where to find additional information on filling the
staging tables
▪ The system setup for the local and the remote
database schema
▪ The importance of the note analyzer
(transaction CNV_NA_MC)
▪ Transport concept for the migration cockpit

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

warranty.
Unit 4: Best Practices and Challenges
Best practices and challenges
Agenda
Migration object information
Impact of release upgrade
Key user extensibility
Mass changes
Performance measures
Overview of main functions

Migration objects – Details and documentation
Download
migration object list
Use filter options
Documentation available
Migration object list in SAP Help Portal (SAP S/4HANA) – http://help.sap.com/S4_OP_MO

Object updates for staging migration objects
From time to time, SAP updates migration objects to ensure that they accurately reflect the current state
of the SAP S/4HANA system.
▪ Updates are shipped with new release or by TCI note
▪ The system will prompt you to update the relevant migration object
▪ Updates can be ignored
SAP Note 2537549 – Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit – File/Staging
TCI notes will be listed in the collective note (release-based)

Impact of release upgrade
Note: Avoid upgrading to a newer release during a migration project if possible!
What is the impact of upgrading to a newer release during a migration project?

Though SAP tries to avoid incompatible changes between releases, it cannot be guaranteed
that migration objects delivered by SAP work after the upgrade.
Same applies to migration objects adapted or created by the customer.
Recommendation
▪ Migration objects can be updated, but check the release comparison carefully!
▪ Extensive tests are essential
SAP S/4HANA – Release Comparison of Migration Object Templates

Object dependencies
During project creation

Predecessors are also listed in
the migration object
documentation
http://help.sap.com/S4_OP_MO
in the section “Prerequisites”.
In our example, the migration
object Cost Center was used.
After adding the predecessors
Click on the migration object.

This will bring you to the
Migration Object details screen

Key user extensibility – Custom fields support
Key User Extensibility SAP S/4HANA migration cockpit

▪ Business experts or implementation consultants can ▪ Some migration objects support these custom fields –
use the Custom Fields app to create additional fields check migration object list (details next slide)
▪ Example: Add product-related bonus to product master ▪ If supported, custom fields will automatically be
data, see video reflected in the template of the corresponding
migration object

Custom fields support – Check for custom fields
▪ Use the Check for Custom Fields button to check whether custom fields exist. If custom fields exist, the
system updates the migration object with the custom fields
▪ Find detailed messages on the History tab
Check for Custom Fields
History
Show Messages

Custom fields support – Available migration objects
Support of custom fields for migration

objects before SAP S/4HANA 2022 –
check following section on help.sap.com
For list of available migration objects that support custom fields, see http://help.sap.com/S4_OP_MO
Mass changes
SAP S/4HANA migration cockpit does not support mass changes!

The APIs used in the migration cockpit are APIs to create data. The update of existing data is therefore not supported.
Mass change functionality may be available after an initial data migration for some migration objects
in the respective application.
Mass processing of master data for product, customer, and supplier is available. See Help Portal
for further information.
You find this information in the migration object documentation for Customer, Product, and Supplier
in the Post-Processing section.
In addition, you can check SAP Fiori Apps Reference Library to see if the mass change/maintenance
app is available for a specific application.

Performance – Non-technical measures
KBA 3065607 contains information about performance for the Staging Table approach
Non-technical measures
▪ Verify which data in the source system is required – outdated data, incorrect data, and archives should not be migrated
▪ Close open processes in the source system where possible, e.g. close open items
▪ Consider a phased approach – in case of huge amounts of master data, maybe some can already be migrated during
uptime
▪ Create a detailed cutover plan – which actions shall be started when?
▪ Using several migration projects in parallel does NOT improve performance
▪ Check active processes during downtime – skip or postpone all processes which are not necessary for the migration
▪ Perform at least one test in a production-like environment (no sandbox with bad performance!)
▪ Do not start the migration for all objects in a project in parallel. There is a sequence for migrating objects because of the
dependencies between objects.

Performance – Technical measures
Technical measures
The general performance of migration cockpit activities depends on several parameters:
▪ Number of data transfer jobs per migration object and migration project
– For more details about how to modify the data transfer jobs for SAP S/4HANA migration cockpit, see KBA 3066336 and
KBA 2878945
– Even if you assign a higher number of data transfer jobs to run in parallel, the effect in terms of performance depends
on the overall load of the system
– Consider that uploading multiple objects in parallel can flood the job queue
– After the prepare step the system will suggest the maximum number of jobs for a dedicated migration object
– There are some migration objects that cannot be parallelized. You can find the list of these objects in KBA 3294684
▪ System parameters, for example, the number of available batch and dialog processes, available memory, available CPU
or network bandwidth, and latency
▪ The performance of the API used in the respective migration object has also an influence on the performance
▪ Application-specific customizing also influences the performance of the target API

Overview of main functions
The Migrate Your Data app is available as of SAP S/4HANA 2020. Find below important new features for the approach
“Migrate data using staging tables”.
Feature 1909 2020 2021 2022

Transaction LTMC (deprecated with 2021) x x - -
not recommended display mode only
SAP Fiori app Migrate Your Data - x x x

Mass processing (instance-based) - x x x
(FPS01 – delete)
(FPS02 – simulation, migration)
Transport concept (via CTS) - - x x

View migration results - - x x
Download migration results - - x (FPS01) x
Mapping down/upload in SAP Fiori - x x x
Cancel button (on Monitor screen, e.g. cancel simulation) - - x x
Use CSV files to upload data - - - x
CSV: change order of fields; no need to fill the empty fields - - - x (FPS01)
Delete mapping values in SAP Fiori UI - - - x (FPS01)

Key takeaways

▪ Where to find detailed information on migration objects
▪ The impact of release upgrades
▪ How to improve the performance
▪ That custom fields will automatically be reflected in the
template of the corresponding migration object if the
custom fields app is used and the migration object
supports these custom fields

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

warranty.
Unit 5: Getting Started with the Migration Object
Modeler – Staging Tables
Getting started with the migration object modeler – Staging tables
Agenda
Introduction
Getting started with the migration object modeler

Introduction
Typical Questions:
▪ How can I adapt the migration objects to my needs?
▪ Is it possible to adjust the migration objects provided by SAP?
▪ I am missing a field in the staging table – how can I add this field?
▪ There are too many fields in my Excel template that I do not need
– how can I hide these fields?
▪ How can I create my own migration objects to transfer custom-
specific data?
Migration Object Modeler:

Modeling environment for the SAP S/4HANA migration cockpit

Modeling environment for the SAP S/4HANA migration cockpit
Migration Object Modeler
▪ Available for SAP S/4HANA, SAP S/4HANA Cloud, private edition and included in the license
▪ Transaction LTMOM
▪ Available for both approaches
Custom-specific enhancements to pre-delivered migration objects

▪ Easily adjust input structure
▪ Add new fields
▪ Hide a field in the template
▪ Map structures and fields
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 own function module
Easily integrate custom objects and enhancements into the migration project

Topics
Migration Object Modeler: Migrate Data Using Staging Table
Getting started with the migration object modeler (Unit 5)
Adjusting migration objects provided by SAP (Unit 6)
Creating your own migration object (Unit 7)
Tips and tricks (Unit 8)
Migration object modeler: migrate data directly from an SAP source Week 3
Transaction and role
To start the migration object modeler you use transaction LTMOM. Your user needs the following role:
SAP_CA_DMC_MC_DEVELOPER
Check also detailed

information on
LTMOM here.

Demo

Rules
Rules are used 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 created on subproject level can be used by all migration objects

in the project.
Rules created on migration object level can only be used for this
specific migration object.

Translation object – Mapping tasks in SAP Fiori UI
A translation object defines how values from a specific field in the source system must be translated to target values
during the data migration. If you create your own translation objects, you need to assign a translation object to a field-based
rule; it cannot be assigned directly to a target field. Translation objects reflect the mapping tasks in SAP Fiori.
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
For this case, there is already a translation object called MAP_LAND1 delivered and
assigned to a field-based rule (CVT_LAND1). This rule is assigned to the corresponding
target fields.
Translation object 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.
Click-through tutorial
migration object modeler –
getting started
Based on SAP S/4HANA 2022

Key takeaways

▪ How to work with the migration object modeler, transaction
LTMOM
▪ The different areas of the migration object modeler:
source structure, target structure, structure mapping, field
mapping, rules and translation objects
▪ Which role is needed: SAP_CA_DMC_MC_DEVELOPER
▪ Where to find additional information

Migration Object Details screen – Overview
On the Migration Object Details screen you can see for which approach the
migration object was created. Projects created with the old/deprecated
transaction LTMC are classified as “old” as of 2020.
▪ Migrate Data Directly from SAP System (Direct Transfer)
▪ Migrate Data Using Staging Tables
▪ Migrate Data Using Files (old)
▪ Migrate Data Using Staging Tables (old)

Migration Object Details screen – Project and client
Migration objects that were

added via the SAP Fiori app are
classified as template migration
objects
You find also information on the

project name and the client
where the project can be edited.
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 or you can view the tooltip of a field.
Information on staging table name
Choose ‘Insert Field’
View information on
a specific source field

Target structures – Function module
Double-click Target Structures to view detailed information about the function module that transfers the
business object instance to SAP S/4HANA. CDS behavior definitions are also supported.
Forward navigation to
SE37/SE38 on target
structure screen possible
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 view 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
In 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.
Filter for mapped/unmapped fields
mapped
not mapped

Documentation
Information button
Depending on the migration

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

Additional functionality
Documentation
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.

Tip: use Favorites button
You can add projects and migration objects to your favorites list to speed up search.

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

warranty.
Unit 6: Adjusting Migration Objects Provided by
SAP
Adjusting migration objects provided by SAP
Agenda
Migration object modeler:

migrate data using staging table
Add an additional field to the migration object “Bank”
Add a customer view to the migration object “Bank”

and hide fields
Copy / delete / reset a migration object
Restore custom enhancements

migrate data directly from an SAP source Week 3
Working with migration objects in transaction LTMOM
Different ways to work with a migration object in

a migration project in transaction LTMOM:
▪ Adjust a template migration object
− Add an additional field
− Create a custom view
▪ Copy a migration object
▪ Create a user-defined migration object Unit 7

Template migration object
Template Migration Object

A migration object that was selected when creating
a migration project in the SAP S/4HANA migration
cockpit SAP Fiori application.
▪ Link to the delivered SAP content is available.
▪ If SAP updates the delivered content, this
migration object will be updated.
▪ 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 custom fields.
▪ You can ignore updates for the migration object.
The system will permanently ignore content
updates for the migration object and it is treated
as a user-defined migration object.

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 adjust the delivered

migration object, please note that SAP only
supports content issues based on the original
template. For further information on support
for adjusted migration objects provided by
SAP, see SAP Note 2481235.

Demo example
1. Add an additional field [Post_Bank (Char, 16); Post office bank current account number] to the migration
object “Bank”
Fields of target structure for bank migration object (Bank address)
2. Add a custom view to the migration object “Bank” and hide fields [bank branch and bank group]
Demo

Template migration object – Content update
Content update
From time to time, SAP updates migration objects to ensure that they accurately reflect
the current state of the SAP S/4HANA system. 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. You can do this in the SAP Fiori app or in transaction LTMOM.
▪ Custom modifications will be deleted when objects are updated.
▪ Any rules created at migration object level will be deleted.
As of SAP S/4HANA 2021:

If you have adjusted the migration object (template migration object), certain modifications will not be deleted
when the objects are updated. The following elements are considered as enhancements:
✓ Adding a new field to an existing source structure
✓ Definition of a field mapping for a target field or an event if a mapping for the field or event was not provided
by SAP; the target field must be part of the target API.
Other modifications are not considered, and you should save any modifications that you want to
keep for future use before proceeding.
Template migration object – Ignore content updates
Ignore content updates

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 can reset a migration object.
If you wish to completely decouple your enhancements from the delivered content you should copy all include
programs to the customer namespace, adjust them if necessary, and then assign them to your migration
object.
If you choose Ignore Content Updates, the migration object is treated as a user-defined migration object.
Restore custom enhancements after content update
Restore custom enhancements after content update

You can adjust template migration objects. Some changes will still be in place after a content update.
As of SAP S/4HANA 2021 the following elements are considered as enhancements:
▪ Adding a new field to an existing source structure
▪ Defining a mapping for a target field or an event (if a mapping for the field or event was not provided by SAP)
− If a target field is delivered without a field-based rule and you assign a field-based rule, the rule assignment
is not deleted if you update the migration object. Same applies for an event and an event-based rule.
Any rules created at migration object level will be deleted during the content update. This means
that any mapping operations or rule assignments that use these rules cannot be used and will also be
deleted.
We recommend creating your own rules on subproject level. Updating a migration object does not
affect any mapping operations or rule assignments that use rules that are created at subproject level.

Restore custom enhancements after content update (example 1)
Example where custom enhancement is available after update

You have added a ZFIELD to the source structure and you have mapped this field to Targetfield5
with a MOVE rule.
Before Update:
Source Field Rule Target Field
Source structure: Keyfield1, Keyfield2, Field3, Field4, ZFIELD
Keyfield1 Move Targetfield1
Field mapping: ZFIELD MOVE Targetfield5
After Update (your extension is still available): Field3 Move Targetfield3
Source structure: Keyfield1, Keyfield2, Field3, Field4, ZFIELD Field4 Move Targetfield4
Field mapping: ZFIELD MOVE Targetfield5 ZFIELD Move Targetfield5
Custom enhancement is still available after update.

Restore custom enhancements after content update (example 2)
Unlikely Case: Example where enhancement gets lost as the standard content is taken into account
You have added a ZFIELD to the source structure and mapped this field to Targetfield5 with a MOVE rule.
Now the standard content has a new field Field5 with a field assignment to Targetfield5. What happens after
the update?
Source Field Rule Target Field
Before Update
Before Update: Keyfield1 Move Targetfield1
Source structure: Keyfield1, Keyfield2, Field3, Field4, ZFIELD
Field3 Move Targetfield3
Field mapping: ZFIELD MOVE Targetfield5
Field4 Move Targetfield4
ZFIELD Move Targetfield5
After Update:
Your field mapping is lost, as it is replaced by the standard content
Source structure: Keyfield1, Keyfield2, Field3, Field4, Field5, ZFIELD Source Field Rule Target Field
Field mapping: Field5 MOVE Targetfield5 Keyfield1 Move Targetfield1
After Update
ZFIELD is no longer used in the field mapping as the new Field3 Move Targetfield3
standard field Field5 is used. Data in ZFIELD is still available Field4 Move Targetfield4
after the update and if needed, the field mapping can be Field5 Move Targetfield5
adjusted again. ZFIELD

Copying migration objects
Copying a migration object into a different project

You can copy a migration object from another client or from another
project. The migration object type (template migration object, custom
migration object) will stay the same.
We recommend that you always use the latest available migration objects for your project. We do not
recommend copying migration objects from older releases, as you will not have the latest content
updates available in the copied migration object.
Copying a migration object within a project

A template migration object can only be available
once in a project for a dedicated migration object.
If you copy it more than once, it will be treated as a
user-defined migration object.
Deleting or resetting a migration object
Deleting a migration object

▪ You can delete a migration object from your project
▪ Only possible in transaction LTMOM, not in the SAP Fiori UI
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.
Resetting a migration object

▪ You can reset a migration object so that it reverts to its original
template version
▪ Any changes will be lost

Differences between migration object types
Template Migration Object User-Defined Migration Object

1. Adding a migration object to your project in the SAP 1. Start from scratch and use standard API or own
Fiori app function module
2. Creating a migration object from template in 2. Ignore content update
transaction LTMOM 3. Copying a migration object from template more than
once within a project
Content update possible Content update NOT possible
Adding new fields is possible, but no changes to existing Changes possible to all fields, structures, rules, and so on
fields
Standard View or Custom View possible Only Custom View possible
Only available once in a project for a dedicated migration Can be available more than once in a project
object (with a different name)
Naming convention: Z_ Naming convention: Z_Z

Link to click-through tutorial

Migration object modeler –
adding an additional field

Key takeaways
In this unit you have learned that

▪ A template migration object can only be available once
in a project
▪ As soon as you start to adjust the delivered migration
object, SAP only supports content issues based on the
original template
▪ From time to time, SAP updates migration objects to
ensure that they accurately reflect the current state of
the SAP S/4HANA system
▪ If you ignore content updates, the system will
permanently ignore content updates for the migration
object and it is treated as a user-defined migration
object

Template migration object – Example bank master
Fields cannot be changed. They

are not marked as Custom Field.

Template migration object – Adding a field (source structure)
You can add additional fields. Custom fields will start with ZZ.
If you add an additional field, you need to run the “Adjust Structure” functionality either in the SAP
Fiori app or in transaction LTMOM or generate the runtime object in LTMOM.
Template migration object – Adding a field (field mapping)
To map the added source field to the target field, simply drag
and drop. Alternatively, you can right-click the target field.
The resulting mapping operation is a simple 'MOVE' operation – that is, the values of the source field will be
moved to the target field. For more complex requirements, you can use rules.
Do not forget to generate your adjusted migration object to check for any error messages.
Template migration object – Change view (1/2)
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.
If you want to change the view of a migration object you can

create a custom view and adjust it to your needs.
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
You can choose the following options: source structure field
▪ Visible, Not Visible, Required
▪ At least one field must be visible if the
corresponding structure is visible S4CORE – SAP S/4HANA on-premise, SAP S/4HANA Cloud, private edition
SAPSCORE – SAP S/4HANA Cloud, public edition
If you want to change the delivered view, we recommend that you create a custom view and adjust it
to your needs.
Template migration object – Change view (2/2)
On migration object level you find the active view of a migration object
▪ The view determines the visible and mandatory fields for a migration object.
▪ For template migration objects the standard scope is assigned
▪ To use your custom view, change the active view to custom scope.
Don’t forget to synchronize the structures or generate the runtime object
if you change the active view!

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

warranty.
Unit 7: Creating Your Own Migration Object
Creating your own migration object
Agenda

Create migration object to add additional languages

for “Cost Center” description
Further source of information

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
restriction: a function module or (CDS) behavior
definition must populate the target structure with data.

User-defined migration object – Example
Example
If you use the migration object CO – Cost center, you can only create the description of the cost center in one
language. See SAP Note 2671476 for more information on migration of text/description in multiple languages.
If you need to add descriptions for additional languages, you can create your own migration object to handle
this. In our example we will create a migration object to add a description in additional languages to an already
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 customers.
As of SAP S/4HANA 2020, a (CDS) behavior definition as well as a function module can be
used to transfer data to SAP S/4HANA.

User-defined migration object – Demo steps
1. Create user-defined migration object (name must start with Z_Z)
2. Assign the target API and simulation settings
3. Create source structure
4. Maintain the structure mapping
5. Maintain the field mapping by adding a rule
6. Maintain the field mapping via drag and drop
7. Show fields with mapping to check if settings are missing
8. Generate the runtime object to check for errors

Demo

How-to-Guide: How to create an own migration object
Good to know
▪ A user guide on how to create an own migration

object is 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 Staging Tables”.
▪ How-To-Guide: Creating a New Migration Object with
the Migration Object Modeler
▪ 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 the documentation
linked in SAP Note 2590165 as a starting point.
Direct link to user guide documentation.
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. Instead, all error, warning,
and abort messages should be reported back to the calling program.
▪ 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.

Link to click-through tutorial

Migration object modeler –
Creating an own migration object
click

Key takeaways

▪ How to create an own migration object based on the
example of the cost center texts
▪ Where to find a detailed user guide on how to create
an own migration object
▪ Important prerequisites for creating an own migration
API

Creating a user-defined migration object – Wizard
1. Enter a name (must start with Z_Z), 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_ZKOSTL_TXT_M01
The fields Modified and Update

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

automatically assigned as Active View.
Technical name of user-defined migration objects will start with Z_Z as of SAP S/4HANA 2020.

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 using a text file,

choose Upload Source Structure List.
Maximal key length: The sum of all field lengths for the keys on the top level source structure,
including separators, must not exceed 200 characters.
Structure mapping
4. Maintain the structure mapping. You can check whether any errors exist for the
mapped structures.
Drag the source structure to the target

structure. Start with the HEADER. A To get an overview of all
source structure (or structures) must existing structure mappings for
be mapped to a target structure in the migration object, choose
order to map the fields of the source Structure Mapping Preview.
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.
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. 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: 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 dropdown menu.

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.
For more complex requirements, you

can use rules (e.g. S_CVT_KOKRS)
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.
Field mapping: filter
7. Show fields with mapping. Don’t forget to save your changes.
Filter on Show Fields With Mapping for an

overview of the rules you have assigned.
Rule assignment for our example Cost Center

Text
Source Field Target Structure Target Field Rule
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

Field mapping: filter
Import parameters for CVT_KOSTL_ALL
Variant 1 = KOKRS, 2 = BUKRS, 3 = WERKS.

Generate runtime object
8. Generate the runtime object to check for errors.

Rule proposal (1/2)
Good to know
An Expert function is available to have an automated rule proposal for the target fields in the field mapping
screen. This feature is intended to help you create your own migration objects.
If you change the rules in delivered migration objects based on the rule proposals, there will be
no content support.

Rule proposal (2/2)
▪ 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.
Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 8: Tips and Tricks
Tips and tricks
Agenda

Simulate/debug the import of data from staging tables
Use project in a different client
Reset transfer status
Overview on main functions

Tips and tricks
Simulate/debug the import of data from staging tables for a migration object
Simulate Import in LTMOM Option for Debugging Errors in Target

System
Simulation functionality
Debug Saved Record Delete Saved Record

Program: DMC_MC_MIGOBJ_EXEC_SINGLE_OLO Program: DMC_MC_MIGOBJ_EXEC_OLO_DELETE

Tips and tricks
Prerequisites for simulation and 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 the
target structure
▪ The migration object is not locked by any
other user
▪ If the migration object is of type Template
Migration Object, it must not be outdated
(Update Available  No)
KBA 3047880 – Analyzing API Calls Triggered by the SAP S/4HANA Migration Cockpit

Tips and tricks
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:
▪ Simulate All Instances
▪ Simulate Number of Instances (random)
▪ Simulate Specific Instances (note: for this option, it is
currently not possible to select instances that contain lower
case values)
You can choose two breakpoint options

▪ Breakpoint Before Mapping
▪ Breakpoint Before API Call
Note: this option will not be visible for production systems
If required, you can view the migration object instances before

they are simulated. You can also download these migration
object instances

Tips and tricks
Debug errors and delete debugging run
If required, you can debug errors in the SAP S/4HANA target system.
The system will save the relevant information about the

first erroneous instance 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 instance will be saved and the specified simulation run
will be deleted from the system after the simulation run has finished.
Tips and tricks
Add elements to a transport request
Transport functionality
Add projects, migration objects and their elements to a transport request.
If you add a project to a transport request, all assigned migration objects, rules,
fixed values, translation objects, and variables will be added to the transport
request.
If you add a migration object to a transport request, all rules, fixed values,
translation objects, and variables that are used by the migration object will be
added to the transport request.
You can also add single rules, fixed values, translation objects, or variables to a
transport request.
Only the definition of a rule, fixed value, translation object, or variable is added to a transport
request. No values, for example mapping values, are included.
If you transport a project into a system that contains the same mass transfer ID as the imported
project, this could result in inconsistencies.
Check SAP Note 3104790 for further information.

Tips and tricks
What if both development and test client are in the same system?
Use project in different client
If development and test system are

DEV + Test System on the same system:
PRD system 1. Set up project in DEV client
Function LTMOM 2. Use project in Test client
“Use Project in different client” 3. In case of adjustments, use
Development project again in DEV client
Test Client Production client
client Function LTMOM
“Use Project in different client” 4. Transport project to PRD
system
Transport project
DEV: Development System
PRD: Production System
Tips and tricks
Use project in different client – Basic facts
The transport function for the migration cockpit does not support transports
between clients in the same system.
To use a project within a system in another client, for example for testing purposes,
proceed as follows:
1. Log on to the client where you want to use the project
2. Go to the migration object modeler (transaction LTMOM)
3. Select your project in the object browser
4. Choose Goto → Use Project in Different Client
The project will not be copied to the other client; it is moved to the other client and therefore no longer
available in the old client.
Note that all mapping tasks are deleted. If you want to use the same mapping values, download
them in advance. You can use the download mapping functionality in the SAP Fiori app Migrate Your
Data – Migration Cockpit.
Tips and tricks
Use project in different client – Important considerations
If you want to transfer the same data again to the new client, note:
▪ If the staging tables are located in the local ABAP schema of the SAP S/4HANA system
− populate the staging tables with data again, as the staging tables are client-specific
▪ If the staging tables are located in a remote system,

− delete all data from the staging tables and populate them with data again
or
− manually reset the processing status of all migration object instances in the staging table by clearing field
/1LT/PROCESSED
Technically, the staging tables of the local ABAP schema have an additional client (MANDT) field compared
to the remote schema.
Tips and tricks
Overview of options to transfer projects from one system to another
Release Import/Export Transport Check on System Use Project in

Functionality Mechanism (DEV- Modifiability Different Client
QAS-PRD)
2022
2021 FPS1
2021 In LTMOM**
2020 In LTMOM**
*
1909 In LTMC
* Not for projects created with transaction LTMC (deprecated transaction)

** LTMOM (migration object modeler)
Tips and tricks
Reset transfer status
If you want to migrate an instance of a migration object again for test purposes, it is possible to reset the
transfer status.
If you have already transferred an instance
to the target system you get the following
message if you try to migrate it again.
1. Delete the instance in the staging table in the SAP Fiori app Migrate Data – Migration Cockpit (not possible
in production system)
2. Use transaction LTMOM and choose Goto → Reset Transfer Status for the dedicated migration object and
respective instance (only possible in change mode).
Check the report information for The report

further details. DMC_MC_FM_RESTART_HANDLE resets
the transfer status of the selected instances.

Tips and tricks
Copy projects
Functionality to copy projects changed in SAP S/4HANA

2022
➢ Copied objects are considered as template migration
objects if they refer to a delivered migration object and
can be updated with new content delivered by SAP
➢ Copied project with the same settings as the “original”
Use Cases project
▪ Using templates
You can create one migration project that will act as a template for other migration projects.
▪ Reusing successful projects
You want to reuse the settings of a successful project.
▪ Creating similar migration projects in a test environment
You want to create similar migration projects in a test environment.
▪ Transporting a project to a different system
You can copy a project so that it can be transported to another system. For example, a
project might use a local development package that cannot be transported to another system.
Tips and tricks
Overview of main functions in transaction LTMOM
Find below important new features in transaction LTMOM for the approach “Migrate data using staging tables”.
Feature 1909 2020 2021 2022

Reset transfer status – x** x x
Copy and delete objects – x x x
Use project in different client – x** x x
Client dependency – x** x x
Check on system modifiability/non-modifiability – x x x
Export/import projects x (LTMC) x x (FPS0, FPS1) –
Transport concept via CTS – – x x
Restore custom enhancements after content upgrade – – x x
Copy migration object from one project to another project – – – x
with link to original SAP delivered template* (no update of copied (no update of copied (no update of copied (update of copied
objects possible) objects possible) objects possible) objects possible)
* Copy function changed with 2020; below 2020 objects in the copied project can’t be updated with new standard content
** Not applicable for projects created with old transaction LTMC
Tips and tricks
Further information
Release SAP S/4HANA 2021 and higher
Release SAP S/4HANA 2020

Tips and tricks
Key takeaways

▪ How to simulate or debug the import of a migration
object with the help of the migration object modeler
▪ What you can do if your development and test client
are located in the same system
▪ How to migrate an instance of a migration object again
for test purposes
▪ Which LTMOM functions are available with which
release

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

warranty.

OpenSAP s4h35 Week 1 All Slides

Uploaded by

Document Information

Original Description:

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

OpenSAP s4h35 Week 1 All Slides

Uploaded by

Copyright:

Available Formats

Week 1: Staging Tables Approach and Migration Object Modeler

Unit 1: Introduction to Data Migration

Week 1: Staging Tables Approach and Migration Object Modeler

By the end of this week, learners will be able to

Week 2: Direct Transfer Approach

Data migration requirements in a “new

Supporting tools: SAP Activate methodology,

Overview of SAP S/4HANA migration cockpit

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

Approach Business Driver Transition Option Target

SAP S/4HANA Cloud,

SAP S/4HANA Cloud,

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

Approach Business Driver Transition Option Target

SAP S/4HANA Cloud,

SAP S/4HANA Cloud,

What are the sources / sender systems of the data?

Migrate data “as is” or transform on the fly?

Who needs to be involved?

Bottom Line: Start as early as possible to ensure high quality data

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

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

Preconfigured SAP S/4HANA- Automated mapping

Integrated into SAP Lower migration time and costs

Migration object modeler for

SAP S/4HANA Cloud,

SAP S/4HANA Cloud,

SAP Business Legacy

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

Two different migration approaches, depending on the source system:

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

Preconfigured SAP S/4HANA-specific migration content

What is a migration object?

What is migration content?

What about updates on migration objects delivered by SAP?

Not designed for:

* Exception: FI – Historical balance migration object see SAP Note 2943035

▪ Amount of business data to be transferred and converted

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

In this unit you have learned

It is one key task during the transition to SAP S/4HANA.

Make sure to understand your data migration

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

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

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

SAP Fiori app Process and content Data load

Staging Direct Transfer

▪ SAP ERP 6.0

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

SAP Fiori app Process and content Data load

Staging Direct Transfer

▪ SAP ERP 6.0

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

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

▪ Maintain required roles and authorization:

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

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

In this unit you have learned

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

Name your project

Local SAP S/4HANA Database

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

You can use the search field