转 Consistency and Extended Checks for Workflow Template and Tasks

Consistency and Extended Checks for Workflow Template and Tasks

By Anirban Bhattacharjee, KPIT Cummins and Infosystems from Link

Purpose: The purpose of this document is to demonstrate how to perform Extended Checks and Consistency Checks for a Workflow Template and Standard Tasks.

Use and need: These checks are similar to extended checks and code inspector checks that are performed on any ABAP Code, Function Module or Class.

Process: SAP has provided standard transactions to execute these checks. We will discuss these transactions in detail.

These transactions are SWU7 and SWU4.

Transaction SWU7 is used for checking Workflow Templates.

The entry screen of SWU7 looks as shown. We enter the Workflow Template ID of the workflow which we want to check

Execute the program. The output is as shown

We can see the program prompts in this case that there is one INFORMATION message: No start events or start transactions/forms.

We can run this program with another workflow template that has more steps and see the following output

We can thus see that the program analyses each step of the workflow and displays the results.

The program also displays multiple check results at the same time. Simply enter the range of workflow template IDs at the select option in selection screen.

This will give the following output

We can thus correct and tune the workflow to make its performance much better.

Transaction SWU4 is used for checking Standard Tasks.

The entry screen of SWU4 looks as shown. We enter the Standard Task ID of the Task which we want to check

The output of the program is shown below

We can see that the program returned the Standard Task to be completely consistent. It would have captured and displayed any errors / warnings / information accordingly.

Advantages of these transactions:

·         All possible runtime errors are displayed, like loss of data in bindings, data type mismatch, etc.

·         Containers elements that have been declared and not used are also displayed.

·         Event linkage and trigger failures are detected and displayed. Hence we can analyze event issues without executing the workflow or displaying it.

·         Incomplete steps created in the workflow template are also captured.

·         Missing bindings in workflow and standard task are displayed.

·         Inconsistent code / bindings / containers, etc are detected.

·         Multiple Tasks and Workflow Templates can be checked at the same time.

These transactions perform many more extended checks which you will get to know when you run them for different workflow templates and standard tasks that you might have created in the system. These transactions are very important to analyze with certainty that the workflows will have a stable runtime environment.

Conclusion: We have demonstrated successfully the standard transactions provided by SAP to perform Consistency and Extended checks on Workflow Templates and Standard Tasks.