Hello S/4HANA migration cockpit users,
in this blog we would like to share some best practices, either in documents or short videos.
NEW 29.4.2020 Create your Test System
Check out the possibility to create a test system in fully-activated appliance: https://blogs.sap.com/2020/04/27/sap-s-4hana-migration-cockpit-create-your-test-system/
NEW 5.2.2020 openSAP Course
Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario
With this course, you’ll get an introduction to data migration with SAP S/4HANA, and where it fits in with respect to the different transition scenarios. The course will focus on the new implementation scenario, with a deep dive into the SAP S/4HANA migration cockpit and the migration object modeler. We’ll also offer optional hands-on exercises so you can better familiarize yourself with the different migration approaches. For these exercises, you can use a system image from the SAP Cloud Appliance Library. The course starts March 25.
NEW 13.01.2020: new tips in section “Staging Tables” further below
Part 1: SAP S/4HANA migration cockpit – Migrating data using staging tables and methods for populating the staging tables
Part 2: SAP S/4HANA migration cockpit – Using SAP Data Services to load data to the staging tables
Part 3: SAP S/4HANA Migration Cockpit – Using SAP HANA Smart Data Integration (SDI) to load data to the staging tables
Part 4: SAP S/4HANA migration cockpit – Using SAP HANA Studio to load data to the staging tables
Check Data Migration Landing page on help.sap.com
|Landing Page SAP S/4HANA||http://help.sap.com/S4_OP_DM|
|Landing Page SAP S/4HANA Cloud||http://help.sap.com/S4_CE_DM|
Check Quick Links for available migration objects
|Available migration objects SAP S/4HANA||http://help.sap.com/S4_OP_MO|
|Available migration objects SAP S/4HANA Cloud||http://help.sap.com/S4_CE_MO|
Analyzing API Calls Triggered by the SAP S/4HANA Migration Cockpit
The purpose of this guide is to assist users with the processing of messages raised by an API that is called by the migration cockpit for the migration approaches “Migrate Data Using Files” or “Migrate Data Using Staging Tables” – find document link here.
Start / Continue Transfer Button – Continuing with the migration after logging off
When you choose Start Transfer for a migration object, the system displays a guided procedure for the migration process. Depending on the volume of data to be transferred, the migration process may take some time. You can log off or choose “Run in Background”. When you log back on to the system, choose the Start Transfer button to display the guided procedure again and view the current status of the transfer – so it is a “Continue”.
Migration Cockpit – check error logs (10.4.2019)
If you need to access the backend logs, please find information in Note 2517820
Migration Object Modeler
- First, create a project in LTMC – then go to LTMOM to change/create migration object
- How-to Guide: SAP S/4HANA Migration Cockpit: Creating a New Migration Object with the migration object modeler – find PDF
Migration Cockpit – check relevant notes
- Use the report DMC_NOTE_ANALYZER to list all notes from the Centrap SAP Note hata are not implemented yet
- Choose 2594002 for Centrals SAP Note Number
Migration Cockpit – Staging Tables
- Knowledge Base Article (KBA) Transfer Data Using Staging Tables SAP Note 2733253
- Check backend Transcation DBCO if your database connection is available
- White-list this connection in table DMC_C_WL_DBCO_OP; use SM30
- Naming convention staging tables: /1LT/DS<sys-id><consecutive number>
- due to technical reasons, staging tables are transparent tables – can be seen in SE11 – but are not used, only tables in HANA schema. To acces them you can use OpenSQL
- When you are adding fields to an object that is already established in MC, it is advisable to save, synchronize structures and generate in every source structure after 5-10 additional fields. This way you will find an issue as you are programming and not after all is done.
- Definitely save, synchronize structures and generate after adding fields to each structure to see if there are any issues – choose from menu bar -> “Synchronize Structures”
- If it is required to change a Source field name in LTMOM, it is suggested to delete the table row with the incorrect table name and save, synchronize, and generate. Then go back and add the correct field name, save, synchronize, and generate.
- If you get the message “Staging tables are locked for transfer” – click the “Restart Transfer” button.
- NUMC fields must have leading zeros SAP Note260849
- DATE fields are YYYYMMDD
Migration Cockpit – Short Learning Videos
- Learn how to personalize your view (e.g. to create an “active view” for your migration objects): Personalize View
Migration Cockpit ICF Services
- In the backend system call transaction /nsicf
- Activiate following services:
MOM: New migration object – Create own function module:
Find details in SAP Note 2590165
MOM: Which function modules to use with newly created migration objects
- Only function modules that are released shall be used
- If a function module is released to be used by customers can be checked easily in SE37 -> „Attributes“ and “Released on” field.
- Example for a released FM:
- Example for a FM that is not released:
- You should also check the SAP Notes for the FMs they want to use to get more information and also error corrections, e.g. RFC_CVI_EI_INBOUND_MAIN: 2506041 – S4TWL – API RFC_CVI_EI_INBOUND_MAIN is obsolete in SAP S/4HANA; 2387032 – Maintain the Task field in the communication segment in RFC_CVI_EI_INBOUND_MAIN; 2518068 – Load Credit Management Data with RFC_CVI_EI_INBOUND_MAIN
MOM: testing a migration object
When you created your own migraton object using a XML template, you may want to run a simulation/test. This report for kind of debugging funciontality is availabe from 1709 FPS01.
Please check note 2630182