A. Match

B. Validate

C. Deactivate

D. Calculate best record

E. Activate

F. Standardize

A. Role-specific user interfaces can be configured in SAP MDG, no programming or modification necessary.

B. User interfaces for central governance can appear very differently along the process.

C. A cohesive MDM strategy helps elevate the conversation from data quality and governance issues with master data to efficient business processes and practices.

D. Every expert can get a dedicated, role-specific user interface that best fits their work.

A. Comprised business dynamics with negative impact on managing resources effectively

B. Pre-configured data models, user interface configurations, workflows, and data distribution are available

C. Lack of consistent information impedes to make critical decisions supporting innovation

A. All solutions use the SAP-BP as central anchor for identifying data

B. Business Partners that are customer and supplier are represented by one BP only

C. Solutions only being based on SAP-BP (e_g. Service Industries)

D. Transition from MDG-BP to MDG-S / MDG-C occurs without disruption

A. Master Data Governance for Customer (MDGC), and Master Data Governance for Supplier (MDGS) rather than in MDGF.

B. The second segment is related to the company code. This segment determines how the company code defines the account.

C. Financial master data is also used in the material and business partner (vendor/customer) objects. In MDG, this master data is maintained in MDGM.

D. The first segment is related to the chart of accounts and contains central control features (to be used across company codes) such as a description of the account, the consolidation account number, and if the account is a balance sheet account or a Profit and Loss (P/L) account.

A. Integrated object models can result in proven data models for operational and financial master data

B. Flexible enough to respect the distributed responsibilities existing in a company across various business units

C. Linear or distributed and workflow based

D. Data in process is stored in a separated repository and will be transferred to operational database after final approval

E. Roles, responsibilities, and task authority (for example, create, change, and approve requests)

F. Provides the possibility to extend the process by adding business logic and thereby bringing in data quality

G. Can be adapted and tailored based on customer needs

A. Duplication detection is based on SAP HANA.

B. Quality KPIs and associated metrics

C. A scorecard that measures data quality

D. The quality trend over time

A. Governance: Change requests with built in approval process

B. User-centricity: Central work center for the maintenance of materials

C. Deliver a Data Model proven by several applications and industries

D. Workflow: Standardized but flexible processes including rules management and tracking

A. Search active data only to limit search to active area.

B. Attribute-based search in specific fields only.

C. Free-text search across many attributes.

D. Fuzzy search checkbox to enable error-tolerant search mode.

E. MDG running on SAP HANA

A. Flexibility to replicate selected data only to a specific client system by defining filters (controlled by DRF).

B. Monitoring and error handling.

C. Support of different object IDs or customizing keys between hub and client systems (via mapping in SAP MDG or SAP NetWeaver Process Intrgration
[SAP PI]).

D. None of these.

A. Assign entity types to the change request type

B. Assign business activities to the change request type

C. Assign actions to the change request type

D. Assign the change request type to a workflow template

E. Assign change request steps to the change request

A. Configure Properties of Change Request Step

B. Define Priorities for Change Request

C. Create Change Request Type

D. Define Change Request Actions

A. Supports integration scenarios based on a Service Oriented Architecture (SOA) especially used WEB-Services,

B. Integrates into existing integration technologies e.g. Application Link Enabling (ALE) especially Intermediated Documents (IDoc).

C. Provides specification of business activity based on current UI and logical action for application-specific UIs.

D. Allows for an easy "growth path" from existing technology to SOA because it wraps the different communication channels.