SAP Blogs

New Installation of SAP S/4HANA 2020FPS0 – Part 5 – Direct Data Transfer using Migration Cockpit

New Installation of SAP S/4HANA 2020FPS0 – Part 5 – Direct Data Transfer using Migration Cockpit

There is lots of content out there – blogs, notes, ppts, guides, videos, eLearning Hub, and the key to fast tracking this is to find out all the notes that apply. This blog will take you there in a structured way for current release and you can use same logic for future releases to find out all the details easily.

Basic understanding of the types of notes makes it easy to crack the process. This way you know which notes you have to read, which notes you have to read and apply as corrections using SNOTE.

The sequence in which you migrate data from ERP to S/4HANA is as follows in this order:

    (1) Organization data – configure Company Code, Sales Org, Purchasing Org, Plant, etc

    (2) Master Data – Customer, Vendor, Material, General Ledger, Customer Material InfoRecord, Pricing conditions, Source List, Planned Independent Requirements, etc

    (3a) Open Balances – General Ledger balance, Inventory balance, Accounts Receivable balance, Accounts Payable balance, etc

    (3b) Open Transactions – Open Sales Orders, Open Purchase Orders, Open Contract, etc.

    We will first prepare the Source ECC System. Then create RFC connection to ECC system, then prepare target S/4HANA System (prepared based on blogs Part 1 – 4 above) and then Start data migration using Fiori App.


    Let’s first find out the note applicable. It’s good to know the difference between Composite Note – which is a note that includes Installation information of all releases like 1909, 2020, etc You have to first go to SAP Note 2780378 Composite SAP Note for SAP S/4HANA Migration Cockpit (all releases) to find out which notes are applicable to the release and then for more details in SAP Note 2747566 – SAP S/4HANA Migration Cockpit: Composite Note for Transfer Data Directly from SAP System.

    Then you have to refer to Central Note specific release like 2020. So we locate Central Note 2946774 (BackEnd for correction notes) and 2967468 (FrontEnd) and 2973957 (ERP).

    There is an Analyzer Note 2596411 to be applied in the S/4HANA system to run program DMC_NOTE_ANALYSER to find out if any more correction notes are required. Also in ERP system we have to refer to Note 2974017 for DMIS installation and correction notes included.

    There is a FAQ Composite Note which we will use for the step sequence SAP Note 2747566 – SAP S/4HANA Migration Cockpit: Composite Note for Transfer Data Directly from SAP System

    There is a Collective FAQ Note 2537549 that has KBAs for migration objects, like for example the Consulting Note 2663293 – Migration Cockpit: Analyze Fixed Asset data migration errors This note says the error could be a configuration/customizing issue and may be due to inconsistencies/incorrect values.

    There is also a KBA Note 2778320 – Release Comparison of Migration Objects which contains information about the changed structures and fields between the different releases.


    (A) Read SAP Note 2973957 – SAP S/4HANA Migration Cockpit: Composite Note for Transfer Data Directly from SAP System – SAP ERP or SAP AFS to SAP S/4HANA.

    (B) Follow Note 2974017 – Installation and delta upgrade of DMIS 2011_1

    Install the latest SPAM update to latest version. Upgrade/Install DMIS 2011_731 SP19 on source system. For fresh installation, go to Software Download – DMIS Choose DMIS and then DMIS 2011_1_731 to download K-116AGINDMIS.SAR

    After all the files have been uploaded/extracted, login to client 000 and apply DMIS Add-on using SAINT and password for DMIS 2011_731 fresh install is 51055C245A

    (C) Create User in Source System for Data Transfer.

    Login to Source System Client from where you want the data transferred. Use tCode SU01 and Create User ECC_RFC_USER, User Type = Communications Data, User Role = SAP_DMIS_OBT_REMOTE.

    TIP1: The user ECC_RFC_USER allows access to data in ECC system and SAP has further tightened the security in S/4HANA 2020 to reduce the authorizations for a standard role from SAP_DMIS_OBT_REMOTE. When testing through SM59 the RFC connection for authorization you will get error – No RFC authorization for function module RFCPING. This is normal in view of reducing authorization to bare minimum, but data migration will work. If you want to test, temporarily assign SAP_ALL for testing.

    TIP2: For assigning role SAP_DMIS_OBT_REMOTE, it is recommended to use copy of the role. Please ensure that the assigned role is “Generated” after going into tCode PFCG and clicking on change, Authorizations tab, Change Authorization Data button, Generate. If you don’t do this you may get errors due to authorization issue.

    TIP3: In case you do not have ERP system and want to try the example, please use IDES ERP 6 EHP8 system. Copy from CAL (60 mins) or Install from media. You will have to upgrade DMIS add-on to the latest as above.


    Login to Target S/4HANA System, tCode SM59 and Create RFC Destination as per graphic:

      (1) ECC_S4H_XFER, Connection Type 3

      (2) Specify Language = EN, Client = 100, User = ECC_RFC_USER, Password.

      (3) Save

      (4) Menu -> Utilities, => Test => Authorization Test


    Steps are based on system prepared with Part1 to Part4 of the blog for New Installation. In Part 3 the Best Practices Content Activation would be done without demo data. This requires unchecking the demo data option in the first dialog after starting activation.


    Login to BackEnd tCode SLG1 and filter for Transaction Code MWB


    Migration Cockpit – Direct Transfer – use component CA-LT-MC

    Migration Cockpit – File/Staging – use component CA-GTF-MIG


    The notes applied have to be moved across the landscape using transport. Users will have to be manually created in each system.

Leave feedback about this

  • Rating