C_MDG_90 無料問題集「SAP Certified Application Associate - SAP Master Data Governance」

（A）A BAdl allows the implementation of ABAP coding for freely defined agent determination concepts.

（B）A pre-defined change request status can be assigned to the relevant change request type.

（C）A standard SAP MDG customizing table assigns organizational objects (user,org unit,etc.) directly to a workflow step.

（D）A FPM UI can be configured to allow the flexible agent determination.

（A）Reduction of manual correction work due to "First Time Right" data entry

（B）To deal with business deviation, complex deviation and cross-unit derivatives

（C）More automation in reconciliation of charts of accounts across multiple ledgers

（D）BRF + derivative works

（A）Specify the httpurlloc table entries if needed to enable transactions like NWBC and SOAMANAGER will be forwarded to the proper link from MDG system.

（B）Uniform assignment block for change request information

（C）Validity information included, if editions are used

（D）Personalization features, including layout, defaulting, and more

（A）Multi-column design, which includes up to three columns

（B）Change sequence

（C）Integration of Context Based

（D）Stacked UIBBs or tabs

（E）Expand, compress, or suppress blocks

（A）Define Priorities for Change Request

（B）Create Change Request Type

（C）Define Change Request Actions

（D）Configure Properties of Change Request Step

（A）Define a new business activity for the Fast-Track activity to route the change request directly to the final approval step.

（B）Create a custom step type, add your new Fast-Track action, and assign this step type to the corresponding change request step in the workflow setup.

（C）Adjust the workflow setup that the Fast-Track action will route the change request directly to the final approval step.

（D）Create a custom change request status, which includes the additional Fast-Track button, and assign this status to the corresponding change request step in the workflow setup.

（A）Reduced sales effectiveness.

（B）Delayed go-to-market process.

（C）Ineffective business decisions.

（D）None of the above.

（E）Sub-optimal procurement decisions.

（A）SAP HANA-based search

（B）Enterprise search

（C）Quality and Search

（D）Fuzzy search via BAS-DES (for example, SAP BusinessObjects Data Quality Management)

（E）DB-based search

（A）Import to MDG system, including master data, key mapping, and value mapping

（B）Export from client systems and MDG system, including master data, key mapping, and value mapping

（C）Conversion from IDoc format to SOA-Messages

（D）Records with a matching score lower than the low threshold are not regarded as duplicates.

（A）Define rule sets and insert required rules.

（B）Insert a validation rule into the workflow.

（C）Enable the material entity in the data model for validation.

（D）Create the CHECK_MATERIAL function.

（A）It allows flexible navigation between UIs.

（B）It provides enhanced determination of business activities.

（C）It provides a high-level process definition not tied to any business object.

（D）MDG-S, MDG-C: Business Partner (BP)

（A）Match groups that have matches above an upper threshold are sent to a change request automatically.

（B）Records within open match groups are processed separately as single records.

（C）Match groups that have matches above an upper threshold are approved automat cally.

（D）Match groups that have matches below an upper threshold are open and approved or rejected manually.

（E）Records within open match groups are rejected automatically.

（A）Dedicated DRFLOG transaction

（B）Search result list

（C）SAP Master Data Governance analytics

（D）Application log

（A）It also supports Data Migrations.

（B）Deep Dive API adaptations are feasible but are usually not necessary

（C）The directions can be switched on and off.

（D）A Synchronization Cockpit is available.

（E）Hooks for enhancements are available, including business add ins, and so on.

（F）Synchronization Process and Architecture that Supports.

（G）A Customizing is available.

（H）The CVI-Framework is used to keep the data synchronous in all directions.

（A）Credit-worthiness check (for example via Duns & Bradstreet interface) with the Data Import ^ Framework (DIF)

（B）Duplicate checks with the Customer Vendor Integration (CVI)

（C）Address checks with the Enrichment Framework

（D）Value added tax checks with the Service Mapping Tool (SMT)

（A）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])

（B）Automatic or manual replication to SAP and non-SAP systems

（C）Flexibility to replicate selected data only to a specific client system by defining filters (controlled by DRF)

（D）Monitoring and error handling

（E）Peer-to-peer or mediated

（A）Hierarchies are maintained in the hierarchy view of the collective processing application which is fully generic and works for all data models

（B）Additional UI elements are available that can be added to the single item maintenance UI in order to maintain information on higher level nodes and predecessorts

（C）Overall, three entity types are created. One for the design study name (ZHRCHNAME), one for the work packages (ZWPHIER), and one for the year (ZYEAR).

（D）Supports drag and drop

（A）Processing Times: You can detect peak and off-peak times during the processing of Processing Times change requests, You can compare processing times to SLAs and identify which change requests meet or exceed a specified due date. You can also measure how long it takes to process change requests, both by the change request type and by data model.

（B）You can analyze the processing times and statuses of Change Requests. This involves monitoring business activities, tracking compliance with Service Level Agreements (SLAs), optimizing processes, and turning insight into action.

（C）General The process is more visible. Statistics and graphics allow you to identify and fix General gaps in the process, bottlenecks, and errors. You can navigate directly to problematic change requests and fix the problems.

（D）The analytics feature is usually used by the Master Data Steward and the Master Data Expert when running analysis reports on the master data governance area.

（E）StatusesStatuses Statuses: You can identify the change request types that are processed quickly and the Statuses ones that are processed slowly. You can access summaries of the statuses of the change requests (for example, Final Rejected, Final Approved, or Created. You can also analyze why change requests of a particular status include errors or get rejected.

（A）Sales Determines cost and UoMs for sales. Also used for dynamic availability checks.

（B）Material requirements planning Determines required numbers of components for production.

（C）Purchasing Determines appropriate suppliers and lead times. Data from the material master is automatically filled into purchase requisitions.

（D）None of these.

（E）Storage allocation Determines special storage requirements such as storage UoMs, dimensions, weight, and hazardous markers