先試後買

A. The first data set is restricted in its validity (until 31.12.2017) and the second data set is created {from
01.01.2018)

B. The first data set is updated with the data of the second data set

C. The first data set is marked for deletion and a second data set is created (from 01.01.2018)

D. A second data set is created {from 01.0 1.2018) and the first data set is NOT updated

A. Validations.

B. Prevent creation of duplicates for increased effectiveness and
efficiency.

C. Address enrichment.

D. None of these.

A. Change request types for the entity type

B. UI configuration for an entity type

C. Storage/use type of an entity type

D. Relations for entity types

E. Attributes which are part of an entity type

A. Heterogeneous data providers can be selected to retrieve data.

B. Data stored in one flat internal table can be based on a dynamic structure

C. Authorization checks can be performed out of the box.

D. BCV can display and change the data in the predelivered UI.

A. Define Authorization Relevance per Entity Type

B. Define Field Properties for UI

C. Configure Properties of Change Request Step

D. Define Available UI Applications

A. SAP BusinessObjects Data Services). These might be sufficient for loading data in non-SOA based format (such as csv-files or, IDoc-XML) into the active area.

B. MDG-F does not use data export / data import framework. Instead, it uses file upload / file download functionality. For more information, see the initial load of MDG-F system and documents working with Master Data governance / financial / file uploads and downloads.

C. For business partners, transaction BUPA_SEND is available, which includes complete address data.

D. SAP MDG stores data in one of two persistencies: staging area or active area. Data in the staging area is not ready for consumption and usually has to be approved by a master data steward to be sent to the active area.

A. After the final approval of the change request

B. After the creation of the change request

C. After executing the validations for the master data object successfully

D. After saving the master data object in the user interface

A. SAP BusinessObjects Data Services). These might be sufficient for loading data in non-SOA based format (such as csv-files or, IDoc-XML) into the active area.

B. For business partners, transaction BUPA_SEND is available, which includes complete address data.

C. SAP MDG stores data in one of two persistencies: staging area or active area. Data in the staging area is not ready for consumption and usually has to be approved by a master data steward to be sent to the active area.

D. A Change Request section that includes the Change Request UIBB, both automatically added by MDG Communicator.

A. Call transaction a) MDGIMG. Find under General Settings Process
Modeling Change Requests Define Rejection Reasons for Change
Requests

B. Add a reason for your change request type with the pattern b) SFZ## by adding them and specify a reason.

C. Call transaction a) MDGIMG. Find under General Settings Process
Modeling Change requests define reasons for change requests.

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

B. Monitoring and error handling

C. Reuse existing data structures and functionality of SAP Business Suite

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