Parallel Workflow Implementation

 

Parallel Workflow Configuration & BADI Implementation

 

·       We have Vendor namely In-direct Supplier in which we have steps as below workflow diagram.

·       There are two tasks which are in parallel which is independent of each other.

·       In MDG, we have to Implement some BADI’s to handle this type of workflow.

·       Following are the step by step procedure to Configure and Implementation of BADI’s.

 

            

                                    Figure: In-direct Supplier Workflow

 

Steps to follow

1.       First, will create service name which we will mention further to filter BADI’s. For that, go to MDGIMG -> Process Modelling -> Workflow -> Rule-Based Workflow -> Define Service name for Rule-Based Workflow.

2.       After that maintain one service name as follows.

 

3.       Next, Create Change Request. Copy all attributes from another standard Supplier workflow.

 

 

4.       Maintain Steps in following path.

 

5.       Next go to RBW configuration using Transaction USMD_SSW_RULE or below path.

 

 

6.       Maintain following values in Non-User DT, User DT and Single Value DT.

 

Note: In Service Name Field, give the Service name which we have created in above step.

Note: In Merge Parameter field, give the same Service name or Create another service name for this as per the requirement.

7.       Now Implement BADI’s. We have to Implement 2 BADI’s as following. Use following Path or Directly open Transaction SE18 and open Enhancement Spot ‘USMD_SSW_SERVICE_PROCESSOR’.

 

By Right Clicking on Implementation, create one Implementation, give Service name in filter value and activate it. Here, we no need to write any code inside method of Implementation.

8.       Go to another BADI, where we need to write code. Create one Implementation give Service name in Filter value and Open

 

Write Following Code and Modify it as per requirement.

 

 

 CONSTANTS: lc_mergestep    TYPE usmd_crequest_appstep VALUE 'DG',
               lc_finalize     TYPE usmd_crequest_action VALUE '05',
               lc_sendrivision TYPE usmd_crequest_action VALUE '06',
               lc_crtype       TYPE usmd_crequest_type VALUE 'ZINISUP1'.

    CLEAR: ev_merge_action, et_message, ev_merge_step.

    CALL METHOD cl_usmd_crequest_api=>get_instance
      EXPORTING
        iv_crequest          = iv_cr_number
      IMPORTING
        re_inst_crequest_api = DATA(lo_crequest).

    lo_crequest->read_crequest(
      IMPORTING
        es_crequest   = DATA(ls_request)                 " Change Request
    ).

    IF ls_request-usmd_creq_type EQ lc_crtype.

      LOOP AT it_step_action ASSIGNING FIELD-SYMBOL(<ls_step_action>).
        IF <ls_step_action>-action = lc_sendrivision.
          ev_merge_action = lc_sendrivision.
          ev_merge_step = lc_mergestep.
          RETURN.
        ENDIF.
      ENDLOOP.

      ev_merge_action = lc_finalize.
      ev_merge_step   = lc_mergestep.

    ENDIF.

 

9.       After that Activate this BADI too and test your workflow.

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