Process Pattern
The rule-based workflow groups several workflow steps together to form basic operations that are called Process Patterns
. These patterns are used to control the flow of the change request process or to define which background task the system will perform in a change request step.
Technically, the rule-based workflow runs in a loop. In each repetition of the loop, one out of several process patterns is executed. The workflow continues to run in this loop until the change request process is ended with the process pattern 99 Complete (Sub-)Workflow
.
If the current change request step is a user-agent step, the used process pattern is 01
UI Dialog
. For non-user agent steps, the column Process Pattern
in the Non-User Agent Decision Table
DT_NON_USER_AGT_GRP_<change request type>
is used to determine the pattern.
The possible process patterns are:
01
UI Dialog
This process pattern is used by the system for user-agent change request steps and should not be entered by you in the Non-User Agent Decision Table
. It is a special process pattern that is always automatically selected if a user agent has been found in the user agent decision table. This process pattern uses the dialog task Dialog Processing
TS60807954
.
02
Call Synchronous Method
You can use this process pattern to include operations that are not provided from SAP. This process pattern uses the background task Synch. System Method
TS60807949
. For more information, see BAdI: Calling of System Method for Rule-Based Workflow
in MDG Customizing under .
03
Call Sub-Workflow
You can use this process pattern to start a sub-workflow. The background task Subworkflow for Single Step Workflow
TS60807994
starts a sub-workflow with the workflow template ID that is read from the column Service Name
of the non-user agent decision table.
04
Call Data Replication
You can use this process pattern to start the replication of the master data after the change request has been activated. This process pattern uses the background task Change Request Replication
TS60807976
and the method DISTRIBUTE
of the object type MDG Change Request
BUS2250
to replicate the object using the data replication framework (DRF).
05
Activation (do not bypass snapshot)
You can use this process pattern to activate the data in the change request. This process pattern uses the background task Activate Change Request
TS60808002
with the indicator IGNORE_SNAPSHOT_DIFF
not set. The value of Previous Action
is updated with the result of the operation enabling you to handle error situations. If there have been conflicting changes to the data in the standard master data tables while the change request was in process the activation fails. In this case, Previous Action
is set to 33
Activation failed for Snapshot
. If the activation was successful Previous Action
is set to 31
Activation Successful
. In all other cases, Previous Action
is set to 32
Activation failed
.
06
Activation (bypass snapshot)
You can use this process pattern to activate the data in the change request, even if the data has been changed in the backend since the change request was created. The system ignores these potential changes and overwrites them. This process pattern uses the background task Activate Change Request
TS60808002
with the indicator IGNORE_SNAPSHOT_DIFF
set.
07
Validate Change Request
You can use this process pattern to validate the change request data. The results are written to the application log. The process pattern uses the background task Check Change Request
TS75707952
.
08
Roll Back Change Request
You can use this process pattern to remove the inactive data of the change request from the staging area if the change request should not be activated. This process pattern also provides the information when and by whom the change request was released and sets the change request status to 06
Final Check Rejected
. The process pattern uses the background task Discard Change Request
TS75707936
.
98
Error
You can use this process pattern to handle errors and exceptions. The process pattern uses the background task Error Handler
TS60807951
.
99
Complete (Sub-)Workflow
You can use this process pattern to end the rule-based workflow instead of looping back.