Set Up the Rule-Based Workflow
Note
This document describes an example for a preconfigured Rule-Based Workflow for the Process Business Partner Cleansing Case.
MDG-S uses advanced workflow capabilities by combining the SAP Business Workflow with the SAP Business Rule Framework plus (BRFplus) tool. This section describes how to activate and load the necessary settings for BRFplus.
To use the predefined change request type BPCC2 run the following Customizing activity and activate the BC set CA-MDG-APP-SUP_VC_USMD110_C04
.
Check that the steps for Rule-Based Workflow are imported by the BC-Set by running the following activity in Customizing: .
The following are the default steps required for the predefined change request type BPCC2
.
Type of Chg. Request | CR Step | Keys | Validation | Description |
|---|---|---|---|---|
BPCC2 | 0 | Processing | ||
BPCC2 | 90 | X | Final Check | |
BPCC2 | 91 | Activation | ||
BPCC2 | 92 | Revision | ||
BPCC2 | 95 | Revision Processing | ||
BPCC2 | 96 | Processing After Activation Error | ||
BPCC2 | 99 | Complete |
To check that the predefined change request type exists see the Customizing activity .
To check that the link between the predefined change request type and the generated BRF+ application ID exists, run transaction SE16, enter the table name USMD213C_SSW and look for the following entries:
|
|
|---|---|
BPCC2 | 005056AC02D81ED2AC971CAB3C1DC848 |
Check that the BRF+ catalogs (inclusive application, functions, decision tables with content) for the predefined change request type are in the client.
Due to technical restrictions further settings currently cannot be included in the BC set processing therefore the following steps need to be executed manually:
Run transaction BRF+.
On the Catalog
tab choose Select Catalog
.
Enter the search criteria: Select the Object Type
Catalog and as Name
enter USMD_SSW_CATA_BPCC2.
Note
If the catalog does not exist in your client, export the catalog from the client 000 using transaction SCC1.
The import will also include the values in the three pre-delivered decision tables. For testing the standard workflow configuration you have to start the workflow now.
Maintain your content in the decision tables, reflecting your governance process. You can use the pre-delivered SAP content as a starting point.
To maintain your content either run transaction USMD_SSW_RULE
and select the correponding change request type or run the Customizing activity .
Note
If you extend the BRFplus decision tables make sure that the status of the final step is set to 05 Final Check Approved
or 06 Final Check Rejected
.
The following are the minimal settings for the relevant change request types.
DT_SINGLE_VAL_BPCC2
(Single value decision table)
DT_NON_USER_AGT_GRP_BPCC2
(Non-user agend decision table)
DT_USER_AGT_GRP_BPCC2
(User agent decision table)
DT_NON_USER_AGT_GRP_BPCC2
and DT_SINGLE_VAL_BPCC2
contain the automated steps and follow-up logic used by the BRFplus. The follow-up logic can either result in an automated step or in a user task that will be made visible as a workflow.
The users involved in the Master Data Governance process need to be included in table DT_USER_AGT_GRP_BPCC2
so that they can receive and execute the workflow tasks. Maintain agents (for example the users or organizations in the Portal Content and Portal Role Assignment sections of this document) for all change request types and their associated workflow steps. Each condition alias that appears in the DT_SINGLE_VAL_BPCC2
table needs at least one processor, either automatic or user (group). Therefore, for all non-automated steps at least one entry needs to exist in DT_USER_AGT_GRP_BPCC2
.
For further details on the workflow concepts, see Rule Based Workflow for Business Partner. You can adopt the settings described in that document for BP1P1 to BPCC2.
The following step types are pre-delivered by SAP:
Step Type | Short Description | Actions |
|---|---|---|
1 | Check Change Request | 01 Agree; 02 Disagree |
2 | Approve Change Request | 03 Approve; 04 Reject |
3 | Process Change Request | 05 Finalize Processing; 06 Send for Revision |
4 | Revise Change Request | 07 Resubmit; 08 Withdraw |
5 | Activate Change Request | 09 Activate; 10 Send for Revision |
6 | Approve Change Request (Without Rejection) | 03 Approve; 06 Send for Revision |
7 | Revise Change Request (Without Rejection) | 05 Finalize Processing |
8 | Activate Change Request | 09 Activate; 04 Reject |
The following agent types exist:
User Agent Type | Short Description |
|---|---|
US | User |
O | Organizational Unit |
C | Job |
S | Position |
AG | Role |
SU | Special User (Initiator/Last-Step User) |
The following is the standard content pre-delivered by SAP:
DT_SINGLE_VAL_BPCC2
Previous Change Request Step
| Previous Action
| Condition Alias
| New Change Request Step
| New Change Request Status
|
|---|---|---|---|---|
00 (Processing) | No value | 1 | 90 (Final Check) | 01 (To Be Considered and Approved) |
90 (Final Check) | 03 (Approve) | 2 | 91 ( Activation) | |
90 (Final Check) | 04 (Reject) | 3 | 95 (Revision Processing) | 10 (To Revise: Perform Changes) |
91 (Activation) | 31 (Activation Successful) | 4 | 99 (Complete) | 05 (Final Check Approved) |
91 (Activation) | <>31 (Activation Successful) | 5 | 96 (Processing After Activation Error) | 11 (Process Errors After Activation) |
92 (Revision) | No value | 6 | 99 (Complete) | 06 (Final Check Rejected) |
95 (Revision Processing) | 07 (Resubmit) | 1 | 90 (Final Check) | 01 (To Be Considered and Approved) |
95 (Revision Processing) | 08 (Withdraw) | 8 | 92 (Revision) | |
96 (Processing After Activation Error | 09 (Activate) | 9 | 91 (Activation) | |
96 (Processing After Activation Error | 10 (Send for Revision) | 3 | 95 (Revision Processing) | 10 (To Revise: Perform Changes) |
DT_USER_AGT_GRP_BPCC2
Condition Alias
| User Agt Grp No.
| Step Type
| User Agent Type
| User Agent Value
|
|---|---|---|---|---|
1 | 001 | 2 (Approve Change Request) | SU (Special User (Initiator/Last-Step User)) | INIT |
3 | 001 | 4 (Revise Change Request) | SU (Special User (Initiator/Last-Step User)) | INIT |
5 | 001 | 5 (Activate Change Request) | SU (Special User (Initiator/Last-Step User)) | INIT |
DT_NON_USER_AGT_GRP_BPCC2
Condition Alias
| Agent Group
| Process Pattern
|
|---|---|---|
2 | 001 | 05 (Activation (Do Not Bypass Snapshot)) |
4;6 | 001 | 99 (Complete (Sub-)Workflow) |
8 | 001 | 08 (Roll back change request) |
9 | 001 | 06 (Activation (Bypass Snapshot)) |
It is necessary to activate your new entries for each of the three decision tables.
In the preconfigured delivery for all step types the value for user agent type is SU (Special User) and the user agent value is INIT (Initiator). Therefore testing is immediately possible.
The quickest way to allow additional users to participate for example in the approve step for testing purposes is to copy the default entry for step type 2 into the DT_USER_AGT_GRP_BPCC2
table and change the entries as follows:
User Type: AG
(Role)
User Value: SAP_MDGS_MENU_04
(The MDG-S role of PFCG/SU01)
If the system cannot find a processor for your change requests check the background steps of the change requests workflow log to see if a work item with the description Set Status x for Change Request y
is in process or in error. If this is the case regenerate the authorization profile of SAP_ALL
or include USMD*
authorization objects into the authorization for the user WF-Batch.
Choosing the process pattern 06 Activation (Bypass Snapshot)
means that the business partner will be activated, even if the business partner record was changed in the backend system since the change request was created. Any backend changes are lost upon activation. You can adjust this behavior with SAP Note 1797009
. Implementing this note means that the system only overwrites changes to entities present in the change request rather than all entities.