Kontakt

Ansicht
Dokumentation

VC_DQ_SEARCH - Define Search Applications

VC_DQ_SEARCH - Define Search Applications

ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define the search providers available for the different types of search used in Master Data Governance (MDG). The available search applications are:

  • Address Search (BAS)
  • Database Search
  • Enterprise Search
  • Remote Key Search
  • SAP HANA Search

For each search type, you have to specify which features are supported by the underlying search provider implementation, for example, fuzzy search or free text search. You can also specify if complex selections are supported for search. Complex search means that several attribute sets can be processed in one step (instead of processing them one after the other). For example, when searching for duplicates of a business partner, who has multiple addresses, all of these addresses can be processed at once.

Some of the settings you make for a search provider are used by the system to control UI elements. For example if you specify that a search provider supports free text search then an additional input field will be rendered to enter the search term.

Allocation of Search Help to Search Applications

Some search providers require the allocation of one or more search helps.

  • The search provider DB requires allocation of search helps from DDIC.
  • The search provider HA requires allocation of search views.

Allocation of Entities to Search Help

You can also allocate the data model and entity types to be considered by each search help. You should only specify a data model that is relevant to the type of search specified. For example, address search can only be used by address-linked entity such as data model BP and entity type BP_HEADER. You cannot perform address search on, for example, the material data model.

Allocation of Fuzziness to Attribute in Search Help

After you define your search mode as HA, and your data model, display the Allocation of Fuzziness to Attribute SearchHelp. You can add an Entity Type and Attribute and then specify the Fuzziness you would like for non-key fields. The fuzziness threshold ranges from greater than 0.7 to less than or equal to 1.0. The default value for fuzziness is 0.7 for non-key fields when you have not maintained an entry in the customizing table, excluding special cases. Defining a fuzziness threshold of 1.0 means that only exact matches will be returned in the search results when using the EQUAL TO operator.

You can still use the * wildcard to increase your search results to include those that contain the search term.

Allocation of Entities to Search Applications

After selecting a search application on the Define Search Application screen, you can use the Preferred Language (Pref.Lang.) column here to specify if a preferred language will be considered for the data model in question when using the search within MDG for material.

If you enable this setting: When calling up materials using the material search UI, processors can then see the material description displayed in a different language (called the ‘preferred language’) in cases where the description has not been maintained in the logon language.

If you do not enable this setting: The system displays 'Description not available' if no logon language description exists.

You define the sequence in which the preferred language is shown in Customizing for SAP NetWeaver under Search and Operational Analytics -> Enterprise Search -> Presentation of Objects -> Define Preferred Language Sequence for the Presentation of Objects.

Creation of Match Profile for Duplicate Check

You can create profiles that specify which attributes the system compares in order to identify duplicates. For example, to compare addresses, you can specify that the system should consider the house number, street, city, postcode, and country/region of each record. You can specify that a field is mandatory for duplicate check. During a duplicate check, all fields that you specify as mandatory must contain a value in order for the check to be performed. You can also assign a relative weight to each field indicating the importance of that field in identifying duplicates so that the system can prioritize certain attributes for the purposes of the comparison. For example, two addresses with identical postcodes could be considered more likely to be duplicates than two addresses in which the values for country/region are identical.

You can create one or more match profiles. At any point in time, only one match profile can be active.

You can also use the Rule Set Name field to specify the name of the rule set used for HANA-based searches and to identify duplicates. When you enter a rule set here the information from the rule set is used instead of the attribute view for duplicate checks.

For Enterprise Search or Address Search (BAS), you must have performed the corresponding systems set-up and you must have performed initial indexing.

Since search functions rely on substantial main memory allocation, for optimal search performance you should have installed TREX 7.1. or above. This is the first TREX release to support 64-bit architectures. TREX 7.1 supports Windows and LINUX only.

MDG Supplier supports the use of the BAS-DES interface for providing search for address data. This requires the installation and configuration of an additional component, for example SAP BusinessObjects Data Quality Management.

For SAP HANA Search you must have:

  • Performed the corresponding system set-up for the SAP HANA database
  • Maintained MDG landscape Information, see Master Data Governance -> General Settings -> Maintain MDG Landscape Profile.






BAL Application Log Documentation   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6716 Date: 20240523 Time: 162505     sap01-206 ( 124 ms )