Working with Container Operation and Loop (Until) Steps - PART2

Note: 

  1. Before reading this document readers must study Part 1 of this document. i. e.( Working with Container Operation and Loop (Until) Steps - PART1 ).
  2. This document will help us to learn how to execute and analyze a workflow.
Steps:
  1. In Part 1 of this document we have seen how to build a workflow with Container Operation and Loop (Until) Steps.

final_screen.PNG

2. After completely Building a workflow we can start our execution process.

  • We have to press execute button(F8) to run the workflow.


Excecute_screen.PNG

3. Now we can see a screen as shown below.

first execute screen.PNG

4. This screen consists of the following tabs.
  •      Input Data Tab.
    • Here we have to fill in the importing input parameters.
    • _wf_initiator , _wf_priority and _wi_group_id are default parameters.
    • lv_counter  is the parameter created by us for keeping the loop count
    • (This is discussed in Part 1 document->ABAP Workflow For Beginners: Working with Container Operation and Loop (Until) Steps-PART1’)
    • We can change the value of the ‘lv_counter’ parameter to our desired value.


Execute_work_flow_container.PNG

5. Now we have to press on Execute(F8) to start workflow processing.

start_WF.PNG

  • We will get the following status message.

start_wf_message.PNG


6. Now as we have started the execution of our workflow we have to follow steps to analyze the execution of it as shown below.


   Test_work_flow_steps.PNG

  • Graphical Workflow Log:
    • This will display a graphical representation of the process flow of our workflow.
    • The green path will show the step-by-step execution of the workflow.
    • Here we can see that first the loop step will be executed.
    • And then the container operation step will be executed, here the decrement of the value of the ‘lv_counter’ element by 1 is performed on every loop execution.
    • Then the next step to execute will be the ‘send mail’ activity.
    • After the ‘send mail step’, the loop will continue to execute until the ‘lv_counter’ element’s value will be ‘0’.
    • Once the ‘lv_counter's value is ‘0’, the loop ends and workflow completes.    


Graphical_view.PNG

  • Workflow Chronicle log:
    • This log consists of a tree view(technical Details) of the steps executed in a workflow.
    • Here in the below figure, we can see that five loops have been executed.
    • This is because our ‘lv_counter’ value is ‘5’ and the loop step will loop until the ‘lv_counter’ value is ‘0’( This is discussed in the Part 1 document).
    • With the execution of each loop, the ‘lv_counter’ Value will be decremented by 1(That is why the loop will end after 5 executions).


Chronicle_log.PNG

  1. In technical details (Tree structure) we have 6 tabs.
  • Details tab
    • Has details like workflow task ID, Work item status, date, time, etc.

details_tab.PNG

  • Step History tab
    • This is a step-by-step error detail.
    • There are no errors in our workflow execution, that is why ‘Execution Action’ is in green status.

step history tab.PNG

  • Deadlines tab
    • This step shows the deadline details for the steps used(example mail step).
    • We have not set any deadlines so this tab has no entries. 

deadline details.PNG

  • Task Description tab
    • This step shows the description of the tasks that are used in our workflow.
    • For example: Send Mail step body content. 

task description tab.PNG

  • Container tab
    • This tab consists of the container elements with their runtime values.
    • For example:’lv_counter’ value will be  ‘0’  after completion of the workflow execution as shown below.

Container tab details.PNG

  • Message tab
    • This tab displays work item-wise message details.

message tab.PNG

2. SAP business workplace

  • Sap business workplace (T code SBWP) is a place, where we can view the emails triggered by a workflow as shown below with recipient specified as our SAP login ID.
  • As we can see ‘5’ unread mails are displayed in the ‘Inbox’.
  • This is because the ‘send mail step’ is created inside the branch of  ‘loop until step’ and the ‘loop until step’ will be executed 5 times.
  • And the mail recipient is ‘WF_INITIATOR’, that is why the mail is sent to our ‘Inbox’.

      

sbwp.PNG

  • After opening the mail we can see the following details.
    • Subject, the body of the mail, and recipient details will be displayed.

sbwp_mail.PNG

7. This ends the detailed explanation of the execution of workflow( Creation is explained in Part 1).

Conclusion: Now we know how to execute a workflow using step types: loop(until), Container operation and Send Mail.


Workflow CreationPlease refer to my Blog with Part - 1Working with Container Operation and Loop (Until) Steps - PART1

Comments

Popular posts from this blog

Working with Container Operation and Loop (Until) Steps - PART1

Working with Fork