Skip to Content
Product Information
Author's profile photo Sybille Lackermeier

SAP S/4HANA Migration Cockpit – tips&tricks

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.

http://open.sap.com/courses/s4h16

 

NEW 13.01.2020: new tips in section “Staging Tables” further below

 

NEW 03.12.2019:

  • Part 1: SAP S/4HANA migration cockpit – Migrating data using staging tables and methods for populating the staging tables

https://blogs.sap.com/2019/12/02/sap-s-4-hana-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

https://blogs.sap.com/2019/11/29/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

https://blogs.sap.com/2019/12/02/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

https://blogs.sap.com/2019/12/02/sap-s-4hana-migration-cockpit-using-sap-hana-studio-to-load-data-to-the-staging-tables/

____________________

NEW 26.11.2019:

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

 

  • 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:
    • /sap/bc/webdynpro/sap/DMC_WDA
    • /sap/bc/webdynpro/sap/DMC_WDA_GAF

 

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

Notes:

 

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

 

Sybille

 

Assigned Tags

      13 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Federica Quaranta
      Federica Quaranta

      Dear Sybille,

      we are trying to use LTMOM with function module UKM_DB_UKMBP_CMS_EXECUTE in a SAP S/4 HANA 1709 system. Our aim is to create the role UKM000 for existing BP.

      We are unable to upload the data in LTMC because of the error:

      Furthermore, in SE37 this function module is "not released":

      Can you help us?

      Thank you,

      Federica

       

      Author's profile photo Sybille Lackermeier
      Sybille Lackermeier
      Blog Post Author

      Hello Frederica,

      as this post is quite old - I suppose you did open a SAP incident.

      For your specific question on this role: You can use bapi BAPI_BUPA_ROLE_ADD_2 to maintain role UKM000.

      best regards, sybille

       

      Author's profile photo Frank Finkbohner
      Frank Finkbohner

       

      HI,

       

      there is a small typo in your naming convention for staging tables. It must be "1LT" not "LT1"

      /1LT/DS<sys-id><consecutive number>

      BR

      Frank

      Author's profile photo Manish pandey
      Manish pandey

      Can we use mss db for staging ??

       

      Author's profile photo Sybille Lackermeier
      Sybille Lackermeier
      Blog Post Author

       

      Hi,

      can you please specify "mss db"?

      regards, sybille

      Author's profile photo Manish pandey
      Manish pandey

      Microsoft SQL Server DB as the staging table DB

      Author's profile photo Sybille Lackermeier
      Sybille Lackermeier
      Blog Post Author

      staging tables can be created only in HANA DB. No other databases are supported here.

      Author's profile photo Guillaume Brochet
      Guillaume Brochet

      Hi Sybille,

       

      Thanks a lot for this useful blog.

      Please note that the OpenSAP course URL is : http://open.sap.com/courses/s4h16 

      (not 17).

      Author's profile photo Roman Hess
      Roman Hess
      Dear Sybille,
      maybe you know why I keep getting the following error message:

      No records found in staging table for this selection

      Message no. CNV_DMC_MC_EXCEPTION160

      
      when I try to debug a Stage-Object. Also i checked the tables are not empty!
      
      It works with File-Object but not with Stage-Objects. Is there anything i missed out?
      
      Thank you!
      
      
      
      
      
      Author's profile photo Sybille Lackermeier
      Sybille Lackermeier
      Blog Post Author

      Hello Roman,

      please open an SAP incident in component CA-LT-MC so that support can investigate further. Please state which SAP S/4HANA release you are working on and provide log-on credentials.

      Best regards,

      Sybille

       

      Author's profile photo Daniela Turcanu
      Daniela Turcanu

      Hello Sybille,

      I tried to find some information in regards of SAP best practice for using Migration Cockpit for carve-out activities. But unfortunately I did not find so many recommendation about it.

      Can Carve-out activities be done via Cockpit? Having in mind that we are going to use legacy system S4 as source and target?

      If any documentation available, can you please help me with?

       

      Thank you in advance,

      danielaT

       

       

      Author's profile photo Sybille Lackermeier
      Sybille Lackermeier
      Blog Post Author

      Hello Daniela,

      what you can do with Direct Transfer -> only select dedicated company codes and migrate them. Keep in mind: SAP S/4HANA will not work as source system, only ECC (due to different table structures).

      When you want to have a Carve-out/Merge scenario which is more complex (maybe also with historical data), this then will not belong to NEW IMPLEMENTATION, rather than SELECTIVE DATA TRANSITION.

      regards, Sybille

      Author's profile photo Daniela Turcanu
      Daniela Turcanu

      Thank you very much Sybille!

      I have found my answers.

      Thank you again for all your support,

       

      with kind regards,

      danielaT