Upload Canceled Migration Template Does Not Correspond to Active View
Together with a revamped business suite you lot can expect revamped data migration tooling. We are used to piece of work with LSMW for years equally the legacy data migration tool for new implementations and migrations. LSMW is notwithstanding an available tool in S/4HANA, only working with LSMW can be a cumbersome process, this is also the reason why a lot of third party solutions (based on LSMW) are created and sold to make life easier. At present we have new tools available, can nosotros completely forget the former fashioned LSMW?
Changes in data migration
Together with the innovations related to data models, user interfaces, etc. in S/4HANA, SAP has revised the way nosotros load data into SAP.
The reason to come up up with a modern and easy to employ migration tool is to simplify and fulfill the following challenges and requirements:
- Migrate data from SAP/non-SAP systems to S/4HANA
- Provide a data migration solution without programming requirement
- Incorporate custom objects in an easy way
- Mapping data between source and target organisation
- Reduce attempt and minimize downtime
Earlier going into detailed explanations, I will provide yous the list of available tools for data migration in S/4HANA. Likewise the two new tools, we all the same have LSMW and RDM:
- LSMW
- Migration Cockpit (MC)
- Migration Object Modeler (MOM)
- Rapid Data Migration (RDM) with Data Services
Are you interested in the dissimilar migration tools in S/4HANA and various possible transition scenarios? Would yous like to know more than about the availability of LSMW and have detailed explanations on the Migration Cockpit and Migration Object Modeler? Are you wondering why yous still demand the more avant-garde Rapid Data Migration tool and what this tool is all about? After having gained insights in these tools, you probably also want to have a prissy overview of when to use which tool? Then continue reading this blog.
What are the different transition scenarios?
In of my previous blogposts I explained the possible transition scenarios to S/4HANA. You can read the total post here, but I will give a quick refresh here since the transition scenarios are related to the option for a migration tool.
Due south/4HANA Deployment Options
New Implementation
This approach is also known as the greenfield implementation. For this approach the bachelor data migration tools will exist discussed further in this blogpost. The elapsing and complexity of the projection depends on the number of required data migration objects and the volume per data migration object.
Organization Conversion
From a technical point of view, a system conversion is a complete conversion of an existing SAP ERP system to SAP S/4HANA. So, an existing SAP ERP system is converted to S/4HANA together with the database tables, data models and application code.
Landscape transformation:
the landscape transformation scenario requires currently a service or consulting engagement with SAP. There is not mostly released toolset with documentation available which you can use to configure, test und execute your ain, individual data migration to the SAP S/4HANA platform. The currently available tools and technology are only bachelor via SAP Value Assurance Services or Consulting Service Engagements.
Availability of LSMW
Every bit mentioned before, LSMW is available within S/4HANA On-Premise, merely not considered by SAP as the migration tool going forward. When using LSMW in a South/4HANA surround all object should be checked and tested carefully. Especially for objects which are subject to change, like GL account / Price Elements.
According to SAP, LSMW is not recommended for data load into S/4HANA and can be used at customer's own take chances.
The S/4HANA Migration Cockpit
The Migration Cockpit is the new migration tool for S/4HANA. It is available for on premise as from version 1610 and it is the just migration tool for Cloud deployments. It is a tool for the initial upload of information only and not all LSMW functionalities are covered. The number of supported objects are growing with each new release, just non all objects are available currently.
In the beneath two tables you can find the bachelor object in the S/4HANA 1610 and 1709 releases.
Available objects in S/4HANA 1610:
Migration cockpit available object S4HANA 1610 (32)
Bachelor objects in S/4HANA 1709:
Migration cockpit available object S4HANA 1709 (52)
Available objects in S/4HANA 1809:
How does the Migration Cockpit work?
The Migration Cockpit features a single bespeak of entry where, via guided procedures, data selection, data transformation and monitoring tin can be performed. It provided logs and documentation to aid the user during the process.
To my opinion the about convenient part is the fact that there are predefined Excel templates for each object and SAP is taking care of the source and target structure mapping automatically.
Let's encounter how this works…
Migration Project
The transaction code for the Migration Cockpit is LTMC. In the Migration Cockpit I have created a Test projection. From the test project I can navigate to the available Migration Object:
Create Migration Project in Cockpit
Download Template
I have selected the Migration of Vendors object. As you tin run into the organisation also shows the dependent object, in this case the migration of banks. From this page I can download the Excel template. The Excel file can be saved locally, and you tin outset filling in data. The Excel templates are in XML format.
Migration Cockpit Migration Object Vendors with Excel template
Upload File
After you take prepared the file, and all mandatory fields are filled, the file can be uploaded in the Migration Cockpit.
Migration Cockpit Migration Object Vendors Upload file
Actuate, start transfer and validate data
The uploaded source file is now ready. Afterward selecting the correct file, it should be activated first and and so we can start the transfer.
Migration Cockpit Migration Object Vendors Beginning Transfer
Convert Values
In this pace the field mapping will be done. If a value is constitute for the first time, you need to ostend the value.
Migration Cockpit Migration Object Vendors Convert Values
Simulation and import
Now you can click on simulation and import.
Migration Cockpit Migration Object Vendors Execute import
The import is finished and the vendor is created.
Migration Cockpit Migration Object Vendors Created
Troubleshooting
All actions in the Migration Cockpit are performed as a groundwork task (SM37). To empathize the import process and for troubleshooting in case of errors it is good to empathize how the BAPI behind the Cockpit works. The BAPI used for the information import can exist constitute in transaction LTMOM. In the BAPI yous can too see how the source and target fields ere mapped.
What near objects not supported by the Migration Cockpit?
For On-Premise and private cloud deployments it is possible to raise the pre-defined migration objects with the Migration Object Modeler (MoM). The MoM is designed to integrated custom objects (east.m. add new fields) and to create SAP standard object which are currently non in scope of the Migration Cockpit.
Standard object can exist hands enhancement in the Migration Object Modeler with the following steps:
- Select the advisable project/object
- Edit source structure
- Change field mapping
- Download new template
Let'due south see how we tin can enhance the previous used vendor principal data object in the Migration Object Modeler:
Transaction LTMOM and select the project/migration object
Select the specific Migration Object in your project in which yous want to brand enhancement.
Migration Object Modeler Select Object
Editing Source Construction
Here yous can find all the fields which are shown in the Excel template. From here additional fields tin can be added.
Migration Object Modeler Change Source Structure
Select the tab in which you would like to make an enhancement. As you can meet, all fields in a specific tab in the Excel file are grouped together in the hierarchy. I will add a field in the Purchase Organization Data. Select the construction and switch to change style:
Migration Object Modeler Change Source Structure 2
Every bit you can see, the template default fields cannot be inverse. I add my enhancement in the showtime free field.
Migration Object Modeler change field mapping
Migration Object Modeler Calculation Field to construction
Change Field Mapping
After we have added the enhanced field in the source structure, the field mapping must be maintained. Find your field in both left and right-hand sides of the screen. Drag and drib the file grade the correct side (target structure) to the left side of the screen. Y'all will meet that the new field will go active.
Migration Object Modeler alter field mapping
Download the new template file
Later on the Migration Object enhancement, we can download the new Excel template from the Migration Cockpit. The template will include the new added field.
Migration Object Modeler Download new Excel template
Rapid Information Migration with Information Services
After you have seen the Migration Cockpit and the Migration Object Modeler you may wonder why you lot still need Data Services. SAP Rapid Data Migration is a tool which must exist installed on your system separately.
SAP Data Services provides capabilities for data extraction, transformation, and load (ETL), as well as information 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 Information Services license. The Rapid Data Migration packet also contains sample migration content in the form of e.g. business partners, materials, sales document etc.
In the adjacent affiliate I share an overview of all the available migration objects in Rapid Information Migration. You will see that the delta with the latest version of Due south/4HANA (1709) is not huge. The added value of Rapid Data Migration is not the college number of available standard migration objects, merely the ETL and Data Quality capabilities together with the SAP Best Do Migration Content.
The SAP Best Practiced Migration Content is non only available for Due south/4HANA, but besides for other SAP solutions listed below. These packages tin be downloaded for complimentary with your S-user.
- SAP Business Suite on HANA
- SAP ERP (incl. Retail and HCM)
- SAP CRM
- SAP Billing for Utilities
- SAP SuccessFactors Employee Cardinal
- SAP Hybris Cloud for Customer
For more than information, you can visit the below SAP sites.
http://service.sap.com/public/rds-datamigration
http://service.sap.com/bp-datamigration
Procedure overview
In the next picture a high-level overview is given in 6 steps nigh the architecture and process of the Rapid Data Migration Solution.
Rapid Data Migration Architectur
- 1. Source and Target arrangement
- On the left side the system is integrated with 1 or more SAP or not-SAP legacy systems via different interfaces (flat file, information base, etc.)
- On the right side the S/4HANA system is connected.
- ii. Extraction and profiling
- This is the staging surface area between the source and target system. The area is provided by the database on which SAP Data Services runs.
- In this stride the information is extracted and analyzed (profiled)
- iii. Cleansing, Conversion, validation and loading
- In this footstep the cleansing of data records is done. You ensure that the information comply to certain rules and the customizing settings in the Southward/4HANA system. Information cleansing can include e.1000. dividing fields, merging field and converting values to certain formats.
- The cleansed and verified data is then imported to S/4HANA
- four. Customizing extraction from SAP South/4HANA
- The customizing settings in the S/4HANA system are extracted and replicated to the intermediate layer so you tin ensure that the data is compatible with these specific customizing settings (e.g. plants, cloth types, customer groups, etc.).
- v. Data Reconciliation
- The actual imported data to South/4HANA is reconciled with the expected data for the Data Services migration.
- 6. Dashboard and Reporting
- The entire migration process can be tracked and traced with dashboards and reports. The pre-defined reports are delivered in the SAP BusinessObject BI WebIntelligence tool. The reports tin can be used as is or tin can be used as a template to create own reports.
Available object in the Rapid Data Migration tool
Beneath you can find the list of all available migration objects in Rapid Data Migration. I have added an extra column to make an easy comparison between the available object in the Migration Cockpit in S/4HANA version 1709. Column "MC 1709" indicates the availability of the object in the Migration Cockpit for version 1709.
Rapid Data Migration bachelor object (65)
When to employ What?
You now should have a practiced overview of the different information migration tools bachelor today for existing arrangement and for S/4HANA. It tin exist difficult to choose the right tool, there is no general recommendation because multiple tools tin can be used in parallel and the choice of tool depends highly on your deployment model and information quality requirements.
To below overview volition help y'all to choose the tool for your situation.
S4HANA Migration When to Utilize What
Final words
If yous're familiar with LSMW, y'all can clearly see that the Migration Cockpit and the Migration Object Modeler will brand lives easier. It is a prepare to use solution which volition reduce migration fourth dimension. The solution is not perfect and still needs some enhancements, but SAP has announced that these set of tools are the characteristic solutions for data migration in S/4HANA.
The number of migration objects are growing with each release, and when nosotros accept a await at the planned functionalities and enhancement it is quite promising.
- Straight access via RFC (instead of file upload)
- Staging area between source and target system
- Data Quality (cleansing, checks, etc.)
- Analysis (In SAP source system)
- Automated validation (of migration results)
Update 08-2019
S/4HANA 1809: I added a table with the migration object added in release 1809. Proficient news is that GL accounts are at present part of the standard object list.
Related
Source: https://s4hanablog.com/2017/11/17/data-migration-in-s4hana-revamped/