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.
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
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.
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
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.:
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.
For migration of Masters and Transactions
To integrate AP Transactions with S/4 HANA
To move Historical Data from EBS and Current data from S/4HANA to SAP BW
dataZap - Pre-Configured Templates & Migration Engine to Extract, Transform, Pre-Validate, Load, Reconcile & Report.