Show TOC

Background documentationSet Up Search

 

MDG offers several options to search for the data in change requests including the active and inactive data. The search options are distinguished by their capabilities and their landscape requirements. The main difference is in their capability to include classification data in the search. These are the following options:

  • SAP search engine-based search (TREX search) offers full search capabilities.

  • As of Master Data Governance 7.0 SP2, Feature Pack you can use SAP HANA-based search to connect the MDG database to an SAP HANA-based system for search. See Configuring SAP HANA-Based Search for MDG for more detail.

In MDG for material the default search provider is the SAP search engine based on TREX. If you want to configure the system for SAP HANA-based search, follow the instructions in the section SAP HANA-Based Search.

TREX-Based Search

For TREX-based search are two search options available:

  • Embedded Search (included in SAP NetWeaver on a local system)

  • SAP NetWeaver Enterprise Search (run centrally)

Embedded Search is limited to indexing and searching within a single SAP system (single SAPSID). In production scenarios with heavy data load it is mandatory to install a separate TREX instance that is used exclusively by Embedded Search for performance and sizing reasons. For installation information for TREX 7.1 see SAP note 1249465Information published on SAP site.

Embedded Search

If you want to use Embedded Search, run the following activity in Customizing for SAP NetWeaver under Start of the navigation path Search and Operational Analytics Next navigation step Embedded Search End of the navigation path.

If you are not familiar with TREX or TREX is not yet activated, proceed as follows to make the basic settings:

  1. Connect to the TREX installation.

    During TREX installation, you created an RFC-destination for the TREX. Run transaction SM59 in the TCP/IP connections section to verify that it exists and can be linked. Link the ABAP system to this TREX destination.

    For more information, see Customizing for SAP NetWeaver under Start of the navigation path Search and Operational Analytics Next navigation step SAP NetWeaver Enterprise Search Next navigation step TREX Next navigation step Set TREX Destination End of the navigation path.

    Alternatively, you can run report ESH_ADM_SET_TREX_DESTINATION.

  2. Create and index the connectors.

    SAP delivers the following two standard templates for MDG for material. You need to activate these templates and prepare them for indexing.

    • Material (MATERIAL) – for the active data residing on the standard tables MA* and related objects

    • Material Template for MDG (MDG_MATERIAL) – for the inactive material data linked to the MDG change requests

    Open the Connector Administration Cockpit in Customizing for SAP NetWeaver under Start of the navigation path Search and Operational Analytics Next navigation step SAP NetWeaver Enterprise Search Next navigation step Modeling, Administration, and Monitoring Next navigation step Open Administration Cockpit End of the navigation path. Alternatively, you can run the transaction ESH_COCKPIT. Make the following settings:

    1. To open the Modeler, select the Modeler link.

    2. In the Software Components menu choose Maintain Software Components and choose Create. Enter the name for the new software component and assign a package. Choose Create. Enter a description for the new software component and choose Save. Select a workbench request.

      Note Note

      The new software component is necessary to get all extensions of the template MATERIAL, which are made in the included software component. When creating the search connector for MATERIAL and you have installed both, the MDG_APPL software component and the PLMWUI software component, you have to decide in which software component the MATERIAL connector is created. This is because both, MDG_APPL and PLMWUI are parent software components of SAP_APPL. Both the MDG_MATERIAL template and the MATERIAL template are used in the MDG applications (which are related to the software component MDG_APPL). This requires that the related connectors are created in the software component MDG_APPL. However, applications related to the software component PLMWUI require, that the MATERIAL connector is created in the software component PLMWUI. However, as described above, each connector can only be created in one software component.

      To overcome this situation, you have to create a super component of MDG_APPL and PLMWUI. If you now create the MATERIAL or the MDG_MATERIAL connector, they are assigned to this new top level component. Related search templates can be used in all underlying software components.

      End of the note.
    3. Mark your new software component and choose in the Software Component menu select Include Software Components. Include the component MDG_APPL. Choose Save and select Workbench Transport. Repeat this process for the highest software component for the connector MATERIAL. For example, if the software layer hierarchy is PLMWUI > EA-APPL > SAP-APPL use the software component PLMWUI but if the software layer hierarchy is EA-APPL > SAP-APPL then use the software component EA-APPL.

    4. Go back to the Administration Cockpit and select Create. Select the new software component and search for the template MATERIAL. Once you have located the template, create the connector for the Enterprise Search. Create the connector using the MATERIAL template first and wait for the job to complete before creating the connector using the MDG_MATERIAL template.

    5. The two connectors Material and Material Template for MDG are now visible with the status preparing and or prepared. Select the Material connector and from the Actions menu select Schedule Indexing. On the new screen choose Show Input Form. Next, choose the option for immediate indexing and the recurrence period. You can also activate real-time indexing if the sizing, parameters, and performance of the system allow for this. Select all object types and choose Copy Settings. This copies the default settings from the input form to all object types. The status of the connector is changed to Indexing.

    6. Ensure authorization indexing. Enterprise Search requires its own authorizations. Authorizations for all MDG users must be indexed on the Enterprise Search system. The system writes every new or changed user as an entry into the table ESH_AU_USR_UPD that contains the user IDs that have been changed since the last indexing of the technical object type USER_AUTHORITY.

      The object type USER_AUTHORITY and other object types which do not support real-time indexing need to be regularly scheduled for indexing on the Enterprise Search system. The object type USER_AUTHORITY can be found in the connector Material or the connector MDG_MATERIAL. You cannot enable real-time indexing for USER_AUTHORITY.

    Once indexing is complete the two connectors should have the status Active.

  3. Use the report ESH_TEST_SEARCH to verify the search function. In the Search Scope section, enter a Connector ID. Next, enter Default in the Request field and execute the report.

    • The connector MATERIAL returns the active material master data.

    • The connector MDG_MATERIAL returns the inactive material master data. At least one active change request of type MAT* needs to exist with materials assigned to it, otherwise you will get a message that the search provider MDG_MATERIAL does not exist during the search and in the duplicate check of any change request where this is relevant.

For more information about TREX, see Configuration of the TREX Security Settings.

Search Engine Service

If you are running a central SAP NetWeaver Enterprise Search system and you connect other SAP NetWeaver systems with Embedded Search to the central system, follow the steps as described in Customizing for SAP NetWeaver under Start of the navigation path Search Next navigation step Search Engine Service End of the navigation path.

SAP HANA-Based Search

To implement SAP HANA-based search follow these instructions:

  1. Check, if SAP Note 2090025Information published on SAP site or MDG_APPL SP04 has been implemented.

  2. Enter transaction MDGIMG and navigate to Start of the navigation path Master Data Governance Next navigation step MDG, Central Processing Next navigation step General Settings Next navigation step Data Quality and Search Next navigation step Business Add-Ins Next navigation step BAdI: Search for Data in Reuse Active Area End of the navigation path.

  3. Deactivate the BAdI implementation MDG_BS_MAT_PP_SEARCH by deselecting the Active (IMG) flag.

  4. Follow the instructions in Configuring SAP HANA-Based Search for MDG.