SAP S/4HANA Migration Cockpit - Migrate Data Directly from SAP System - Transport Concept
This document shows details on transport concept in the frame of Migrate Data Directly from SAP system approach. You will learn the basic information, allowed activities in the development, test and production systems, transport between clients, system modifiability and more. Download the DocumentPublic
SAP S/4HANA Migration Cockpit
Transport Concept
Migrate Data Directly from SAP
SAP S/4HANA Product Management Data Migration and Data Transformation
January, 2024
SAP S/4HANA Migration Cockpit
Transport Concept
Migrate Data Directly from SAP
SAP S/4HANA Product Management Data Migration and Data Transformation
January, 2024
2Public
Transport – the basics
Transport concept
Allowed activities in DEV and QAS/PRD
Allowed activities in DEV and QAS/PRD - details
Transport between clients
System modifiability
More information
Agenda
Transport – the basics
Transport concept
Allowed activities in DEV and QAS/PRD
Allowed activities in DEV and QAS/PRD - details
Transport between clients
System modifiability
More information
Agenda
3Public
Transport – The Basics
▪ The transport functionality used in the migration cockpit is designed to transport from one system to
another.
▪ Introduced with SAP S/4HANA 2020.
▪ Until SAP S/4HANA 2022, you assign a development package while creating a project (SAP Fiori app).
Note that it is not possible to change this assignment later.
▪ Starting with SAP S/4HANA 2023 you do not assign a development package any more during the
project creation. You only go to transaction LTMOM and assign your project to a customizing transport
number.
▪ You have the possibility to add projects, migration objects, and rules to a transport request in transaction
LTMOM.
▪ It is not possible to create or edit projects in non-modifiable systems, they can only be executed. Usually,
non-modifiable systems are quality and production systems. For more information about non-modifiable
systems, see slide 10.
▪ For information about how to transport from client to client within one system, see slide 8
Selected instances and mapping values are not transported!
Transport – The Basics
▪ The transport functionality used in the migration cockpit is designed to transport from one system to
another.
▪ Introduced with SAP S/4HANA 2020.
▪ Until SAP S/4HANA 2022, you assign a development package while creating a project (SAP Fiori app).
Note that it is not possible to change this assignment later.
▪ Starting with SAP S/4HANA 2023 you do not assign a development package any more during the
project creation. You only go to transaction LTMOM and assign your project to a customizing transport
number.
▪ You have the possibility to add projects, migration objects, and rules to a transport request in transaction
LTMOM.
▪ It is not possible to create or edit projects in non-modifiable systems, they can only be executed. Usually,
non-modifiable systems are quality and production systems. For more information about non-modifiable
systems, see slide 10.
▪ For information about how to transport from client to client within one system, see slide 8
Selected instances and mapping values are not transported!
4Public
DEV QAS PRD
SBX
Design time activities*
e.g. create project, select migration
objects
Execution time activities
Import change request
and update connection
(NO design time activities*)
Execution time activities
Import change request
with project and objects from DEV
and update connection
(NO design time activities*)
Execution time activities
e.g. execute migration, edit
mapping
Import change request
and update connection
(NO design time activities*)
Execution time activities
Individual
transport
of project
Adjust
manually in
DEV if
needed
Transport
project
Transport
project
*Design time activities are allowed in systems which are open for changes, usually DEV systems
Separation between design time and execution time activities
Same release, patch level respectively SAP notes
level required!
Transport Concept
DEV: Development System
QAS: Quality System
PRD: Productive System
SBX: Sandbox System
DEV QAS PRD
SBX
Design time activities*
e.g. create project, select migration
objects
Execution time activities
Import change request
and update connection
(NO design time activities*)
Execution time activities
Import change request
with project and objects from DEV
and update connection
(NO design time activities*)
Execution time activities
e.g. execute migration, edit
mapping
Import change request
and update connection
(NO design time activities*)
Execution time activities
Individual
transport
of project
Adjust
manually in
DEV if
needed
Transport
project
Transport
project
*Design time activities are allowed in systems which are open for changes, usually DEV systems
Separation between design time and execution time activities
Same release, patch level respectively SAP notes
level required!
Transport Concept
DEV: Development System
QAS: Quality System
PRD: Productive System
SBX: Sandbox System
5Public
QAS/PRD system: execution time
(system is locked against changes)
FIORI app
➢ Select data, prepare mapping, simulate, migrate
➢ Mapping values: edit, download/upload
➢ Finish project
➢ Certain project settings **
LTMOM
➢ Only display mode
➢ It is possible to simulate the migration and to use the
debugging function.
DEV system: design time
(system is open for changes)
FIORI app
➢ Create project (assign to development package)
➢ Edit project (all project settings)
➢ Add objects to project
➢ Change object settings (all object settings)
➢ Content update/upgrade
➢ Select data, prepare mapping, simulate, migrate*
LTMOM
➢ Change SAP objects, create own objects
(source tables, rules, field mapping, ...)
➢ Add dedicated objects / rules to transport
Allowed Activities in DEV and QAS/PRD Systems
**) for details see next slide
*) optional
QAS/PRD system: execution time
(system is locked against changes)
FIORI app
➢ Select data, prepare mapping, simulate, migrate
➢ Mapping values: edit, download/upload
➢ Finish project
➢ Certain project settings **
LTMOM
➢ Only display mode
➢ It is possible to simulate the migration and to use the
debugging function.
DEV system: design time
(system is open for changes)
FIORI app
➢ Create project (assign to development package)
➢ Edit project (all project settings)
➢ Add objects to project
➢ Change object settings (all object settings)
➢ Content update/upgrade
➢ Select data, prepare mapping, simulate, migrate*
LTMOM
➢ Change SAP objects, create own objects
(source tables, rules, field mapping, ...)
➢ Add dedicated objects / rules to transport
Allowed Activities in DEV and QAS/PRD Systems
**) for details see next slide
*) optional
6Public
Allowed Activities in DEV and QAS/PRD - Details
Activity DEV QAS / PRD Comment
Create project YES NO Projects must be transported to the QAS / PRD system.
Add object to project YES NO Objects must be transported to the QAS / PRD system.
Define connection to source system
(RFC)
YES YES Not transported; can be set only once after the import, then cannot be
changed again.
Selection of organizational units (Fiori) YES YES (see
comment)
Selection of organizational unit (e.g. company codes) is not transported;
can be set only once after the import, then cannot be changed again.
Edit selection settings (LTMOM) YES NO Selection settings edited in LTMOM are transported.
Edit number of jobs YES YES Number of jobs is not transported.
Select, simulate, migrate YES YES Can be executed in any system.
Edit mapping values YES YES Note that mapping values are never transported. They have to be
transferred by using the download/upload function if required. The same
applies to fixed value rules.
Set project to Finished, set retention
time
YES YES Settings are not transported.
Delete projects YES YES Can be done manually (DEV) or automatically (DEV, QAS, PRD) after
expiration of retention period.
Usage of transaction LTMOM YES NO Any adjustments made using transaction LTMOM must be transported.
Allowed Activities in DEV and QAS/PRD - Details
Activity DEV QAS / PRD Comment
Create project YES NO Projects must be transported to the QAS / PRD system.
Add object to project YES NO Objects must be transported to the QAS / PRD system.
Define connection to source system
(RFC)
YES YES Not transported; can be set only once after the import, then cannot be
changed again.
Selection of organizational units (Fiori) YES YES (see
comment)
Selection of organizational unit (e.g. company codes) is not transported;
can be set only once after the import, then cannot be changed again.
Edit selection settings (LTMOM) YES NO Selection settings edited in LTMOM are transported.
Edit number of jobs YES YES Number of jobs is not transported.
Select, simulate, migrate YES YES Can be executed in any system.
Edit mapping values YES YES Note that mapping values are never transported. They have to be
transferred by using the download/upload function if required. The same
applies to fixed value rules.
Set project to Finished, set retention
time
YES YES Settings are not transported.
Delete projects YES YES Can be done manually (DEV) or automatically (DEV, QAS, PRD) after
expiration of retention period.
Usage of transaction LTMOM YES NO Any adjustments made using transaction LTMOM must be transported.