Enterprise Search Extension for SAP Master Data Governance...Enterprise Search template is generated, a relationship has to be maintained between the Object Type Code (OTC) and the

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Enterprise Search Extension for

SAP Master Data Governance

Applies to:

ERP 6 EhP 5. For more information, visit the Master Data Management homepage.

Summary

This article explains the extensibility concept for Enterprise Search in SAP Master Data Governance.

Author: Lars Rueter

Company: SAP AG

Created on: 8. June 2011

https://www.sdn.sap.com/irj/sdn/nw-mdm

Enterprise Search Extension for SAP Master Data Governance


© 2011 SAP AG 2

Table of Content

Adding New Attributes to SAP Entity Types ....................................................................................................... 3

Alternative 1: ................................................................................................................................................... 3

Alternative 2: ................................................................................................................................................... 3

Adding New Relationships between SAP Entity Types ...................................................................................... 3

Alternative 1: ................................................................................................................................................... 3

Alternative 2: ................................................................................................................................................... 3

Adding New Entity Types to SAP Data Models .................................................................................................. 4

Alternative 1: ................................................................................................................................................... 4

Alternative 2: ................................................................................................................................................... 4

Defining New Data Models ................................................................................................................................. 4

Alternative1 (Separate Enterprise Search Object Connectors for Staging & Active data areas): .................. 4

Alternative2 (Single Enterprise Search Object Connector for both Staging & Active data areas):................. 5

Related Content ................................................................................................................................................ 12

Copyright........................................................................................................................................................... 13



© 2011 SAP AG 3

Adding New Attributes to SAP Entity Types

If an entity type is added with new attributes, Enterprise Search structures for the corresponding Entities have to be regenerated (View Cluster VC_USMD004) (View Cluster VC_USMD004).

Alternative 1:

If a search connector is already created for the Enterprise Search template for the corresponding Master data object, the customer has to delete the search connector using the transaction ESH_COCKPIT. Once the search connector is deleted, navigate to Template Modeler in the ESH_COCKPIT screen and Edit the corresponding Enterprise Search template by deleting the existing node for the changed entity type and create a new node(With same name) by providing a data source with the new Structure name(In Define Nodes step).

Alternative 2:

Instead, you can create a new Enterprise Search template again by using transaction MDG_ES_TEMPL or in General Settings > Data Quality and Search >Create Search Object Connector Templates. Once the Enterprise Search template is generated, a relationship has to be maintained between the Object Type Code (OTC) and the Enterprise Search Template in General Settings > Data Quality and Search >Assign Search Object Connector Templates to Object Types.

A search connector has to be configured using ESH_COCKPIT transaction. Here, the system details on which the search has to be performed is given.

After navigating to this screen using given transaction, Search connector can be created for the corresponding Enterprise Search template. After creating Search Connector, an initial extraction of data for the connector can be set using Actions-> Schedule Indexing to fetch all the data lying in databases tables corresponding to a master data object.

Once the initial extraction of data is done, there can be changes which would have happened to existing entries. This needs to be updated to the Enterprise Search index. You can set this option on the same screen (Actions-> Schedule Indexing) by enabling the button Real-time Indexing.

Adding New Relationships between SAP Entity Types

Alternative 1:

If a search connector is already created for the Enterprise Search template for the corresponding Master data object, the customer has to delete the search connector using the transaction ESH_COCKPIT. Once the search connector is deleted, navigate to Template Modeler in the ESH_COCKPIT screen and Edit the corresponding Enterprise Search template by maintaining the new relationships (In Define Structure step).

Alternative 2:







© 2011 SAP AG 4

Adding New Entity Types to SAP Data Models

If a data model is added with new Entity types, Enterprise Search structures for the corresponding Entities have to be generated (View Cluster VC_USMD004).

Alternative 1:

If a search connector is already created for the Enterprise Search template for the corresponding Master data object, the customer has to delete the search connector using the transaction ESH_COCKPIT. Once the search connector is deleted, navigate to Template Modeler in the ESH_COCKPIT screen and Edit the corresponding Enterprise Search template by creating new nodes(with new Entity names) by providing a data source with the new Structure names(In Define Nodes step).

Alternative 2:





Defining New Data Models

If a new data model is created, Enterprise Search structures for all entities of the data model have to be generated (View Cluster VC_USMD004).

You can create a new Enterprise Search template again by using transaction MDG_ES_TEMPL or in General Settings > Data Quality and Search >Create Search Object Connector Templates. Once the Enterprise Search template is generated, a relationship has to be maintained between the Object Type Code (OTC) and the Enterprise Search Template in General Settings > Data Quality and Search >Assign Search Object Connector Templates to Object Types.




Alternative1 (Separate Enterprise Search Object Connectors for Staging & Active data areas):

In this case the master data object will already have enterprise search enabled for the active area. Since the staging area data model might be different from the active area, a separate enterprise search connector template is required for staging area which can be created as mentioned in the above steps. While searching



© 2011 SAP AG 5

the results have to be combined from both staging and active areas enterprise search connectors so that for the search UI it looks like a single set of results. For this during the call to search, a BAdI will be provided - BADI_SDQ_PP_SEARCH. The implementing team will have to provide active area results using the BAdI method- SEARCH_PP().

Alternative2 (Single Enterprise Search Object Connector for both Staging & Active data areas):

In this case there is only one enterprise search template maintained for both the staging area and active area. Hence only one index is maintained for both areas. Here, in order to fetch data from active area, a BAdI will be provided - BADI_SDQ_PP_DATA_EXTRACTOR_ES. The implementing team will have to provide active area records during initial extraction and delta extraction by using the methods - INITIAL_DATA_LOAD() and DELTA_DATA_LOAD().

Note: If application follows two template approach like Material(One for PP and One for Staging), mapping between new customer fields and PP fields needs to be taken care by Search BAdI (Implemented by applications).



© 2011 SAP AG 6



© 2011 SAP AG 7



© 2011 SAP AG 8



© 2011 SAP AG 9



© 2011 SAP AG 10



© 2011 SAP AG 11



© 2011 SAP AG 12

Related Content

For more information, visit the Master Data Management homepage

https://www.sdn.sap.com/irj/sdn/nw-mdm



© 2011 SAP AG 13

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 Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., 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.

Documents

Enterprise Search Extension for SAP Master Data Governance...Enterprise Search template is generated, a relationship has to be maintained between the Object Type Code (OTC) and the