Review and/or define which statuses the change requests can have, and which processing options are enabled for those statuses. Optionally, you can add new statuses to be used in the change request types.

For more information, see Customizing for Master Data Governance under  General Settings Process Modeling Change Requests Edit Statuses of Change Requests .

The following statuses are delivered for the SAP standard processes.

Check that the following business activities are in your system and that they are assigned to the default data model MM.

For more information, see Customizing for Master Data Governance under  General Settings Process Modeling Business Activities Create Business Activity .

Create new change request types for data model MM, or validate after import using business configuration sets (BC-Sets).

For more information, see Customizing for Master Data Governance under  General Settings Process Modeling Change Requests Create Change Request Type .

The following table shows the change request types for data model MM. Only the relevant columns are included.

The standard workflow template used by Master Data Governance for material is WS60800086. This template is a rule-based workflow which uses BRF+ decision tables.

There is also a workflow template without BRF+, which covers the same processes. If you want to use this template, replace template WS60800086 with template WS46000057 in the relevant change request type.

The following settings should exist in the substructures of the change request types:

You can configure the properties of the change request steps. This is optional except for the Multiple-Record Processing change request types. For more information see Customizing for Master Data Governance under  General Settings Process Modeling Change Requests Configure Properties of Change Request Step .

For the Multiple-Record Processing change request types you can find the link to the example UI configuration under the view User Interface per Change Request Step.

For the change request types the following UI application names and configuration names are delivered for all steps using BC-sets:

Optionally, you can define priorities, reasons, or rejection reasons for change requests. You can enter codes and a short description to tag or classify your change requests. These codes can be used later for change request analytics (process quality analysis). They also can be used to influence the workflow-driven processes. For example, depending on the priority of a change request, you can mark it for special processing.

Perform the following activity in Customizing for Master Data Governance under  General Settings Process Modeling Change Requests Define Priorities / Reasons / Rejection Reasons for Change Requests .

Optionally, you can define print forms for change requests. By default, the form USMD_EDITION_CREQUEST is used. This is relevant only if your own or multiple print forms are required.

For more information, see Customizing for Master Data Governance under  General Settings Process Modeling Change Requests Define Print Form for Change Requests .