S/4HANA Migration Cockpit – Direct Transfer (Quickguide)
As more and more S/4HANA Projects are on the road and customers are planing for a S/4HANA Transformation project in near future I am often asked about “Data Migration”. First of all there is a main difference in the Transformation approach (New Implementation, System Conversion, Selective Data Transition) a customer will choose which leads to the migration approach that matches best. I will not go into detail of each approach but only will highlight my experience with the S/4HANA Migration Cockpit – direct transfer.
You can learn more about the different migration approaches here: https://www.sap.com/documents/2017/07/26113ac0-c47c-0010-82c7-eda71af511fa.html
For a New Implementation customers may choose the S/4HANA Migration Cockpit, as it comes with the S/4 HANA on-Premise Release out of the box without additional costs.
As good starting point I recommend this blog: https://blogs.sap.com/2019/09/23/sap-s4hana-migration-cockpit-tansfer-data-directly-from-sap-system-direct-transfer/
New with S/4HANA 1909 Release is the direct transfer option that allows to migrate data from an existing SAP ERP System (lowest supported release is ERP 6.0 / NW 7.0) directly into S/4HANA via RFC connection. This does neither require staging tables (available since Release 1709 FPS2) nor file transfer (available since Release 1511), which eliminates known data volume restrictions (i.e.100MB file size).
To get MC direct transfer up an running please start with the following SAP notes:
First make sure /LTB/ namespace is registered with repair key (SAP Note 2546754 ) and continue with the MC central SAP note: 2819445 & 2817159
Additionally I had to implement the following SAP notes: 2857334 , 2863688 , 2809042 , 2803928
Assign the business roles “SAP_DMIS_OBT_MASTER & SAP_BR_CONFIG_EXPERT_DATA_MIG” to your user. You will find all relevant information about the MC Fiori App here: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps(‘F3473’)/S15OP
Create a new migration project and select the direct transfer scenario.
Next step is to select your migration objects (currently 97). All available Migration objects can be found here (filter by direct transfer!): http://help.sap.com/S4_OP_MO
After you save your project in the background the migration objects are prepared in the system, which takes a couple of minutes. The “Activity Tracking” is a nice function that will show you the status. This can also be used within migration object later on.
Select your data. You can increase the speed by adjusting the background processes.
Under Project settings -> Technical Information you see the maximum available number of background jobs for the whole project.
Then apply your mapping rules. This could be a longer task, depending on the mapping requirements.
Finally you can migrate your data.
Happy data migrating & Best Regards
Thanks for the blog.
If the migration approach for a standard migration object is listed as File Transfer, would it still support the file/staging approach? or not at all?
only what is mentioned in the list is what is supported per MO.If MO supports "file & staging tables" then no direct transfer for this MO is possible. Sometimes MO are mentioned more than once, that is why you best work with filters.
MO "Routing" is a good example, which is mentioned multiple time and is supported for all three approaches... http://help.sap.com/S4_OP_MO
Does it required to install any component or add-on on source system to extract data?
We have some issues regarding the Direct Transfer options for which we tried the following always for one Company Code containing ~1000 records in the source system:
Our issue is that after the object is being prepared, regardless of the 3 cases, every time we get exactly and the same 39 errors:
Also, in LTMOM we can notice that no Migration Objects are created for these Direct Transfer:
Any ideas what should we try? The RFC connections are working, we tested them via transaction SM59.
hard to answer or doing remote diagnostics. Most often this is depending on you target stack and/ DMIS version. I assume it is inside the "cloning procedure" of the standard migration objects.
Did you try this SAP note already? https://launchpad.support.sap.com/#/notes/2856116
Thank you for your input! The SNOTE is not applicable to our system, but we tried it nevertheless. Any other ideas are welcomed.