Configuring the duplicate check functionality in SAP Master Data Governance for Business Partners is a multi-layered process. First, the underlying search technology must be established by creating and assigning search object connectors, which link the MDG data model to the search engine (E). Second, the logic of the duplicate check must be defined by setting low and high similarity score thresholds; these thresholds determine how the system categorizes a potential match as a duplicate, a potential duplicate for review, or a non-duplicate (A). Finally, this functionality must be integrated into the governance workflow by explicitly enabling the duplicate check for the relevant steps within the change request type configuration, making it available to the user (C).

B. Define recency and source system reliability.

This is incorrect because defining recency and source system reliability are parameters primarily used in MDG Consolidation and Mass Processing for survivorship rules, not for the standard duplicate check within a change request process.

D. Set up the sort method for the data model at entity type.

This is incorrect because the sort method is a data modeling property that defines the default ordering of entity instances (e.g., addresses) in the UI and is unrelated to the search and duplicate check configuration.

1. SAP Help Portal, SAP S/4HANA 1909, SAP Master Data Governance, Configuration of Master Data Governance. Section: Configuration of Data Quality and Search -> Set Up Search and Duplicate Check. This section details the necessity of creating search object connectors using transaction ESHCOCKPIT (Answer E) and defining search applications with low and high thresholds (Answer A). Specifically, it states, "For each search application you can define a threshold for the hit list."

2. SAP Help Portal, SAP S/4HANA 1909, SAP Master Data Governance, Configuration of Master Data Governance. Section: Process Modeling -> Change Requests -> Configure Properties of Change Request Step. This official documentation shows the configuration screen for a change request step, which includes a "Duplicate Check" indicator. Setting this indicator makes the duplicate check function available on the user interface for that specific workflow step, confirming the necessity of step C.

3. SAP Help Portal, SAP S/4HANA 1909, SAP Master Data Governance, Configuration of Master Data Governance. Section: Configuration of MDG, Consolidation and Mass Processing -> Configure Consolidation Process -> Define Validation and Derivation Rules. This documentation describes how survivorship rules can be defined based on various criteria, including source system, which is distinct from the standard duplicate check configuration (refuting B).

4. SAP Help Portal, SAP S/4HANA 1909, SAP Master Data Governance, Configuration of Master Data Governance. Section: Data Modeling -> Edit Data Model. The documentation for entity type properties explains that the "Sort Method" is used to control the sequence of records for specific entity types, confirming it is not part of the duplicate check mechanism (refuting D).