SAP S/4HANA Migration Cockpit
Transport concept
Migrate Data Using Staging Tables
SAP S/4HANA Product Management Data Migration and Data Transformation, SAP
September, 2023
PUBLIC
Document History
Revision
Date
Change
1.0
October 2021
Release for customer
2.0
May 2022
Update SAP S/4HANA 2021 FPS01
3.0
October 2022
Update SAP S/4HANA 2022
3.1
September 2023
Update add projects to transport request
Public
2
Agenda
01
05
Transport Functionality
- Basic Facts
System Modifiability
02
06
Transport Concept
How to Use a Project in a
Different Client
03
07
Transport Functionality
- How to transfer a project to
another system
Overview About Options for
Transferring Projects
04
Transport Functionality
- Allowed Activities
Public
08
Export/Import Functionality in
Older Releases
3
As of SAP S/4HANA 2021
Transport Functionality (Migrate Data Using Staging Tables)
Basis Facts
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!
Instances already uploaded to the staging tables will not be transported.
Only the definition of a rule, fixed value, translation object or variable is added to a transport request and
transported. No values, for example mapping values, are included.
Public
Back to Agenda
4
As of SAP S/4HANA 2021
Transport Functionality (Migrate Data Using Staging Tables)
Concept
Separation between design time and execution time activities
Transport
project
DEV
Transport
project
QAS
PRD
Design time activities*
e.g. create project, select migration
objects
Import change request and
update DB connection
(NO design time activities*)
Import change request and
update DB connection
(NO design time activities*)
Execution time activities
Execution time activities
Execution time activities
Individual
transport
of project
SBX
Adjust
manually in
DEV if
needed
Same release, patch level respectively
SAP Notes level required!
Import change request with project
and objects from DEV
and update DB connection
(NO design time activities*)
Execution time activities
e.g. execute migration, edit mapping
* Design time activities are allowed in systems which are
open for changes, usually DEV systems
DEV: Development System
QAS: Quality System
PRD: Production System
SBX: Sandbox System
5
Public
Back to Agenda
As of SAP S/4HANA 2021
Transport Functionality (Migrate Data Using Staging Tables)
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
assign a development package:
Choose the project and add it to a transport request
(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, see chapter 8, 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
Public
6
As of SAP S/4HANA 2021
Transport Functionality (Migrate Data Using Staging Tables)
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.
Public
Back to Agenda
7
As of SAP S/4HANA 2021
Transport Functionality (Migrate Data Using Staging Tables)
Allowed activities in DEV and QAS/PRD systems
DEV system: design time
QAS/PRD system: execution time
(system is open for changes)
(system is locked against changes)
FIORI app
FIORI app
▪ Create project (assign to development package)
▪ Upload data, prepare mapping, simulate, migrate
▪ Edit project (all project settings)
▪ Mapping values: edit, download/upload
▪ Add objects to project
▪ Finish project
▪ Change object settings (all object settings)
▪ Certain project settings (**)
▪ Content update/upgrade
▪ Upload data, prepare mapping, simulate, migrate*
LTMOM
LTMOM
▪ Change SAP objects, create own objects
(source fields, rules, field mapping, …)
▪ Only display mode
▪ Add dedicated objects / rules to transport
▪ It is possible to simulate the migration and to use
the debugging function as of SAP S/4HANA 2020 FPS01
*) optional
**) for details see next slide
Public
8
As of SAP S/4HANA 2021
Transport Functionality (Migrate Data Using Staging Tables)
Allowed activities in DEV and QAS/PRD systems - Details
Activity
DEV
QAS / PRD Comment
Create project
Project is transported
Add object to project
Object is transported
Database Connection (local /
remote)
Not transported; can be set only once after the import, then
cannot be changed again
Content upgrade
Update SAP objects with updates delivered by SAP
Settings for number of jobs
Settings are not transported
Execute migration activities
Can be executed in any system
Edit mapping values
Mapping values are never transported! They have to be
transferred by using the download/upload function if necessary.
Same applies to fixed value rules.
Set project to finished, set
retention time
Settings are not transported
Delete projects
Manually or automatically after expiration of retention period
Usage of transaction LTMOM
Changes to structures and rules only in DEV, then transport
Public
Back to Agenda
9
As of SAP S/4HANA 2020
System Modifiability (Migrate Data Using Staging Tables)
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.
As of SAP S/4HANA 2020, configuration is not possible in non-modifiable environments.
No project creation, no adding migration objects 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.
Public
10
As of SAP S/4HANA 2020
System Modifiability (Migrate Data Using Staging Tables)
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 (LTMOM).
Projects can only be created with the following settings:
1.
2.
Changes must be permitted for objects in the system at global level, cross client level, and client-specific level.
As of SAP S/4HANA 2021, the assigned development package must itself be assigned to a modifiable software component and
a modifiable namespace.
1. Check for client-specific and cross-client object changes
in transaction SCC4
client settings
system is modifiable if one of
these client settings is chosen
and
cross-client settings
one of these cross-client settings
is chosen
Public
11
As of SAP S/4HANA 2020
System Modifiability (Migrate Data Using Staging Tables)
2. Check for general system change options in transaction SE06 (button "System Change Option")
Global settings is set
to modifiable
Software component assigned to
the development package is set
to modifiable
Namespace assigned to the
development package is set to
modifiable
Public
Back to Agenda
12
As of SAP S/4HANA 2021
What if both Development and Test Client are on the Same System?
Use project in different client
If development and test system are
on the same system:
DEV + Test System
PRD system
Function LTMOM
“Use Project in different client”
Development
Test Client
client
Function LTMOM
“Use Project in different client”
Transport project
Public
1. Set up project in DEV client
2. Use project in Test client
Production client
3. In case of adjustments, use
project again in DEV client
4. Transport project to PRD
system
DEV: Development System
PRD: Production System
13
As of SAP S/4HANA 2021
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.
Public
14
As of SAP S/4HANA 2021
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.
Public
Back to Agenda
15
Overview of options to transfer projects from one system to another
Release
Import/Export
Functionality
Transport
Mechanism (DEVQAS-PRD)
Check on System
Modifiability
Use Project in
Different Client
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)
Public
16
How to Transfer Your Project to Another System within the Same Release
Export / Import / Transport Project (Migrate Data Using Staging Tables)
Project created in
What to do
Additional Considerations /
Prerequisites
SAP S/4HANA 2020,
via LTMC
1. Open the migration project that you want to transfer.
2. In the Migration Project Details screen, choose Export Content.
3. The system creates a zip file that contains the migration project. Save this file.
4. Open the migration cockpit in the other system and open the migration project
that has the same mass transfer ID as the project you want to transfer.
5. In the Migration Project Details screen, choose Import Content.
6. Select the zip file that you saved in step 3.
A project must exist in the target system with same mass
transfer ID.
1. Open migration object modeler (transaction LTMOM).
2. Use the export / import Project functionality. You first export a project from a
system and save the project as a zip file. You then import the zip file into the
other system.
Projects cannot be created in non-modifiable systems –
a new project will be created automatically with same
mass transfer ID (no need to have it beforehand).
To import a project for the first time, you must use the
report.
SAP S/4HANA 2020,
via SAP Fiori App
“Migrate Your Data”
Staging table names are different in D, Q, P systems ->
use mapping table /1LT/DS_MAPPING.
For detailed documentation, see:
help.sap.com - using files
help.sap.com - using staging tables.
You can use the report /LTB/MC_PROJ_Q2P instead.
For detailed documentation, see KBA 3054108,
and KBA 3081981.
As of SAP S/4HANA 2021
1.
2.
3.
4.
5.
6.
Open SAP Fiori App “Migrate Your Data” – Create project.
Specify a development package.
Open the migration object modeler (transaction LTMOM)
Choose a project and add it to a transport request.
Proceed with standard SAP transport functionality.
After importing the project in the other system, you are asked to provide the new
database connection when opening the project for the first time.
Projects cannot be created in non-modifiable systems.
For detailed documentation, see the system
documentation in transaction LTMOM.
Import/Export can be used instead in transaction
LTMOM only in SAP S/4HANA 2021 FPS0 and FPS01.
More details in KBA 3054108, and KBA 3081981.
Public
Back to Agenda
17
Export/Import Functionality in Older
Releases
SAP S/4HANA 2020
Export / Import Projects (File/Staging)
Use migration object modeler (LTMOM)
Before SAP S/4HANA 2020: You export/import projects using transaction LTMC.
In SAP S/4HANA 2020 but only for projects created with the Fiori App: You export/import projects using
transaction LTMOM (migration object modeler).
SAP S/4HANA 2020 – migration object modeler
Public
You first export a project from a system and save the
project as a zip file. You then import the zip file into the
other system. Mapping values, job settings, event
logs, staging tables and records in staging tables will
not be exported.
19
SAP S/4HANA 2020
Export / Import Projects (File/Staging)
Considerations
If the project you are importing does not exist in the system, a new
project will be created with the relevant project settings.
If the project you are importing already exists in the system, the existing
project settings will be overwritten with the exception of the following:
▪ Database connection
▪ Job settings
▪ Retention period settings
Check the report information on further details.
Non modifiable systems / production systems
It is not possible to create or modify projects in production system. You cannot, for example, remove a migration object. If
you need to make such an adjustment, you can adjust the project in the source system and transfer it again to the target.
This does not apply for projects created with LTMC.
Public
20
SAP S/4HANA 2020
Export / Import Projects (File/Staging)
Project created in older releases (with LTMC)
In SAP S/4HANA 2020, the namespace of mass transfer ID is
LTMC
X** to Z**
Migrate Your Data app
N** to O**
The mass transfer ID of your zip file from older versions of S/4HANA to S/4HANA 2020 will differ.
Therefore, you cannot import the migration project into the S/4HANA 2020 system*.
To export/import the migration project from one system to another, proceed as follows:
1. Copy the relevant migration object(s) from the existing project to the newly created project using the migration
object modeler LTMOM.
The copied migration objects will be treated as user-defined migration objects and cannot be
updated. This applies until SAP S/4HANA 2021. As of SAP S/4HANA 2022 copied migration
objects can be updated, if they are not user-defined.
2. The new project will have all the copied migration objects.
3. In the migration object modeler, use the Export/Import functionality to export and import the migration project
across different landscapes.
*Note: We do not recommend importing projects to an
SAP S/4HANA system with a different release.
Public
Back to Agenda
21
Thank you.
Contact information:
SAP S/4HANA migration cockpit Product Management Team
sap_s4hana_migration_cockpit@sap.com
Public
© 2022 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
22