SAP Master Data Management (MDM) is used by customers predominantly to carrying out CRUD operations on master data objects such as Products, Vendors, Customers, Employees, and Catalogues etc. The master data residing in the central MDM system is then harmonised with target systems. The master data attributes and rich content held in MDM can also be used by customers for different purposes;
- Reporting requirements
- Planning and forecasting
- Analytics within Data Warehouses and Data Marts
- Data profiling
For such needs, retrieving MDM data using DB Views is a more reliable option, when compared with other options (e.g. using syndicated files). This blog looks at DB Views in some detail, and gives an example on how DB Views can be integrated with data quality and data profiling tools. DB Views DB Views are generated database views that are saved as database queries (SQL Views) and which represent MDM data in the same manner as displayed in MDM Data Manager Tool. The difference being – that MDM data can only be read/retrieved using DB Views but cannot be modified or created. From MDM 7.1, SP10 onwards, DB Views can be generated (for supported databases) using CLIX commands. DB Views example: Integration with SAP Data Services: The following example shows how MDM data can be integrated with external data quality tools using generated DB Views. Firstly DB Views are generated for the required MDM repositories. Each DB View is named according to a fixed naming convention. Once successfully created, all DB Views can be seen as an external metadata in SAP BusinessObjects Data Services (DS). The required Views are imported in to the DS repository. The data is then pulled into DS using batch jobs and can then be validated and transformed as per requirement. When the batch job is executed, the data pulled via DB Views is always latest data from MDM. We are not then reliant on syndication or any other file transfer mechanism to bring the data into Data Services. Snapshot of DS Data flow
The transformed data out is then profiled and used for reporting and further analysis. Note that the availability of data from MDM system is independent of MDM repository being online. Hence the data can also be accessed when the repository is down. Below diagram shows an example of DB Views’ usage.
- Makes monitoring quality of master data more straightforward
- Reporting is more accurate as it is based on the latest data.
- No file transfer required, and therefore with no syndication avoiding any locking of the MDM repository during syndication.
- No dependency on the MDM repository to be online.
- Indirectly, DB Views help to make MDM processes more efficient.
For more information about our Best Practice Deployment for SAP Master Data Management, SAP Business Objects & Information Steward offering, please contact email@example.com Find out more about our services in Enterprise Information Management here