Hierarchy
⤷ CA-MDG-DQ (Application Component) Data Quality
⤷ MDG_SDQ_DATA_QUALITY (Package) MDG: Data Quality
IMG Activity
ID | VC_DQ_SEARCH | Define Search Applications |
Transaction Code | S_BT6_28000045 | (empty) |
Created on | 20101111 | |
Customizing Attributes | VC_DQ_SEARCH | Customize Search |
Customizing Activity | VC_DQ_SEARCH | Customize Search |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | VC_DQ_SEARCH |
Use
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
For each search type, you can specify the types of search permitted, for example, you can allow fuzzy searches or free text searches. You can also allow or prevent complex selection for search. For example, when searching for an address, you can specify that, in a case where a business partner has multiple addresses, each of these addresses is considered in the search.
Allocation of Search Help to Search Applications
You can allocate search help to each search - defining the possible values that the system help proposes for a user to search for.
Allocation of Entity Types to Search Applications
You can also allocate the data model and entity types to be considered by each search. 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.
Creation of Match Profile for Duplicate Check
You can also 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 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 are identical.
You can create one or more match profiles.
At any point in time, only one match profile can be active.
Requirements
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.
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | VC_DQ_SEARCH | 0 | BTD0000212 | Data Quality |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VC_DQ_SEARCH | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20110110 |
SAP Release Created in | 703 |