Show TOC

Process documentationConfiguring Drill-Down Search (Optional)

 

The Drill-Down Search UI is used to search master data records, starting with a general category, and moving down through the hierarchy of fields to the required information. This document contains the information required to configure this UI.

Prerequisites

Before you can begin configuring the drill-down search you must consider the following:

  • SAP HANA Configuration

    You have completed configuration of SAP HANA search for MDG and configuration of data replication for your SAP HANA database. See Configuring SAP HANA-Based Search for MDG for more details.

  • Deployment Scenario and Component Installation

    You have decided on a deployment scenario and installed the required components. There are two deployment options for installing SAP NetWeaver Gateway:

    • Single system deployment or embedded deployment where the back end system and Gateway hub are installed on the same system.

    • Dual system deployment or central hub deployment where the back end system and the Gateway hub are deployed on two different systems.

    SAP recommends the dual system deployment scenario, where the back end system and Gateway hub are deployed on different systems. Depending on the deployment scenario and SAP NetWeaver release, the following Gateway components need to be installed:

    SAP NetWeaver Release

    Deployment Option

    Gateway Component Installed

    NW731

    Single system

    In SAP GW SP06, IW_FND250, IW_BEP200 and GW_CORE200 on same system.

    NW731

    Dual system

    In SAP GW SP06, IW_BEP200 on back end system, and IW_FND250 and GW_CORE200 on Gateway hub system.

    NW740

    Single system or dual system

    No need to install as all the above Gateway components come as part of bundle under the component SAP_GWFND.

    For SAP NetWeaver release NW731, UI5 SP04 has to be installed regardless of the deployment scenario. For SAP NetWeaver release NW740 and above, UI5 is part of the bundle. For a full range of features it is recommended that you install SAP UI5 1.15.0 or higher.

  • Browser Support

    You have chosen a browser and version that is supported. See SAP Note 1716423 for details on supported browsers.

  • Attributes with Technical Keys

    If a database view contains attributes with technical keys (such as Country Keys or Region Codes) then your query results will display these technical keys. To avoid this, manually modify your generated SAP HANA views in SAP HANA Studio by adding text joins to the corresponding text tables. This causes the text description to display correctly in the browser panes and result set.

  • Update Annotation Namespaces for SAP NetWeaver Gateway Server

    Update the SAP namespace in table /IWFND/I_MED_ANS by implementing SAP Note 1885373Information published on SAP site.

Process

Follow the steps below to configure the drill-down search for SAP Master Data Governance:

  1. Create an External Alias

    1. Run transaction SICF.

    2. Create an external alias called /sap/mdg for the URL http://gatewayserver:port/sap/opu/OData/Information published on non-SAP site.

    3. In the URL, insert your own port and Gateway server names where it says gatewayserver and port. This enables the system to interpret your URL correctly.

  2. Activate the Gateway System

    Open the SAP Gateway hub system. In the SAP Customizing Implementation Guide navigate to Start of the navigation path SAP NetWeaver Next navigation step Gateway Next navigation step OData Channel Next navigation step Configuration Next navigation step Activate or Deactivate SAP NetWeaver Gateway End of the navigation path. Activate the SAP NetWeaver Gateway.

    In the dual-system deployment scenario, the web dispatcher has to be configured. For more details, see Configure Web Dispatcher below.

  3. Maintain System Alias

    In the gateway hub, maintain the system alias in customizing under Start of the navigation path SAP NetWeaver Next navigation step Gateway Next navigation step ODATA channel Next navigation step Configuration Next navigation step Connection Settings Next navigation step SAP NetWeaver Gateway to SAP System Next navigation step Manage SAP system Aliases End of the navigation path. If the development system and Gateway hub are on two different systems maintain the system alias name and the RFC destination to the development system.

  4. Activate and maintain MDG OData services

    1. Open the SAP NetWeaver Gateway hub system.

    2. Under customizing navigate to Start of the navigation path SAP NetWeaver Next navigation step Gateway Next navigation step OData Channel Development with IW_BEP Next navigation step Registration Next navigation step Activate and Maintain Services End of the navigation path.

    3. Choose the +Service button.

    4. Enter the system alias you have maintained above and choose Enter.

    5. Select the service mdg_drill_down_utility. A pop-up opens.

    6. Enter the ABAP package name where you want to save the OData service and choose Continue.

    7. Open the Activate and Maintain Services screen again.

    8. Select the mdg_drill_down_utility service and test that the service is working by choosing Call Browser. The service should be a HTTPS service.

  5. Maintain SAP HANA View Name

    Run transaction MDGIMG and navigate to Start of the navigation path General Settings Next navigation step Data Quality and Search Next navigation step Search and Duplicate Check Next navigation step Define Drill Down Search Configuration End of the navigation path. In this activity maintain the technical name and SAP HANA view name. The SAP HANA view name can be any attribute view created in the SAP HANA system or a search view generated in the MDG system. The SAP HANA view name is a concatenation of the package name and the search view name separated by a forward slash. For example, if the package name is hana1 and the search view name or attribute view name is supplier, the SAP HANA view name would be hana1/supplier.

    Note Note

    Make sure that the configuration to create search views is complete before creating a search view. To configure search view creation see Configuring SAP HANA-Based Search for MDG.

    End of the note.

  6. Maintain Search Attributes

    Run transaction MDGIMG and navigate to Start of the navigation path General Settings Next navigation step Data Quality and Search Next navigation step Search and Duplicate Check Next navigation step Define Drill Down Search Configuration End of the navigation path. Select the HANA view maintained in the above step, double-click on Attribute in the left pane, and maintain the following search attributes:

    • The user description maintained in customizing.

    • The description from SAP HANA repository.

    • The data element description.

    • The default description from the SAP HANA repository.

    • The attribute name is shown as the description.

    If the attribute is a calculated attribute the description displayed on the UI is taken from one of the following fields. If the system does not find data in the first field, it takes the next one on the list and so on.

    The description of the attribute, which is shown in the drill down search UI, is dependent on if it is a normal attribute or a calculated attribute.

    For a normal attribute the description displayed on the UI is taken from one of the following fields. If the system does not find data in the first field, it takes the next one on the list and so on.

    • User descriptions maintained in customizing.

    • Descriptions from SAP HANA repository.

    • Default description from the SAP HANA repository.

    • Attribute name itself is shown as the description.

    If the attribute has the child attribute or hierarchy attribute, maintain it in respective column. For example, the attribute region can be the child of attribute country, and the attribute city can be the child of attribute region. You can maintain up to four levels of hierarchy.

    Select the flag Root if the maintained attribute has to be part of root attribute on the UI.

    Select the flag Result if the maintained attribute has to be part of the result list attribute on the UI.

    Maintain the Authorization Object if the authorization has to be applied on certain attributes in the Object column.

    In the column Authorization Fieldname maintain the field name which is present in the authorization object.

  7. Create Search Template Class

    Copy the template class CL_MDG_GW_DDS_MODEL_TEMPLATE, then go to the constructor of the copied class (at line 7) and change the technical name in the constructor to the technical name of the SAP HANA view that you maintained in the customizing in the step Maintain HANA View Name.

  8. Maintain OData Model

    In customizing, navigate to Start of the navigation path SAP NetWeaver Next navigation step Gateway Service Enablement Next navigation step Backend OData Channel Next navigation step Service Development for Backend OData Channel Next navigation step Maintain Models End of the navigation path. In this activity, create the OData model by using the search template class created above.

  9. Maintain OData Service

    1. In customizing, navigate to Start of the navigation path SAP NetWeaver Next navigation step Gateway Service Enablement Next navigation step Backend OData Channel Next navigation step Service Development for Backend OData Channel Next navigation step Maintain Services End of the navigation path.

    2. Create the OData service using the data provider name CL_MDG_GW_DDS_DATA_PROVIDER. Example OData service name: ZMDG_CUSTOMER_SERVICE.

    3. Save the service.

    4. Assign the OData model created above by choosing the Assign Model button in the Maintain Service screen.

  10. Generate OData service in Gateway Hub

    1. In customizing, navigate to Start of the navigation path SAP NetWeaver Next navigation step Gateway Next navigation step OData channel Next navigation step Administration Next navigation step General Settings Next navigation step Activate and Maintain Services End of the navigation path or run transaction /iwfnd/maint_service. The Service Catalog screen opens.

    2. Choose the Add Service button.

    3. In the Add Service screen, enter the system alias created in the first step above and press Enter.

    4. A list of OData services is displayed. Identify the service you created above and select it. In the pop up, enter the package name and choose Continue.

    5. Open the Service Catalog screen, select the service that you have just added, then in the ICF NODES section choose Call Browser to check if the browser is opened with the collection details.

    6. Close the browser.

  11. Configure Web Dispatcher (Optional)

    The Web Dispatcher is required when the OData service and the UI are on two different servers in the dual system deployment scenario. The Web Dispatcher is located between web client (browser) and the SAP backend system that is running the web application. Depending on the URL prefixes the Web Dispatcher forwards the request either to the Gateway system (providing the business data from the database) or to the SAP system (providing the UI data).

    All OData requests for business data are served by the gateway system and the UI may be located on a different server. In this case the client needs to access both the servers, one for the UI and another for the data; so the web dispatcher needs to be configured.

    Example Example

    Using the example service name from the Maintain OData Service section above, ZMDG_CUSTOMER_SERVICE, the URL http://sapexampleurl/ZMDG_CUSTOMER_SERVICE with an external alias becomes /sap/mdg/sap/ZMDG_CUSTOMER_SERVICE/.

    End of the example.

    The web dispatcher must be configured so that if it is given the alias /sap/mdg, it routes to the Gateway system, and in all other cases routes to the SAP backend system. When setting up the UI, change the port number in the application URL to the port number of the Web Dispatcher.

    For more details on Web Dispatcher configuration go to http://help.sap.comInformation published on SAP site and navigate to Start of the navigation path SAP NetWeaver Next navigation step SAP NetWeaver Platform Next navigation step SAP NetWeaver 7.3 (or higher) Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step Application Server Next navigation step Application Server Infrastructure Next navigation step SAP Web Dispatcher End of the navigation path.

  12. Prepare Drill Down Search for Launch

    You have two choices for launching the Drill Down Search UI: you can either choose to link it to a PFCG role or set it up to launch from the Favorites menu. To set up the Drill Down Search UI to launch from the Favorites menu follow this procedure:

    1. Go to Start of the navigation path Favorites Next navigation step Add Other Objects Next navigation step BSP Application End of the navigation path.

    2. In the BSP Applicat. field enter MDG_DRILL_DOWN.

    3. In the Description field enter a description of your choice.

    4. In the Start Page field choose WebContent/index.html from the context menu.

    5. In the Name field enter service_name.

    6. In the Value field enter the external OData service name that you created above.

    Note Note

    If your Gateway system runs separately to your back-end system, and if you choose to run the drill-down search from the classic UI then you will need to manually adjust the port number in the URL to the Web Dispatcher port number each time you execute the application.

    End of the note.

More Information

More information about the SAP HANA Appliance Software can be found here: http://help.sap.com/hana_appliance/#section3Information published on SAP site.