quinta-feira, 26 de setembro de 2019

SAP S/4Hana Data Migration Cockpit Insights and Business Partner

SAP S/4HANA Data Migration Cockpit
Hi 🙂 ,
Welcome to Migration cockpit World…
After huge success of SAP Data Services, SAP introduces another good product for data migration called- Migration Cockpit(MC).
Data migration is a process of transforming data from heterogeneous systems to heterogeneous targets with lots of information.
Data Migration is one of the keys and complex areas in an SAP implementation project.
So the Data Migration process includes:
  • Extraction of data from the source system
  • Transformation of the data to SAP format
  • Loading of data into the corresponding SAP module
Introduction:
In a new implementation of SAP S/4HANA system, data is migrated from the SAP system/Non-SAP system to SAP S/4HANA system.
SAP S/4HANA provides comprehensive migration solutions with no programming requirement by the customer, automated mapping of data between source and target system, predefined templates, easily integrated custom objects, reduce test effort and minimize downtime.
Following are different options available for data migration in SAP S/4HANA on-premises:
  1. SAP DATA Services (SAP DS)
  2. SAP Rapid Data Migration Content
  3. SAP S/4HANA Migration Cockpit with Migration object modeler

  1. SAP Data Services:
    SAP DS is an ETL tool from SAP, which was a huge success for Dataware house and data migration which follows the methodology as E-T-L (Extraction, Transformation, and Load). It also provides data quality management and text data processing. The ETL capabilities of the tool can be used free of charge, but the data quality features require a Data Services license.
  2. SAP Rapid Data Migration:The rapid data migration to SAP S/4HANA solution enables you to realize the full benefits of our next-generation business suite even faster. It accelerates the process of cleansing, validating, transforming, and migrating your data from any system to SAP S/4HANA.
  3. SAP S/4HANA Migration Cockpit(MC):Here we will discuss data migration in SAP S/4HANA system using Migration Cockpit and create a sample business partner-Supplier.
    • SAP S/4HANA migration cockpit is an automated migration tool provided with preconfigured content and mapping for each migration object. For all major functional areas like a business partner, product, customer, bank, profit center, cost center, plant, GL, etc.
    • Migration objects are predefined and their sequence and dependency are also defined. Each migration object contains its own predefined template in which source data is uploaded. Automatic mapping is done in source and target structures using the template. Migration programs are automatically generated for validating data, simulating data and loading into the target system
Key Features of Migration Cockpit:
  • This tool is embedded and delivered with SAP S/4HANA system
  • No programming is required by the customer
  • This tool is used to migrate data from SAP or Non SAP system to SAP S/4HANA
  • This tool has a predefined migration object which contains a mapping for all master/transactional data. It reduces migration cost and time
  • Migration activities are predefined and easy to use
The Actual technical part is here:
Let us start how to deal with migration cockpit:
Go to transaction codeL LMTC –> It will open MC on a new web browser.
Step 1:
The Web browser has been opened with the above transaction:

Step 2:
Here, to start with a new project, please click on the “Create” button as highlighted in below screen and it will pop-up with project details to-be filled screen.
Step 3:
Please enter Project name and Default view as shown below:
The main thing is Master Transfer ID: it generated automatically based on existing projects count, If you want your own customized ID, Please click on “Generate New Mass Transfer ID”.
This Transfer ID has its own interesting part at code movement between different systems.
Note: It should be same and unique across all environments.
Example: If DEV-008 then TEST and QUALITY should be 008.
Let’s create Project:
Step 4: Project has been created successfully.
Step5: Go to LTMOM and select the object level information:
Step 6: Now create a migration object here:
Step 7: Creating a Migration object
Step 8: Select the created project from LTMC

Step 9: Select your object- here I have selected Supplier

Step 10: You can check the status of creation as highlighted in below screen, Once the object is selected, go for the further steps:

Step 11: Check the source structure

Step 12: Check the target structure
The important thing here: It displays which function module it uses.
Step 13: Now click on Generate object button highlighted below:

Step 14: Finally, Object has been generated with source and target structures.
Step 15: Now go back to MC and select the generated object:
Step 16: Now download the template:
Step 17: Download template
Step 18: Once the template is downloaded, ensure it is relevant one.
Step 19: Fill the values(sample values been portrayed here)
Note: you need to fill all the sheets whatever been selected at the time of creating the project in LMTC and MC.
Step 20: Upload The filled template
It is uploaded

Step 21: Activate it
Step 22: It is activated and then please click “start transfer
Step 23:  start transfer (results)
Step 24: click next for convert values
Step 25: Results of Start transfer
Step 26: Follow convert values and simulate report
Step27: Click next and start “Execute import”
Once this step is done, click on FINISH and check results in SAP S/4 HANA.
In the next blog posts, we can discuss more on processings.
That’s all about this blog post.
Happy Learning!!! 🙂


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.

Migration Cockpit – check error logs (new: 10.4.2019)

If you need to access the backend logs, please find information in Note 2517820

Migration Object Modeler 

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 – Development News 1808 – 1809

  • There are new features for 1808 and 1809. Please find details in the ppt here.

Migration Cockpit – Staging Tables

  • Knowledge Base Articel (KBA) Transfer Data Using Staging Tables SAP Note 2733253

  • Check backend Transcation DBCO if your database connection is available
  • you need to 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

  • 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

Migration Objects Overview

Find an overview on pre-delivered content for
On the right top corner you can access a crop-down list to choose the release you are working on.

MOM: New migration object – Create own function module:

  • In general the API must be a function module (FM) – RFC capability is not required.
  • OData and other techniques are currently not supported by the SAP S/4HANA migration cockpit.
  • The pre-requisites are quite the same as the BAPI definitions in the BAPI Programming Guide
  • The API must not execute ‘COMMIT WORK’ commands. The COMMIT control is handled by the Migration Tool
  • Error Handling: All messages must be returned in a BAPIRET2 formatted table or structure.
  • API should provide a test run flag to simulate the data creation
    • Internal Buffers must be refreshed in case the API is called in test run mode to prevent buffer overflows and performance issues when calling in a loop
  • Consistency Check: Write-enabled API methods must make all the necessary consistency checks to ensure that the modified or newly created instance is consistent.
  • Plausibility Checks: All necessary plausibility checks must be done within the API
  • If some of the prerequisites are not met, you can develop a wrapper (e.g. for old IDocs).
Find more 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:

Videos:


UI:

  • If you use SAPGUI 7.50 we recommand to unflag “SAP Fiori visual theme”

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

SAP S/4HANA migration cockpit, what do you need to know?

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
UPDATED August 16, 2019
Registration link for new August release EGI on Data Migration Strategy and Tools
New blog reference to details for the new ongoing EGI
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The SAP S/4HANA migration cockpit is SAP’s standard solution to migrate business data for new implementation scenarios of SAP S/4HANA Cloud or on-premise.
SAP Enterprise Support Academy held a meet-the-expert (MTE) webinar in July on what you need to know about the migration cockpit in SAP S/4HANA, and a new series of multi-day remote sessions has now been released beginning August (see “EGI” below) to tighten up on your skills.
The MTE focused on the usage of the migration cockpit, how to create a migration project, and how pre-defined migration objects identified via your selected solution scope facilitate the transfer of business data from your source system. Special emphasis was on the functions and features particular to the following implementations: SAP S/4HANA on-premise and SAP S/4HANA Cloud, single tenant edition:
  • SAP S/4HANA transition paths
  • Current migration approaches (transferring data using files or staging tables, and methods in transferring data directly from SAP sources)
Before you can access the replay and registration links, a one-time registration in SAP Learning Hub, edition for SAP Enterprise Support, is required. A detailed step-by step guide to registration can be found here.
Watch the MTE replay
SAP S/4HANA migration cockpit for new implementations
July 10, 2019 10:00 AM EST/New York

In addition to the replay from July 10th, you can now also register for the new expert-guided implementation (EGI) on

Data Migration Strategy and Tools for Greenfield Implementation of SAP S/4HANA

See the blog “The fields are green, and you’re ready to migrate your data. Get strategized” for registration details, as this would be your next step with hands-on activities during the 4 to 6 hours of training.

What is an EGI?

This is a multi-day remote session, where participants learn how to complete a defined activity with experienced SAP service engineers. It is delivered as a virtual classroom.
  • Empowering you with 1 – 2 hour web sessions each morning, where an SAP expert explains step by step configuration using training materials
  • You execute the demonstrated steps within your own project for 2- 3 hours on that same day on your SAP environment or provide cloud system
  • And you have direct access to expertise as you perform the steps
In order to participate, you must be ready to invest 2 or more hours daily (during the training week).

3 Tips You Should Know about SAP S/4HANA Migration Cockpit

ou leverage SAP S/4HANA Migration Cockpit to migrate the custom legacy business data into the new SAP Cloud ERP——SAP S/4HANA. Here I list some scenarios where you would need help on using Migration Cockpit, and some useful tips you should know about Migration Cockpit.

Scenario 1: You are using Migration Cockpit for the first time, or you are encountering different questions on different migration objects. You don’t know what channel to check with.
Tip 1: It’s strongly recommended to read the SAP Note 2538700 before having hands-on experience on Migration Cockpit. This is a collective Note which provides you with a list of SAP Notes/Knowledge base articles (KBA) related to the SAP S/4HANA Cloud Migration Cockpit content.
There are questions related to the tool:
There are also questions related to certain migration objects:
Moreover, we are also updating this Note very frequently, to ensure all those latest hot questions are included.

Scenario 2: You are preparing the customer legacy data with certain migration object template, SAP just publishes new content for the migration object templates in the new quarterly release. You want to know if there are any changes to the migration object template which you are working on.
Tip 2: Considering the new content will be published every quarter, this is a common scenario which could happen at customer projects. SAP provides the Migration Objects Template Comparison Report, which helps the customer to find out what are the new/changed/unchanged migration objects between releases. It can also help to list out the detailed changes for certain migration object from release to release.
E.g. change overview from 1902 to 1905:
You can also find out the detailed field-level changes for every migration object between releases:

Scenario 3: You are filling the data into the migration objects template which you downloaded from Migration Cockpit. You are familiar with SAP R3 ERP, but not with SAP S/4HANA. You are having difficulties to maintain the migration objects template.
Tip 3: In every migration object template, we hide some fields(SAP technical structure name, technical field name, detail description). By unhiding the fields, it can help you to add the data into the template file correctly. Especially if you are an SAP R3 consultant, you will be very familiar with these technical names.

So, these are the tips which I would like to share in this blog. Hope it can help to clarify some of the questions you have on using Migration Cockpit.