Complex Data Cleansing for a Digital Transformation from JDE, BPICS, Mapics to SAP

Automotive Global Supplier

Client Overview

Leading Global Supplier of systems and components for the Automotive industry, headquartered in USA. Products include rubber and plastic sealing, fuel and brake lines, fluid transfer hoses and anti-vibration systems, etc. Its sealing products protect interiors from noise, dust, and weather. Fluid transfer systems deliver and control fluids to fuel and brake systems and HVAC systems. The company sells to virtually every global OEM, prominent among them being Ford, GM, and Fiat Chrysler.

Key Facts:  

  • Number of employees: 32,000
  • Founded in 1936
  • Operations in more than 20 counties, 100+ manufacturing locations
  • Environment: SAP ECC 6.0, JDE, BPCS, MAPICS
  • Revenue: $3.11 billion

Project Scope

  • Data migration from SAP ECC 6.0, JDE, BPCS, MAPICS to SAP S/4HANA
  • Data quality improvement across enterprise systems
  • Master data management

Business Situation

As a result of several acquisitions, this automobile spare parts manufacturer has 40+ manufacturing locations running with different ERP systems and legacy systems such as JDE, BPCS and MAPICS, etc. Business wanted to migrate all the Master data from the non- SAP and non-ERP legacy applications to SAP ECC. As a result, the business team decided to cleanse, dedupe and standardize the master data before migrating them to SAP ECC.

Technical Situation

Since the manufacturer acquired the companies with different ERP applications and non-ERP applications, they ended up having inconsistent master data across the organization. They wanted to migrate everything to SAP ECC, but the legacy system data structures were completely different from SAP systems. Legacy (non- SAP / non-ERP) systems did not have all the critical information that are needed in SAP systems, and so it involved a lot of data enrichment. Address data was not properly maintained for the Customer and Vendor Master data and it required address standardization. Also, there was a need for de-duplication since several Customers and Vendors are maintained with the same address.


The solution proposed was dataZen (a cloud-based MDM solution) that runs on the ChainSys Smart Data Platform. dataZen comes with prebuilt templates thereby reducing the effort and time involved in implementation. And this also enables the usage of Agile methodology wherein the Business users can participate in the validation of the results very quickly.

dataZen is based on Web-service based architecture and is fully configurable to suit business needs. dataZen handled address standardization, identification of duplicates and auto merging business rules flawless.

ChainSys resources were familiar with most major ERP products and solutions. This enabled them to operate independent, thereby reducing the load on the IT team and the Business users.



The "Get Clean" process helped data migration to go successful, since clean golden records were available long before the data loading.

Data standardization part of dataZen used D&B (Dun & Bradstreet) web services to standardize the Customer and Vendor master address data.

Data Enrichment/Construction was done for the missing critical fields coming from the legacy applications.

Duplication check was performed, and the results were shared with the business. Duplicate master records were eliminated or merged (before migration) after business review and approval.

Products and Services Used

dataZen - To 'Get Clean' and 'Stay Clean', and Introduce Master Data Governance.


No items found.