SAP MDG, Workflow Modeling
In My Previous blog, I have given introduction to SAP Master data governance (MDG) and different aspects of process modeling in MDG. Please check the below link.
https://medium.com/@sarojmeher200690/sap-mdg-process-modeling-d33d56187633
In this chapter will be discussing about different concepts of workflow modeling involved SAP MDG.
Workflow in SAP MDG:
It’s an Integral part of SAP Master data change request processing. MDG uses the workflow to govern all the change process related to master data. SAP provides different type of standard workflow templates as part of its change request type configuration.
The workflow settings in Customizing for MDGIMG -> Master Data Governance, Central Governance -> General Settings -> Process Modeling -> Workflow
Below are the different parts of involved in MDG workflow modeling.
· Activate Event Type Linkage
· Configure Workflow Tasks
· Standard Workflow
· Rule-Based Workflow
Activate Event Type Linkage:
SAP delivers object type BUS2250 (SAP MDG change request) for workflows associated with change
requests. To activate the type linkage, go to transaction MDGIMG -> Master Data Governance, Central Governance -> General Settings -> Process Modeling -> Workflow -> Activate Event Type Linkage.
Ensure, that one object type BUS2250 has the following settings:
Event: CREATED
Receiver Type: (blank)
Type linkage active: yes
Enable event queue: deactivated
To enter relevant function module and setting, Select the line and choose Goto -> Details.
Configure Workflow Tasks:
To ensure that processors of a change request step are selected as current agents at runtime and receive the work item, a dialog task needs to be categorized as a general task. If this is not done, then workflow will go into error due to not able to find any possible agents.
To complete the configuration, go to customization path Transaction MDGIMG -> General Settings -> Process Modeling -> Workflow -> Configure Workflow Tasks, and then perform the following tasks:
· Go to application component CA-MDG-AF and choose Assign Agents.
. All activities (denoted by TS*) that are not set as Background Task need to be set to General Task. To do so, select the activity, choose Attributes, and change to General Task. Ensure you follow the activity for all non-background task.
Standard Workflow:
SAP delivers several workflow templates along with change request types. It’s better to have a look at standard SAP workflows for different domain if that fits to business requirement. Otherwise there is always an option given by SAP to create custom change request process and modify the workflow WS60800086 driven with standard template, where business requirement can fit in.
To configure SAP driven standard workflow, below steps must be considered.
Define the workflow steps in customization, MDGIMG -> Master Data Governance, Central Governance under General Settings -> Process Modeling -> Workflow -> Other MDG Workflows -> Define Change Request Step Numbers.
Some example templates for MDG-S are below.
· Change request SUPPL1P1: WS54300005: Step 0, 1, 4, 5, 6, 7 (Supplier Create)
· Change request SUPPL2P1: WS54300007: Step 0, 1, 4, 5 (Supplier Change)
· Change request SUPPL5P1: WS60800059: Step 0, 1, 2, 3 (Supplier Block/Unblock)
· Change request SUPPL6P1: WS60800068: Step 0, 1, 2, 3 (Supplier Mark for deletion)
Lets discuss further with an example: Change request SUPPL1P1: WS54300005
Assign the processor to workflow steps. Perform the user assignment in Customizing for Master Data Governance, Central Governance -> Master Data Governance for Supplier -> Workflow -> Assign Processor to Workflow Step Number in BRFplus for Supplier
Go to Catalog and add the Decision Table: GET_AGENT
In the GET_AGENT decision table, you have to perform the following actions:
· Specify the type of change request and the change request step number. (Mandatory)
· If the change request step requires agent determination based on company code, Purchase org or central flag, maintain those values.
· Assign a processor by entering the object type and the processor ID. (Mandatory)
Rule-Based Workflow:
SAP delivers a rule-based workflow template (WS60800086), which is configurable using a BRF+ decision table and can be used for any change request process of SAP MDG where SAP-delivered standard workflow templates do not suit the project-specific requirements. Also, by this one can avoid coping the standard workflow and do modifications.
If Business requirement process is slightly deviating from the SAP delivered workflow template, then we can copy and modify the template. However, if the process deviates significantly from the SAP delivered workflow templates, then using a rule-based workflow template is more flexible.
In a rule-based workflow, the change request process is configured using decision tables for each change request type. Based on the current workflow step and action performed, decision tables determine the next change request step, status, and agents in the workflow process. For each change request type for which rule-based workflow is configured, a separate BRFplus application is generated by the system with an application name that contains the change request type.
Workflow template WS60800086 was built specifically for MDG to use the BRF+ application in order to dynamically control MDG processes. This workflow template is not to be changed using conventional workflow development tools. From the viewpoint of MDG, this workflow template is a black box. The BRF+ application is the window through which MDG controls the behaviour of the process.
There are mainly 3 elements in every change request BRF+ application to be focus.
· Single-value decision table
· User agent decision table
· Nonuser agent decision table
Single-value decision table:
· Also know as Next step decision table
· Decision table generated by the system has the name DT_SINGLE_VAL_<Change Request Type>.
· This table consist of 14 columns including both input and result column.
Input/Condition Column: Highlighted columns are Important for processing.
Result Column: Highlighted columns are Important for processing.
User agent decision table:
· Also known as Dialog Step Agent Decision Table. This table is used to determine the change request processor and UI action.
· Decision table generated by the system has the name DT_USER_AGT_GRP_<Change Request Type>.
· This table consist of 5 columns including both input and result column.
Input Columns: Highlighted columns are Important for processing.
Result Columns: Highlighted columns are Important for processing.
Nonuser agent decision table:
· Also known as Background Step Type Decision Table. This table is use to determine the background steps involved in change request.
· Decision table generated by the system has the name DT_NON_USER_AGT_GRP_<Change Request Type>.
· This table consist of 5 columns including both input and result column.
Input Columns: Highlighted columns are Important for processing.
Result Columns: Highlighted columns are Important for processing.
Below diagram Describes, How all the decision tables works.
What did we learn?
- Workflow Modeling requirement in SAP MDG change request processes.
- Event linkage for MDG workflow.
- Diffferent types of Workflow provided by SAP.
- Types of decision table involve in rule based workflow and its working. Further on decision table will be dicuss on different blog.
What Next?
Next Blog willl describe about BRF+ Wokflow WS60800086 Configuration in SAP MDG. Stay Tuned…
I would love to hear from you
You can reach me for any query or suggestion on the blog by below channels.
Gmail: sarojmeher200690@gmail.com
Linkedin: https://www.linkedin.com/in/saroj-meher-86017aab/
Please feel free to share with your colleague.