How to Implement a Metadata Management Universe using Information Steward

Transcription

1 Management Universe using Information Steward Applies to: SAP BusinessObjects Information Steward 4.0 Summary The purpose of this document is to show you how you can leverage information captured by SAP BusinessObjects Information Steward into a single BusinessObjects universe. Authors: Nicolas Cottin, David Poisson Contributors: Hemant Puranik, Abhiram Gujjewar Company: SAP Created on: 1 September 2011 Author Bios Nicolas Cottin s experience with Business Intelligence software began with Business Objects back in As a BI Architect, he has taken a leading role in the deployment of the Enterprise Information Management solutions at SAP. Today, he is part of SAP Global IT, Global Business Intelligence. David Poisson joint Business Objects in 2003 as a BI Engineer in the IT Department. Very rapidly, he initiated for his team a close collaboration with the BusinessObjects Development teams, leading to a global, official Partnership a few months later. David has driven the participation of internal IT to the Beta Programs of BusinessObjects XI until recently BI 4.0, making it the most active Early Adopter. Today, David is IT Manager, BI Innovations and supports SAP Global IT to be a thought leader for IT driven innovation and best practices, demonstrating how SAP runs SAP SAP AG 1

2 Table of Contents Overview... 3 Procedure... 3 Further limitations to be taken into account... 4 Result of this initiative to meet the customer requirements... 5 Annexe - Data model... 6 Related content... 7 Copyright SAP AG 2

3 Overview Metadata Management within Information Steward provides a comprehensive view of the BI environment by: Retrieving and centralizing metadata from a wide range of data sources, data integration technologies, and BI systems. Tracing data lineage from an end report back to its original source The standard product includes a set of default Crystal Reports embedded into the End User Interface intended for use by Operational Reporting. However, in the current version these have been designed to return the data about the BusinessObjects Enterprise systems only. To fulfill the high demand for ad-hoc reporting on the whole range of metadata captured by Information Steward, we have managed to build a universe on top of the entire metadata repository database to extract metadata information for Metapedia, BW systems, and so on and enable the user to : o Create their own custom reports. o Retrieve information from Metapedia with their custom attributes. o Get information about their BW systems to make impact and lineage analysis. o Leverage the interactive feature of Web Intelligence - Filters, Inputs controls, Create advanced reports combining the data from Metadata Management and Auditing to show the list of used / unused reports and universe objects. All of this functionality is in a central place BusinessObjects InfoView / Launch Pad. The purpose of this article is to present step by step how you would need to proceed to create such a universe. Procedure Step by step 1. Import the necessary tables from the Information Steward Metadata Repository database 1.1. In Universe Designer, import only views prefixed by MMD_ or MMRV_ such as MMD_BUSINESS_TERM, MMD_BUSINESS_CATEGORY, MMD_RELATIONSHIP, and so on. 2. Join the tables / Create the relations 2.1. Join the MMD_RELATIONSHIP view (or an alias) to the metadata object views Connect Business CATEGORY ID to the MMD_RELATIONSHIP view on the field object_id Connect Business TERM ID to MMD_RELATIONSHIP view on the field related_object_id 2.4. The relation, object -> related_object means is related to and the direction is important. In this case, it means a TERM can belong to one to many CATEGORIES. Figure 1 : Snapshot of the logical schema in the universe 2.5. Then, restrict the relation with the table_id and related_table_id fields. From the csv file located here: <MM_Installation_Folder>\MM\xml\table_id.csv you can retrieve the corresponding ID for each type of objects. In our case, we have Business TERM related table ID = 301 and Business CATEGORY table ID= Position hardcoded auto-join on table_id and related_table_id: 2011 SAP AG 3

4 2.7. Set your join as an outer join if your relation is not always true. Use outer joins with moderation, as these adversely affect performance Create a Business Object from your Metadata object views Test it in a Web Intelligence report by selecting an object from each table. For example:: SELECT MMD_BUSINESS_TERM.BUSINESS_NAME, MMD_BUSINESS_CATEGORY.BUSINESS_NAME FROM MMD_BUSINESS_CATEGORY RIGHT OUTER JOIN MMD_RELATIONSHIP ON (MMD_RELATIONSHIP.OBJECT_ID=MMD_BUSINESS_CATEGORY.DATA_GROUP_ID AND MMD_RELATIONSHIP.RELATED_TABLE_ID=301 AND MMD_RELATIONSHIP.TABLE_ID=300 ) RIGHT OUTER JOIN MMD_BUSINESS_TERM ON (MMD_BUSINESS_TERM.BUSINESS_TERM_ID=MMD_RELATIONSHIP.RELATED_OBJECT_ID AND MMD_RELATIONSHIP.RELATED_TABLE_ID=301 AND MMD_RELATIONSHIP.TABLE_ID= Repeat this procedure to complete your universe data model by adding new types of objects. Further limitations to be taken into account Recursive relations cannot be implemented. For example, for a given BW object it is not possible to repeatedly query the table containing the related transformations until you reach the record that contains the end data source SAP AG 4

5 Result of this initiative to meet the customer requirements The output of the development is a METAPEDIA-centric universe allowing the end-user to create ad-hoc reporting on METAPEDIA objects with CUSTOM ATTRIBUTES and retrieve information about the lineage of related BW objects and BOBJ objects. Here are some screenshots taken from the set of reports delivered to end users, on top of this universe: 2011 SAP AG 5

6 Annexe - Data model 2011 SAP AG 6

7 Related content SDN Information Steward page: Article How to create failed data reports as part of your data quality analysis faca?QuickLink=index&overridelayout=true 2011 SAP AG 7

8 Copyright Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Oracle Corporation. JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty SAP AG 8