The Filter and Remove (FAR) adapter in SAP Master Data Governance (MDG) Consolidation is a versatile process step used to filter records based on specific criteria and move them to a different, subsequent consolidation process. Its placement within the process template is flexible. It can be configured as a successor to several key steps to handle exceptions or processed records. For example, after validation, it can divert erroneous records; after matching, it can separate records from open match groups for manual review; and after best record calculation, it can move the now-processed source records out of the main flow.

B. Matching process step can be configured as successor to the FAR process step to delete duplicate records.

This sequence is logically incorrect. Matching is performed to identify duplicates, and the FAR step would typically act on the results of the matching process, not precede it.

D. Best record calculation can be configured as successor to the FAR process step to move records to a new duplicate process.

This describes a valid process sequence but misrepresents the question's focus. The question asks how to configure the FAR step, specifically what it can be a successor to, which is the pattern in the correct answers (A, C, E).

1. SAP Help Portal, SAP S/4HANA 1909, "Configuration of the Process Template": This documentation outlines the steps for configuring a consolidation process. It describes the available adapters, including the "Filter and Remove" (FAR) adapter, and provides examples of its placement. It confirms that FAR can be used after steps like Matching, Validation, and Best Record Calculation to divert records. For instance, it states, "You can use the Filter and Remove adapter to move records that failed validation to a separate process." and "You can use the Filter and Remove adapter to move records from open match groups to a separate process for manual cleansing." (Navigational Path: SAP Help Portal -> SAP S/4HANA -> 1909 -> Product Assistance -> Enterprise Technology -> SAP Master Data Governance -> Consolidation and Mass Processing -> Configuration of Consolidation and Mass Processing -> Configuration of the Process Template).

2. SAP Official Courseware MDG100 - SAP Master Data Governance (on S/4HANA 1909): Unit 8, "Data Consolidation," details the process steps and their configuration. The course materials explain the function of the FAR adapter and illustrate its use cases, including filtering records after validation failures or separating records from unresolved match groups, which directly supports options A and E. It also covers handling source records after a best record has been calculated, supporting option C.

To restrict master data replication to downstream systems based on specific criteria in SAP MDG, you use the Data Replication Framework (DRF). This requires two main configuration steps. First, you must define the filtering logic itself within an outbound implementation, which is a BAdI that controls data selection. This is done by creating or enhancing an outbound implementation and assigning filter objects to it. Second, you must define a replication model. This model acts as the central configuration object, linking the business object (what to replicate), the outbound implementation (how to replicate), and the target systems (where to replicate), including their communication channels.

C. Define Web service and filter by target system.

Filtering logic is configured within the Data Replication Framework (DRF), not directly within the web service (e.g., SOAMANAGER) definition.

D. Define replication model and filter by target system.

While you apply filter criteria within the replication model, this option is less precise. The fundamental steps are defining the filter capability (A) and the replication context (B).

1. SAP Help Portal - SAP Master Data Governance 1909, Data Replication Framework (DRF): The documentation outlines the configuration of data replication. It specifies the need to "Define Replication Models" where you assign outbound implementations and target systems. It also details how to "Enhance Outbound Implementations with Filters" by assigning filter objects. This confirms that both defining the replication model for a target (B) and defining the outbound implementation with filters (A) are required steps.

Source: SAP Help Portal, SAP S/4HANA 1909, Application Help > Cross-Component > Master Data Governance > Configuration of Master Data Governance > Configuration of Data Replication > Configuring the Data Replication Framework (DRF). Specifically, see sections on "Define Replication Models" and "Define Outbound Implementations".

2. SAP Help Portal - SAP Master Data Governance 1909, Filtering Data: This section explicitly states, "You can use filters to restrict the replication of data to the target systems... To use filters, you need to carry out the following main steps: 1. Define filter objects in Customizing for the outbound implementation... 2. Define a filter in the replication model...". This directly supports that defining the outbound implementation with filter objects (A) and defining the replication model (B) are the core steps.

Source: SAP Help Portal, SAP S/4HANA 1909, Application Help > Cross-Component > Master Data Governance > Data Replication > Filtering Data.

SAP Master Data Integration (MDI) is a service on the SAP Business Technology Platform designed to ensure master data consistency across the SAP Intelligent Suite. This consistency is foundational for executing SAP's core end-to-end (E2E) business processes. MDI is based on the SAP One Domain Model, which provides aligned data structures for key master data objects. The primary E2E processes that MDI is geared towards are Lead to Cash (customer/product data), Source to Pay (supplier/product data), and Recruit to Retire (workforce data), which is represented here by "Recruit to Hire". These processes span multiple applications (e.g., S/4HANA, Ariba, SuccessFactors) and rely on MDI for a single, consistent view of master data.

C. Order to Procure: This is a transactional sub-process within the broader "Source to Pay" end-to-end process, not one of the four core E2E processes itself.

D. Manufacture to Build: This describes a specific activity within the "Design to Operate" end-to-end process, which is another core process but is not listed as an option.

1. SAP Help Portal, SAP One Domain Model - The Common Language for the Intelligent Suite: "SAP One Domain Model enables a seamless integration across the entire value chain, supporting the four core end-to-end business processes: Recruit to Retire, Source to Pay, Lead to Cash, and Design to Operate." This document explicitly names the core processes that MDI supports. (Accessed under SAP Business Technology Platform documentation).

2. SAP Help Portal, What Is SAP Master Data Integration?: "SAP Master Data Integration is the central entry point to create, read, and update master data in an integrated and hybrid system landscape. It ensures the consistency of master data across the Intelligent Suite." This reference establishes the fundamental purpose of MDI in the context of the Intelligent Suite's processes. (Accessed under SAP Business Technology Platform > Integration Suite documentation).

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).

In the SAP MDG rule-based workflow (RBWF), the process logic is defined within BRFplus decision tables, primarily the "Single Value Decision Table" (e.g., DTSINGLEVAL). This table uses the current change request status and the previously executed workflow step as inputs (conditions). Based on these inputs, the table's result columns directly determine the subsequent flow. These result columns explicitly define the next workflow step (NEXTSTEP), the next change request status (NEWCRSTATUS), and the possible actions available in the user interface (UIACTION).

A. Predecessor steps in the workflow: The logic uses the immediate predecessor step as an input condition but does not determine the historical path or all possible preceding steps.

E. User responsible for the next workflow step: This is determined by a separate "User Agent Decision Table" (e.g., DTUSERAGTGRP...), not the primary process logic table.

---

1. SAP Help Portal, SAP S/4HANA 1909, "Configuration of the Rule-Based Workflow": This official documentation details the decision tables used in the RBWF. It specifies that the "Single Value Decision Table" (DTSINGLEVAL) contains the result columns Next Workflow Step, New Chg. Req. Status, and Cond. UI Action, which directly correspond to the correct answers. It also describes the separate "User Agent Decision Table" for determining the processor.

Section: Master Data Governance -> Configuration of Master Data Governance -> Configuration of Processes and Workflows -> Workflow Configuration -> Configuration of the Rule-Based Workflow.

2. SAP Help Portal, SAP S/4HANA 1909, "Service Level and Process Flow": This document explains the process flow control in MDG. It states, "The rule-based workflow enables you to define the process flow of a change request based on the change request attributes... The result of such a check is the next step in the process and the status of the change request." This supports the determination of the next step and status.

Section: Master Data Governance -> Configuration of Master Data Governance -> Configuration of Processes and Workflows -> Workflow Configuration -> Service Level and Process Flow.

To ensure validations occur within an SAP MDG change request process, two key configuration areas must be addressed. First, at the change request type level, you must link the process to the relevant validation and derivation rules, which are typically managed in a BRFplus application. This is done in the "Configure Properties of Change Request Type" activity, which requires a Business Activity to be defined and assigned.

Second, within the rule-based workflow template assigned to that change request type, you must configure the specific properties of the individual steps. This is where you define when the validations are executed. For a given step, you can specify that validation checks should be performed, thereby triggering the rules defined at the change request type level.

B. Enable edition for the required entity type in the data model.

This setting controls time-dependent master data management (creating versions with different validity periods) and is unrelated to configuring validation checks in a workflow.

C. Configure checks and enrichment spot properties for a standard business workflow.

MDG primarily uses a specialized rule-based workflow, not a generic "standard business workflow." Configuration is done through specific MDG IMG activities and BRFplus, not generic enrichment spots.

1. SAP Help Portal - SAP Master Data Governance 1909, "Configuration of the Rule-Based Workflow": This official documentation outlines the steps for configuring the rule-based workflow. It details the activity "Configure Properties of Change Request Step," where you define the behavior of each step, including the execution of checks and validations. This supports option D.

Reference Location: SAP Help Portal -> SAP S/4HANA -> Product Assistance (English) -> Cross-Component -> Master Data Governance -> Configuration of Master Data Governance -> Configuration of the Rule-Based Workflow.

2. SAP Help Portal - SAP Master Data Governance 1909, "Configuration of the Change Request Process": This section explains the setup for change request types. The activity "Configure Properties of Change Request Type" is detailed, showing where the Business Activity is assigned and how the link to BRFplus applications for validations and derivations is established. This supports option A.

Reference Location: SAP Help Portal -> SAP S/4HANA -> Product Assistance (English) -> Cross-Component -> Master Data Governance -> Configuration of Master Data Governance -> Configuration of the Change Request Process -> Business Activities.

3. SAP Press, "SAP Master Data Governance: The Comprehensive Guide" (2nd Edition): Chapter 5, "Process Modeling," describes the end-to-end configuration. Section 5.2, "Change Request Types," explains the role of business activities and the assignment of BRFplus applications for validation. Section 5.4, "Rule-Based Workflows," details how individual workflow steps are configured to trigger these validations. This confirms the necessity of both configuration activities (A and D).

SAP Master Data Governance (MDG) Consolidation is a process designed to identify and merge master data records from various source systems to create a single, high-quality "best record." The primary use cases are well-defined scenarios where data from disparate sources must be harmonized. These include preparing a clean master data set for an initial load before implementing central governance, integrating master data from different companies during a merger or acquisition, and creating a consistent, de-duplicated data set to ensure the accuracy of analytical reporting and business intelligence.

A. Monitor data quality for remediation: This is incorrect because monitoring data quality is the primary function of the SAP MDG, Data Quality Management (DQM) component, which uses evaluation rules, not the consolidation process itself.

C. Financial control in Central Finance integration (cFIN) projects: This is incorrect because while MDG is essential for data harmonization in cFIN projects, "financial control" is a broad business outcome, not a direct use case of the MDG consolidation process.

1. SAP Help Portal for SAP S/4HANA 1909, "Consolidation and Mass Processing": This official documentation explicitly outlines the key business scenarios for using MDG Consolidation. It lists the following:

Initial Load: "You can use the consolidation capabilities to perform an initial load of master data from various source systems into your SAP Master Data Governance hub." (Supports option B)

Consolidation for Mergers and Acquisitions: "You can use the consolidation capabilities to consolidate master data during mergers and acquisitions." (Supports option D)

Consolidation for Analytics: "You can use the consolidation capabilities to provide consolidated data for analytical purposes." (Supports option E)

2. SAP Learning Hub, Course MDG100 - SAP Master Data Governance on SAP S/4HANA (Version for 1909): Unit 8, "Consolidation and Mass Processing," details the same primary use cases. The course material explains that consolidation is used to achieve a "single version of the truth" for initial loads, M&A scenarios, and to feed consistent data to analytical systems like SAP BW/4HANA.