BRF+ Basic Workflow Setup

 Before starting this Make sure you choose workflow id: WS60800086 to Create Change Request Type.

I have created CR type: ZBPCREA1.

Planning the workflow design.

1. When requestor submits CR, it should get routed to first level approver.

2. First level approver should have option Activate/ Reject.

3. If Activate is clicked, CR should get activated.

4. If Reject is clicked, it should go back to requestor again.

5. Then requestor should have Resubmit/ Withdraw button.

6. If Withdraw is clicked, Workflow ends with final check rejected status.

7. If Resubmit is clicked, CR will get routed to first level approver again.

8. Again it will continue from point No 2.

Block Diagram of Workflow.

To use Business Rule Framework, Go to MDGIMG and follow below steps.

Click on New button and fill the CR types and Steps for Workflows to be created in BRF.

Save these entries in any TR.

Go to TCode: USMD_SSW_RULE or Follow below path.

Enter CR type and click Continue.

Select TR and Open Decision tables.

Click on Single Value Decision Table. 

By going into Table settings, Hide Change Request Priority, Change Request Reason, Change Request Rejection reason, CR parent step, Parallel Agent Grp Number, Merge Type, Merge Parameter, Hours of Completion, Dynamic Agent Service columns from table contents as these are not required as of now.

Start filling single value decision table.

Edit and add first row.

Condition Alias should have its corresponding entry in User Agent Decision Table/ Non User Agent Decision table.

In this step, After user clicks on submit button, workflow should be routed to steward/ First level approver. As this needs user intervention, this need to be added in User Agent Decision Table.

If role is used, then User Agent type will be AG and User Agent Value is Role Name.

Add another row in Single value decision table. Check step type and its actions. As it should be included as differencing factor between Activate/ Reject actions.

After activate step, it doesn't need any other user to process further as this is single approver workflow.

As this needs Non-user agent workflow for condition alias 2.

Process Pattern 06 specifies system that this CR need to be activated. 

After reject step, workflow need to be routed to requestor again. So, Condition alias 3 to be added in User-agent decision table.

Step type 4 will have Resubmit/Withdraw options. User type SU can be user for routing workflow to Previous processor or Requestor. Here, INIT specifies initiator of this CR and LAST can be used to route the CR to Previous Processor.

Continue adding more rows in Single Value Decision Table until all workflow is finished.

Finally, Single Value Decision Table.

Non-user Agent Decision Table.

Process Pattern 08 is used for stopping CR. This is used after clicking withdraw button by user.

Process pattern 99 is used for completing Workflow. So that it cant be processed further.

User Agent Decision Table.

Make sure that you have activated all these tables before closing the BRF. Else changes will not work for workflow.

TESTING.

1. Positive testing. In this no approver will reject CR.

With BP requestor role,

Open NWBC and Search Business Partner and Click on New.

Choose CR type.

Enter mandatory data and click on submit.

Check workflow log to whom it is routed at first level. It should be same as user defined in BRF.

Steward login. Open CR and Activate.

Final Check Approved after activation.

Data will be saved in active area. 

Check in BP transaction.

Similarly, check for Withdrawn Scenario/ Reject Scenario.