Skip to Content

The purpose of this blog is to get insights into the nitty-gritty’s of SAP MDM integration into Business objects data services (BODS)

This blog also covers what is Data quality is all about and capabilities of  Business Object data services with respect to data quality EIM 4.0

Why do we need to integrate SAP MDM with BODS?

Business object data services (BODS) can provide more cleansing and matching capabilities, e.g., standardizing and correcting names, supporting different matching algorithms (heuristic, rules based, probabilistic, deterministic, empirical, template), etc. Besides this, it provides full ETL functionality to extract data from any kind of source, transform it, and load it to any destination.

Nevertheless, SAP MDM also has ETL capabilities. It has an Import and Syndicator tools to enable to load and extract data to and from MDM using files and relational databases as a source/target.

 But BODS supports various datasources including files, XML, relational databases, applications, web services and mainframes which SAP MDM won’t. Data quality treatment for local systems is possible without MDM but when you need data quality in a global context (across heterogeneous, multiple-system landscapes, additional MDM on top of BODS is required.

But again, Well you can do duplicate check and data cleansing in BODS also but that is after creating records which may not be useful. But SAP MDM where it can validate the data / do duplicate check before creating records in MDM.

 As part of this blog we are going to cover only how SAP BusinessObjectsData Services tightly integrate with SAP MDM for better data quality & cleansing of master data

Integration SAP NetWeaver MDM and SAP BusinessObjects Data Services

There are two possible scenarios for integrating SAP NetWeaver MDM and SAP BusinessObjects DataServices:

One is the Inbound Scenario :Data Services is integrated with the MDM Import Manager and MDM Import Server

The other is Outbound Scenario :Data Services is integrated with the MDM Syndicator and MDM Syndicator Server

The above scenarios include two components design time integration and runtime integration

To explain in detail, take an example of Customer master data steps of SAP ECC system send records to BODS and to MDM for de-duplication & validation od duplicates of records and send back the single version of truth back to ECC as shown below in steps;

Step 1

Extraction: Sending Customer records from SAP ECC system into BODS using native extractor. The Business object Data service-BODS will has intelligence to validate & de duplicate the records sent by SAP ECC source system

Step 2

Once all required data are extracted the cleansing and de-duplication process starts

in Business Objects Data Services where information is enriched and verified. This is an automatic process without any user interaction. The output of this process are written into several xml-Files

 

Step3

There are two XML-Files written

· One for completely new records.

· One for existing records within MDM which are determined as duplicates

  Step 4

Both XML-Files have to be imported into MDM using different Import Maps using the MDIS as shown in above diagram.

 Step 5

After the import of both files in MDM a manual Consolidation is performed utilizing the information Provided by Business Objects. Afterwards the MDM Syndication Server syndicates the now cleansed records back to the respective.

Overview BODS Data quality
SAP Business Objects Data Quality Management helps to analyze, cleanse, and match all type of data customer, supplier, product, or material data, structured or unstructured – to ensure highly accurate and  complete information anywhere in the enterprise.

That is ;Data quality refers to the set of transforms that work together to improve the quality of your data by cleansing, enhancing, matching and consolidating data elements.

 Data quality is primarily accomplished in the software using four transforms:

• Address Cleanse. Parses, standardizes, corrects, and enhances address data.

• Data Cleanse. Parses, standardizes, corrects, and enhances customer and operational data.

• Geocoding. Uses geographic coordinates, addresses, and point-of-interest (POI) data to append

address, latitude and longitude, census, and other information to your records.

• Match. Identifies duplicate records at multiple levels within a single pass for individuals, households,or corporations within multiple tables or databases and consolidates them into a single source

Data Quality – One hub for all solutions

The Data quality management that serves different purposes;

Data quality management for

Merger & Acquisitions
Compliance reporting
Regulatory Agencies

Data quality management for BI

MDM and
Enterprise DWH
Data quality management for applications
SAP ECC/CRM

Data Quality –Cleansing Capabilities

Following are the Data quality best in class cleansing capabilities from BODS EIM solutions. They are as follows

Data Cleanse

•Parsing/Standardization

•Name

•Title

•Firm

•Phone

•E-mail

Matching

•Duplicate Identification

•Consumer Householding

•Corporate Householding

 

Geocoder

•Many countries supported

• Latitude/Longitude Append

•Population Class & census data

 Look up of Latitude/Longitude

Address Cleanse

Address validation for over 240 countries.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply