Describing Master Data Governance - Mass Changes and Multiple Obj

1.

Which are characteristics of multi-record processing?

There are two correct answers.

It is designed only for large datasets without defined workflows.

It applies only to governance processes for single objects

It involves a well-defined governance process with multiple workflow steps for a limited number of Business Partners.

It is typically a collaboration of multiple processors.

2.

In which multiple object processes is the Highlight Changesoption supported?

Choose the correct answer.

In multiple-record processing

In the mass change process

3.

Which statement is correct?

Choose the correct answer.

Multi-record processing is typically an ad-hoc task for one business user.

Multi-record processing never includes collaboration of multiple processors.

Multi-record processing is a well-defined governance process with multiple workflow steps.

4.

What tasks can master data governance change requests manage?

There are two correct answers.

Single object processing

Form-based workflows

Combining materials and suppliers in one change request

Managing mass changes without preparing a change request

5.

Select the actions that enable hierarchies for an entity type.

There are two correct answers.

Changing the Hierarchies attribute to 'Yes'.

Changing the Hierarchies attribute to a value other than 'No hierarchy'.

Setting the Hierarchies attribute to 'No hierarchy'.

Adding a new key field to the entity type.

6.

Select the true statements about hierarchy names.

There are two correct answers.

Hierarchies always have a name that is modeled as an additional entity type.

The hierarchy name can have leading relations (additional key fields).

The hierarchy name is optional and not required for any hierarchy.

Hierarchy names are defined separately from the hierarchy table.

7.

What are valid considerations for defining multiple object change requests?

There are two correct answers.

Objects in a change request must be of the same object type (e.g., material or supplier)

Objects can be selected without assigning them to a change request.

Customizing in the Implementation Guide is not required for multiple processing.

Change request workflows and validations are determined by the change request type.

Knowledge quiz

Which are characteristics of multi-record processing?

In which multiple object processes is the Highlight Changesoption supported?

Which statement is correct?

What tasks can master data governance change requests manage?

Select the actions that enable hierarchies for an entity type.

Select the true statements about hierarchy names.

What are valid considerations for defining multiple object change requests?