I trust our previous article, “Modify the Run-Time Value of Workflow Containers. Part 1,” helped you understand the pros and cons of restarting a workflow when it goes into an error state due to data issues. However, what if the workflow went into an error state due to a missing container value, or the workflow behaved incorrectly because of wrong container data? In this continuation, “Modify the Run-Time Value of Workflow Containers. Part-2,” we will explore how to address such issues.
Before we start let us simply attempt to comprehend what is a Compartment with regards to work process.
Holder: For the present simply envision Compartment as a can that holds the information and at runtime, work process gets the required/functional information from this pail. Simple right? See with your own eyes how the work process holder holds the information.
Presently investigate a continuous model that will show you how a missing holder esteem constrained the work process to go into the blunder state.
In the beneath picture, you can see that the work process went to mistake and the work process log uncovers that work process compartment is feeling the loss of an information because of which the work process fizzled.
On the off chance that we troubleshoot the blunder work thing, we will come to know which component/information is absent in the compartment. For this model, subsequent to troubleshooting the work thing we came to realize that the delivery code was absent in the work process compartment
Let’s have a look at Some of the debugging snapshots :
Note: These snapshots are just giving you a glimpse of a real time scenario.
Presently here comes the most outstanding aspect. We should restart the work process very much as we did in the primary situation when the work process went to mistake state because of an information issue.
How do I Restart?
The first method will be using transaction SWUS to restart the whole workflow from the starting.
- Doing so will again execute the entire work process ventures from the beginning and the recently gotten done with job will again restart that should be finished by the specialists of the separate work process task.
- Utilizing SWUS, restarting the work process won’t give you the assurance that this time the missing/wrong qualities will be available in the work process compartment. It could be conceivable that holder values are not getting populated because of some information base issue. In the event that you are sufficiently fortunate, restarting the work process can work however there is no assurance that restarting the work process will tackle the issue.
You can not do anything here
- Restarting the work process utilizing SWUS will again produce another work thing in the client’s inbox. Past step clients should again play out a similar work with the new work thing. Past step client can get disappointed doing likewise work over and over. Seriously, I have perceived how clients lash out when they get the new turn out thing for a similar errand. Making another pass to erase the old work thing from their inbox comes as unexpected occupation for themselves and imagine a scenario in which restarting the work process again not tackled the issue and past step client again gets the new work thing to finish.
So, are you going to restart the workflow, again and again? Generating a new work item each time and consider the possibility that the issue isn’t addressed.
The subsequent technique will utilize exchange SWPR to restart the work process from where it went to a mistake state.
Say thanks to God, Restarting the work process utilizing the exchange SWPR won't produce another WorkitemAllow us to do that and see regardless of whether this technique would populate the missing holder esteem.
Steps: Run the exchange SWPR and enter the work thing that should be restarted from the step where it stalled out and press restart.
Wait…What ? The SWPR transaction is not able to restart the workflow.
But Why?
Since, this time as well, the missing compartment esteem is absent in the work process holder.
Presently I suppose you have perceived the motivation behind looking at both the situations where work process went into mistake state because of information issue and work process went to blunder due to missing/compartment esteem.
I realize you are interested to figure out how to determine this missing compartment esteem thing.
SAP has given a standard capability module named ” SWL_WI_CONTAINER_MANIPULATE”
This strong capability module permits you to pass the work thing ID of the step whose holder you need to alter. You can show and alter the compartments. For our situation, the work thing ID is 123456 and the delivery code isn’t populated.
Steps for changing the container value :
- Run the exchange SE37 and execute the capability module SWL_WI_CONTAINER_MANIPULATE
- Enter the work thing number whose compartment esteem should be adjusted and eliminate the showcase steady worth ‘X’ with the goal that you will actually want to alter the holder esteem. Then, at that point, Execute.
- Presently you will actually want to see the work thing holder values. Double tap the compartment esteems whose information should be controlled and adjust the worth.
- Whenever you are finished. Restart the work process utilizing SWPR or SWUS in view of the business need.
Here we are restarting the work process utilizing SWPR exchange since we would rather not produce another work thing once more.
You can see that presently in the wake of restarting the work process, it restarted impeccably without going into a blunder state.
Reason: Since this time the missing holder esteem is available in the work process compartment and the work process has gotten the compartment esteem at run time.
Seeing is Believing…
I trust you enjoyed reading this post and understanding the essential difference between restarting the workflow using transactions SWUS and SWPR. Additionally, I hope you have gained insights on how to Modify the Run-Time Value of Workflow Containers. Part-2. Stay tuned for more details in Part 3 where we will dive deeper into adjusting container values during workflow execution.
YOU MAY LIKE THIS
Integration with SAP Systems and Workflows
WhatsApp us