How to do Data Migration in SAP S/4 HANA:
How to do Data Migration in SAP S/4 HANA:
A).What is the Goal of Data Migration: Main goal of a data migration project is not simply to move and transform data from one system or format to another but it is to ensure that the moved data is of high quality & is fit for use and supports the underlying business processes & operational goals of the organization.
B).What is Data Migration : The data migration is the process of transferring data between computer storage types / file formats. So it is a key consideration for any system implementation , upgrade / consolidation. The data migration is usually performed pro grammatically to achieve an automated migration and freeing up human resources from tedious tasks.
So SAP S/4 HANA helps the organizations to reduce their functioning IT costs by streamlining their IT landscapes. As the requirements of every organization may differ. So it is essential for an organization to execute an appropriate data migration strategy to speed up their drive towards SAP S/4 HANA in a profitable way and it would be a challenging task to transfer the data into SAP S/4 HANA & therefore it is required to have a verified data migration technique. Hence the organization ought to perform data evaluation in their current framework during the planning stage to make a move towards the SAP S/4 HANA and with the goal we can determine how to move , utilize & maintain data. So with the assistance of robust data management approach integrated with the planning phase, So this can possible for the companies to bring down the risk, keep administrative consistency & to increase the ROI on their migration to SAP S/4 HANA.
a).SAP S/4 HANA Migration Requirement:
- 1).Migrate data from non-SAP systems to SAP S/4 HANA and from SAP systems to SAP S/4 HANA.
- 2).Provide a comprehensive migration solution with no programming required by the customer.
- 3).Map data structures between source and target systems.
- 4).Easily integrate custom objects.
- 5).Reduces test effort.
- 6).Minimize the downtime.
- 7).Make the migration solution audible.
b).The key points to be considered at the time of DATA MIGRATION:
- 1).The standards for the data quality, data mapping & data conversion should be defined.
- 2).Recognize the key data stakeholders & their participation through the course of the data migration project.
- 3).A tool required to mechanize the execution of mapping of data, data transformation & data quality responsibilities in an organized & successive manner.
- 4).The initial data migration planning & cleaning, errands should be carried out. So the data utilized in the target system, the data uniqueness & the business procedure that it supports, quality of the transferred data which focuses on the four essential factors, i.e. comprehensiveness, consistency, compliance & conformity.
- 5).Accomplish the clear data standards & guidelines during the time of data entry in the system.
- 6).To identify the issues with the data in setting up monitoring & reporting and then taking the necessary action for data remediation.
c).Overview of ETL , BODS , BDC and LSMW:
1).ETL: Means Extract, Transform & Load: SAP HANA ETL based replication uses SAP Data Services to migrate data from SAP or non-SAP source system to target HANA database. The BODS system is an ETL tool used to extract, transform & load data from source system to target system. So it enables to read the business data at an application layer. We need to define data flows in Data Services, scheduling a replication job & defining source & target system in data store in Data Services designer.
2).BODS( Business Object Data Services ): This is an ETL tool currently acquired by SAP used for integration with all types of disparate systems, extracting data from them, transforming them into meaningful information & loading them into all types of systems. So it is tightly integrated with SAP systems & hence really a good tool to migrate data from legacy systems to SAP systems with ease & less development efforts with effective debugging and monitoring capabilities.
3).BDC( Batch Data Conversion ): It is another method of data migration in SAP, in which data is transferred using the batch input program & can be executed using a call transaction method / a session method. This helps to transfer a large amount of data entries related to the data entries from a legacy system to an SAP system, also this works by automating the process of manual data transfer. So in this method and only the data which relate to a single transaction is transferred initially with the help of a correct data format. This automatically moves all the outstanding data entries that run in various lines using the same data format. The entire process happens in the background & the data are transferred one by one as similar to the manual process. So in this method, the data is transferred from legacy system to SAP system but not from the SAP system to a legacy system. We have two methods of batch data conversion one is call transaction method & another is the batch input session method.
4).LSMW(Legacy System Migration Workbench): The LSMW is a tool that supports the transfer of data from non-SAP systems /Legacy Systems to SAP R/3 systems. So this can be a one time transfer as well as a periodic one. The LSMW also support the conversion of data of the legacy system in a numerous way.
d).SAP S/4HANA Migration Cockpit - A preconfigured migration content:
This is an innovative migration tool for SAP S/4HANA. It Initially was obtainable for cloud release only, however, now it is offered for on-premise version as well since 1610. So the migration object modeler supplement this tool which is a planned tool for improvements & modifications of already defined migration objects.
- 1).Pre-configured content & mapping for each migration object, e.g. G/L open items.
- 2).Predefined templates [Microsoft Excel XML files] for each object.
- 3).Automated mapping between template & target structure.
- 4).Migration programs are automatically generated : no programming required by the customer.
- 5).Available for private & public cloud and on-premise.
e).SAP S/4HANA Migration Cockpit:
f).Migration Objects and Template for Customer / BP:
g).Migration Objects & Template for the Material:
h).Steps to create & upload the file:
- 1).Open the transaction LTMC.
- 2).Create the project.
- 3).Name your project.
- 4).Mass Transaction Id: The system will automatically populate it but it can changed if needed. So it is very important key when you transfer any data from quality system to production system and the key should be identical in both the systems if any content are getting transferred from Quality to Production systems.
- 5).Transfer Option : a).File b).Staging - It was introduced in 1709.
- 6).Data Retention time: The system will keep the upload files for the number of days which we mention here & after that system will clear the files. So for Example : If you mentioned retention time as 15 days then system will keep the upload files till 15 days & then it will be cleared.
- 7).Choose the migration object for example material and customer as per your need. The Object will be assigned to the project which you created in 1st step. So SAP provided few preconfigured objects.
- 8).Download the template & fill the data. The Data is mandatory in the workbook (tab) which is highlighted with yellow color in the template.
- 9).Upload the template which you crated.
- 10).Once the file is uploaded then click on Activate.
- 11).Click on start button to start the transfer process.
i).Configuration Step: 1
j).Configuration Step: 2
k).Configuration Step: 3
l).Configuration Step: 4
m).Configuration Step: 5
n).Configuration Step: 6
o).Configuration Step: 7
p).Configuration Step: 8
q).Execution Flow:
r).Material Created Successfully:
s).Migration Object Modeler( LTMOM ) : It is another tool which is provided in an on-premise version only. So for the description of the migration objects, this tool can be observed as a design-time tool and it has improved skills which are building up each time & depends on the SAP S/4HANA edition.
▶ 1).Migration object modeler is part of the SAP S/4HANA migration cockpit design functionality to easily integrate custom objects & enhancements Integration of newly created objects.
▶ 2).Custom objects.
▶ 3).The SAP standard object that are not yet in the scope of the SAP S/4HANA migration cockpit and customer specific enhancement [e.g..add new field] to SAP standard object delivered with the SAP S/4 HANA migration cockpit available for on premise.
▶4).To start the migration object modeler, use transaction LTMOM.
▶5).To run the necessary transaction our user need the following role: SAP_CA_DMC_MC_DEVELOPER.
t).Rules of Migration Object Modeler:
The rules can be used to change the values that are migrated from source fields to target fields. Hence the different supported rules are: field based rules, event based rules & internal rules.
1).Field-based rules: This can be used to change the value of a target field during the migration.
2).Event-based rules: The custom coding can be inserted at predefined points of processing an event [for example at Start of Loop / Start of Record].
3).Internal rules: This can be called by field-based rules or event based rules. So this allows you to separate code into different modules, which can then also be shared by other field based rules / event-based rules.
u).Additional Functionality:
v).SAP Pre Configured Options :
The SAP predefined options given: 'Not Visible', 'Visible' & 'Required'. So it can be set for any of the field as per the requirement.
w).About Source Structure:
So under Source Structures , we can adjust the source structure so that your data can be transferred to the SAP S/4HANA system.
x).About Target Structure:
So under Target Structures , we can get an overview of the target structures associated with the migration object & structures can be single fields, multiple fields / tables.
y).About Structure Mapping:
So Under Structure Mapping , we can check how the source structure is mapped to the corresponding target structure and as a prerequisite, the source structure must be mapped to a target structure before you can map the field of the source to the target structure [see Field Mapping].
Z)About Field Mapping: So under the Field Mapping, we can map the field from the source structure to field in the target structure. Then simply drag the relevant field from the right hand side to the target structure field on the left hand side. So if a field from a source structure has been mapped to a target field and the system displays a green icon & a red icon if it has not been mapped.
1).About Transaction Objects: The translation object define how value from a specific field in the source system must be translated to target value during the data migration & there are object : for example profit centers, company codes & country keys that have identifier in the source system that do not correspond to the identifier in SAP S/4 HANA. For Example: Following values from the Country field in the source system must be translated to different target values:
Germany à DE
United Kingdom à UK
America à US
So in this case, we create a translation object called Country & assign it to a field-based rule or an internal rule and assign the rule to the corresponding target field.
2).How to change the Template :
C).Updated Template: Customer
Final Conclusion: The Data migration in a SAP S/4HANA couple of imperative focuses should be considered. This is also required to realize that how we can increase the value of our SAP S/4HANA by impacting the data which is a crucial step in the digital travel. So there are different tools which are available for data migration and the usage of these tools makes the data migration process more comfortable. Hence these tools are considered as a ready to use solutions which saves a lot of time for data migration.
Hope this helps. Thank you everyone. Keep supporting and keep reading.
Comments
Post a Comment
If you have any doubts let me know