Routing Workflow Dynamically

 

Requirement

·       We need to route the workflow according to changes in Bank Data in Supplier Workflow.

·       While updating the supplier if the requester changed bank data then the CR should go to Approver or else it should get auto completed.

Workflow Diagram

                      

Steps

Creation of Change Request

MDGIMG -> General Data -> Process Modelling -> Change Requests -> Create Change Request Type.

 

Defining Workflow Steps

MDGIMG -> General Data -> Process Modelling -> Workflow -> Rule-Based Workflow -> Define Change Request Steps for Rule-Based Workflow

Define Service Name

MDGIMG -> General Data -> Process Modelling -> Workflow -> Rule-Based Workflow -> Define Service Names for Rule-Based Workflow

Configure Rule Based Workflow

MDGIMG -> General Data -> Process Modelling -> Workflow -> Rule-Based Workflow -> Configure Rule-Based Workflow

·       Enter respective change request type.

·       Here we need to create one data object with type Element which we will further use in single value decision table for routing the workflow.

·       For this we will create one data element using SE11 and maintain fixed value as below.

·       We have maintained ‘Y’ and ‘N’ values in fixed value range in domain for decide whether the bank data is changed or not.

 

·       Bind newly created BRF+ Element to the DDIC Data Element which we have created before.

·       In domain values we can check the value range

·       Maintain the element in Triggered function

·       Maintain service name in below area

User Agent Decision table configuration

Non-User Agent Decision table configuration

Single Value Decision table configuration

·       In this we need to add the element into table metadata

 

Table Settings -> Insert Column -> From Context Data Objects -> Add bank field

·       The new column will get added as shown below

 

Implementation of BADI:

MDGIMG -> General Data -> Process Modelling -> Workflow -> Rule-Based Workflow -> Business Add-Ins -> BAdI: Rule Context Preparation for Rule-Based Workflow

Or follow this -> SE18 -> ENH. Spot ‘USMD_SSW_SERVICE_PROCESSOR’ -> BADI Definition ‘USMD_SSW_SERVICE_PROCESSOR’ -> Create new Implementation

 

 

 

 

·       Maintain filter values as service name which we mentioned in BRF+

·       Implementation of BADI Class.

 

Comments

Post a Comment

Popular posts from this blog

SAP MDG Process Modelling

Image
Overview In SAP MDG, every change to master data is initiated using a change request. After a change request is initiated, it needs to be processed before activation or rollback by applying governance rules and collaborations. The process model provides the required input (metadata) for change request creation and processing, e.g., workflow, CR steps, and objects that can be processes. Submit and activate/rollback are mandatory steps in a change request. MDG reuses the SAP Business Workflow component of an underlying SAP business suite. SAP MDG workflow is an instance of SAP Business Object BUS2250. If the request has parallel processing, then each parallel step of the change request will have one BUS2250 instance. Define Governance Scope: Here we can define governance scope on the entity as well as the attribute level. For example, we have kept ‘NO’ to the below custom entity. As a result of MDG UI, the UIBB for this entity will only be in read-only mode. Business Object An ...
Read more

MDG Derivation (BADI)

Image
In this blog, we will see how to derive MDG attributes using BADI. Derivations can be divided into two types.  Single-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from same entity. For this, we use 'USMD_RULE_SERVICE' BADI definition. Cross-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from another entity. For this, we use 'USMD_RULE_SERVICE_CROSS_ET' BADI definition. First, we will see a single entity derivation. Scenario:  We are going to make language English as the default if the user gives the country as India. Steps: 1. Go to SE18. 2. In 'USMD_RULE_SERVICE' BADI defination, create BADI Implementation.  3. For creating BADI Implementation, first we need to create Enhancement Implementation.  4. Give the properties as below. 5. Now, create BADI Implmentation and give following properties. 6. Maintain the filter values. H...
Read more

MDG Validation (Using BADI)

Image
In this blog, we will see how to validate the MDG attributes using the BADI implementation. So, we are taking the example of the 'BP Grouping' field to make it mandatory on the UI. For this, we should know the technical attribute name for the respective field. In our case, 'BU_GROUP' is the technical name for the BP grouping field. Steps for the Implementation of Validation BADI. 1.   Open T-code ‘MDGIMG’ –> General Setting -> Data Quality and Search -> Business Add-Ins -> Execute BADI: Define Validation/Derivation OR SE18 -> BADI name: 'USMD_RULE_SERVICE' -> Create BADI Implementation.  2. After execution, the following screen will appear. Go down, and there you will find the option to create enhancement implementation. Click on that button. 3. Provide the name and short description of the implementation, as follows:   4.  After that, we have to create the BADI Implementation and Implementation class. 5.  You will be directed to the Enha...
Read more