SAP S/4HANA migration cockpit, direct transfer, transport capabilities
we have just created a detailed slide deck which describes the transport functionality within the SAP S/4HANA migration cockpit, direct transfer. This functionality is available since release 2020 OnPrem.
The slide deck also talks about transporting from client to client and system modifiability.
LINK to slide deck.
I want to share some more information about connected source systems. We have enhanced our docu with the following:
You may want to use a different client or even a different source system for test purposes. However, if you want to connect to a new source system or client, you need to create a new migration project.
When you create a migration project that connects the SAP S/4HANA migration cockpit to a source system, the SAP S/4HANA migration cockpit creates objects (for example ABAP dictionary and repository objects) in the source system. These objects allow the SAP S/4HANA migration cockpit to select data from the source system. However, if you simply specify a new RFC connection in the migration project, these objects are not created in the new source system or client. You therefore need to create a new project if you want to migrate data from a different system or client.
Note that if your migration project uses a source system that is refreshed with new data, you also need to create a new migration project as the objects mentioned above will not be present in the refreshed source system.
You are also welcome to visit our so-called landing page – you find there all externally available training material: LINK.
SAP S/4HANA Product Management, Migration Cockpit