SAP S/4HANA Migration Cockpit
Transport concept between Directly from SAP vs staging tables
LTMC
deprecated and moved to Fiori successfully.
please
check updates here about LTMC different versions:
SAP Data Migration – SAP LTMC and
LTMOM / LSMW vs LTMC:
https://blogs.sap.com/2021/08/08/sap-data-migration-sap-ltmc-and-ltmom-lsmw-vs-ltmc/
Migrate your data – Fiori / LTMC /
Migration cockpit Decommissioned? or replaced?
https://blogs.sap.com/2021/08/15/ltmc-migration-cockpit-decommissioned-or-replaced/
Migrate your Data – Migration
Cockpit / LTMC on SAP Fiori
https://blogs.sap.com/2021/09/26/migrate-your-data-migration-cockpit-ltmc-on-sap-fiori/
Before
2020 version, the transport is based on export and import between clients and
environments.
Now
with SAP S/4HANA, 2020 release SAP has bought Transport Concept into Migration
Tools.
Transport
concept for 2 different ways
·
- SAP S/4HANA Migration Cockpit – Migrate Data
Directly From SAP
- SAP S/4HANA Migration Cockpit – Migrate Data
Using Staging Tables
1. Transport Concept, SAP S/4HANA
Migration Cockpit – Migrate Data Directly From SAP
- The transport functionality used in the migration
cockpit is designed to transport from one system to another.
- Introduced with SAP S/4HANA 2020.
- You assign a development package while creating a
project (SAP Fiori app). Note that it is not possible to change this
assignment later.
- 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.
LTMC
Allowed
Activities in DEV and QAS/PRD Systems:
Allowed Activities in DEV and QAS/PRD
Systems
Allowed
Activities in DEV and QAS/PRD – Details
Allowed Activities in DEV and QAS/PRD
– Details
Transport
Between Clients:
The
SAP S/4HANA migration cockpit does not support transaction SCC1 or
SCC1N for transporting content from one client to another.
If you
want to distribute a project within a system from one client to another, e.g.
for testing purposes, proceed as follows :
1. Create transport in client A. You can use category “Workbench” or “Transport
of copies”.
2. Add relevant project to the transport (see function in transaction LTMOM).
3. Inform the system administrator to release the transport request in client
A.
4. Ask the system administrator to import the transport request manually in
client B (e.g. via transaction STMS).
System
Modifiability:
Connected
to the transport functionality (since 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. Changes must be permitted for objects in the system at global level, cross
client level, and client-specific level.
2. The assigned development package must itself be assigned to a modifiable
software component and a modifiable namespace.
Check
for client-specific and cross-client object changes
in transaction SCC4
2. Check for general system change
options => transaction SE06 (button “System Change Option”)
Check for general system change
options – transaction SE06 (button System Change Option)
Now,
lets discuss about Staging tables:
2. SAP S/4HANA Migration
Cockpit – Migrate Data Using Staging Tables
- The transport functionality used in the migration
cockpit is designed to transport content from one system to another.
- The functionality is available with SAP S/4HANA
2021 onwards for the approach Migrate Data Using Staging Tables.
- You assign a development package while creating a
project (SAP Fiori app). This assignment cannot be changed later.
- You can 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.
- 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.
Transport Functionality
(Migrate Data Using Staging Tables) Concept:
Transport Functionality (Migrate Data
Using Staging Tables) Concept
Allowed activities in DEV and QAS/PRD
systems:
Allowed activities in DEV and QAS/PRD
systems
Allowed
activities in DEV and QAS/PRD systems – Details:
Allowed activities in DEV and QAS/PRD
systems – Details
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. Changes must be permitted for objects in the system at global level, cross
client level, and client-specific level.
2. As of SAP S/4HANA 2021, the assigned development package must itself be
assigned to a modifiable software component and a modifiable namespace.
- Check for client-specific and cross-client object
changes in transaction SCC4:
Check for client-specific and
cross-client object changes
2.
Check for general system change options in transaction SE06 (button “System
Change Option”)
Check for general system change
options in transaction SE06 (button System Change Option)
The
conclusion is:
Overview
About Options for Transferring Projects:
Conclusion Overview
