Show TOC

Background documentationConfiguration of the Change Request Process

 

When configuring the change request process you need to define the following:

  • Processing steps and their processors

  • Possible actions of processors

  • Process flow between steps

  • Change request status in each step

Additionally, you can use editions to schedule changes and you can define when the data replication should happen. For more information, see Using Editions to Schedule Changes.

You must configure the following elements:

  • Change Request Type

    The change request type defines which data can be processed. The change request type is assigned to one MDG data model and lists the possible entity types that the change request can contain.

    SAP Business Workflow is used to process change requests in SAP Master Data Governance. To define the process flow of the change request you can use standard workflow templates or custom workflow templates when defining a change request type. For more information on SAP Business Workflow, see the Customizing activities under Start of the navigation path SAP NetWeaver Next navigation step Application Server Next navigation step Business Management Next navigation step SAP Business Workflow End of the navigation path.

    Alternatively, you can use the MDG rule-based workflow template when defining a change request type. In this case, the content of Business Rule Framework plus (BRFplus) decision tables defines the process flow of the change request.

    For more information, see the Customizing activity Create Change Request Type under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests End of the navigation path.

  • Change Request Step

    Each change request process consists of a number of change request steps that can be either dialog steps or background steps. For each dialog change request step, you can do the following:

    • Assign processors

    • Configure validations and data enrichments

    • Assign UIs

    The processing sequence of the steps is based on the processors' decision and other criteria that are evaluated by the workflow assigned to the change request type.

    If you are not using the rule-based workflow, the workflow template defines the available change request steps. Every change request type using this workflow template can only have the available steps. For more information, see Customizing activity Define Change Request Step Types and Assign Actions under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow End of the navigation path.

    If you are using the rule-based workflow, the Customizing settings and the content of the BRFplus decision tables define the available steps. Every change request type using the rule-based workflow can have different change request steps although all change request types are using the same rule-based workflow template. For more information, see Customizing activity Define Change Request Steps for Rule-Based Workflow under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow Next navigation step Rule-Based Workflow End of the navigation path.

  • Change Request Step Type and Change Request Action

    The change request step type defines the possible actions that a processor of a change request step can use. We deliver a number of change request step types, for example Approve Change Request with the possible actions Approve and Reject.

    The change request step type of each change request step is determined at runtime. You can configure a change request step that allows the actions Approve and Reject in one case, while allowing Finalize Processing and Send for Revision in another case.

    For more information, see Customizing activity Define Change Request Step Types and Assign Actions under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow End of the navigation path.

  • Change Request Status

    The change request status informs the user about the processing status and determines the possible changes to the change request and the contained data. We deliver a set of status control attributes:

    • no processing

    • objects can be added or removed

    • data changes are allowed

    The following statuses that finalize the change request and stop further processing: Final Check Approved and Final Check Rejected. In all other statuses, including any custom statuses, the change request is still open and interlocks the contained data to protect it from processing with other change requests. For more information, see Customizing activity Edit Statuses of Change Requests under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests End of the navigation path.

    The change request status is set by the workflow. Either the task Set Status of Change Request is used to set the status or, if the rule-based workflow is used, the decision tables are used. For more information, see Customizing activity Configure Workflow Tasks under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow End of the navigation path.