Historical Data Migration During a Digital Transformation

Industry:
Automobile

Client Overview

A globally renowned automobile giant. They are one of the most recognizable names, renowned for their emphasis on continuous improvement. They employ 360000 employees globally with a production output of over 10 million units a year.

Project Scope

The scope was to migrate thirty six objects from the existing Oracle EBS system to SAP S/4HANA, with FI & SD in phase I and MM in phase II of the implementation. ChainSys was involved in migration of all Master data as well as Transactional data from Oracle EBS to SAP S/4HANA. 

This engagement was to be executed as three projects

  • Data migration from Oracle EBS to SAP S4/HANA
  • Data integration for AP payments and
  • Historical data migration into SAP BW

As per statutory requirements, one full year of historical transactions should be in one system for financial auditing purposes.  Since they went live in the middle of the financial year, historical data from EBS and current transactions from S/4 HANA into SAP BW were required to be migrated. For Audit purposes, the scope also included development of more than hundred  dashboards.


Business Situation

The mandate from the parent company was to shift from Oracle EBS to SAP S/4HANA. However Client was using all the modules of Oracle EBS and the application was heavily customized.  Client decided to implement the data migration in two phases. During phase-I, Client  decided that all payments to stakeholders, and creation of Sales Orders for automobiles spare parts would be done through SAP S/4HANA.  The Material Master related actions such as creation of new Items, new Vendors as well as Purchase Requisitions, Contracts, Purchase Orders, Goods Receipts was to continue in Oracle EBS till MM migration was completed.

This necessitated integration between Oracle EBS and SAP S/4HANA during the transition, apart from data migration in phase-I


Technical Situation

A myriad of issues cropped up as S/4HANA is a more rigid system with validations for almost all fields and character limitations which were not present in Oracle EBS.

ChainSys dataZap was used for data migration as well as data integration between Oracle EBS and SAP S/4HANA. This engagement was executed as three projects - data migration, data integration for AP payments  and migration of historical data to SAP BW.

Data migration was carried out using dataZAP as an ETL tool. With scheduled loader processes dataZap was used for integration.  There were five different types of payment transactions.:

  1. Raw Materials and Services - Local
  2. Spare Parts - Local
  3. Spare Parts - Imported 
  4. Fixed Assets - Local
  5. Fixed Assets - Imported.

For the historical data, a subset of EBS data was mapped and migrated to SAP BW and all SAP S/4 HANA was migrated to SAP BW.


Solutions

For migration of Masters and Transactions

  • Developed extractions for 30+ objects from Oracle EBS 11.5.10.
  • Created cross references to transform Source Values to Target Values
  • Configured Standard and business specific validations in the tool.
  • Six cycles of data migrations to fine tune the data migration and integrations..
  • Developed Pre-Load reconciliation reports and Post-Load reconciliation reports to get the confirmation on the data being loaded.
  • Loaded as batches and increments into SAP S/4 HANA for better performance.


To integrate AP Transactions with S/4 HANA

  • Prepared conversion mapping documents.
  • Five types of loaders to handle five  types of AP invoices
  • Made two auto scheduled programs for each Invoice type to run multiple times daily. One loader to run manually with given parameters to take care of missed Invoices.
  • During every run, AP Invoice data will be extracted from EBS, Transformed and Validated automatically.  Error records will be sent to Business thru email.  Success records will be sent to SAP.
  • Reconciliation reports with AP documents created on that day, Qualified for extraction rules, failed during pre-validation will be sent to users daily.


To move Historical Data from EBS and Current data from S/4HANA to SAP BW


  • Based on the business requirements,  prepared a data model to reproduce the existing reports (more than one hundred)  from SAP BW.
  • Moved the selected data from Oracle EBS to SAP BW as a one time activity.
  • Moved the corresponding data from SAP S/4HANA to SAP BW on regular basis

Illustrations

Benefits

  • Integration lead & lag times reduced from 12 hours to real-time
  • Each user saved about 2-3 hours a day by eliminating dual entries
  • Accelerated implementation timeline, equating to approximately 50% cost savings
  • Data reconciliation to a 6-sigma confidence level
  • Data quality increased by about 40% in the first 8 weeks.

Products and Services Used

dataZap - Pre-Configured Templates & Migration Engine to Extract, Transform, Pre-Validate, Load, Reconcile & Report.

Reference

‍


PrivacyTerms of UseAboutContact
No items found.