Do you know how to modify the run-time value of workflow containers to adjust their content during execution?
This implies you can really change and control the work process runtime values after the work process has set off and the work things are made. Let’s go into the Modify the Run-Time Value of Workflow Containers Part 1.
Got Confounded?
Disregard the past lines
Prior to finding out about how to change the run-time worth of work process holders, we want to initially comprehend the business prerequisites that force any one to control the work process compartment esteem at run-time. The control can have various purposes, in our post, we will find out around two straightforward situations that will assist us with grasping the idea.
Note: We have partitioned this instructional exercise into two sections, for the simplicity of the perusers.
Business Requirement :
For instance, we have a work process that contains a sum of 3 stages.
Kindly see.
Presently we should envision that some how stage 2 went to mistake express that made the work process not complete.
Now if you are new to workflow, your first Question will be why it went to an error state?
There could be different explanations behind that and let me call attention to 2 reasons that are connected with this post.
- The Work process couldn’t get the ideal information and it got ended.
- The Qualities in the Work process holders were not populated at run-time or wrongly populated and it got ended.
We need to initially show you the examination between over two situations. How about we examine individually the two situations examined previously.
(A) The Workflow was not able to get the desired data and it got terminated.
Allow us to envision that the step number 2 was bringing a few information from the data set and in the event that information isn’t found, Stage 2 is designed to need to be in a mistake state.
A real time example for you guys :
Allow us to take a buy request work process that is getting the specialist list from a ZTABLE and it is designed to fizzle when there is no specialist/id found.
You can find in the beneath picture how work process couldn’t get any specialist from the data set and it went to a blunder state.
How to Solve this issue?
Presently if you have any desire to settle the issue you want to keep up with the information and again need to restart the work process utilizing t-code SWUS. We should keep up with the missing information and restart the work process.
After restarting the workflow.
See with your own eyes, the work process was restarted and it created another work thing.
Note: When the work process was restarted, it created another work thing and the entire interaction restarted again all along.
Thus, imagine a scenario where you need to restart the work process that is in mistake status because of information issue and furthermore you need that NO new work thing ought to be produced ie. the work process ought to restart from where it went in blunder.
Then you really want to utilize the exchange SWPR.
Present Scenario :
Desired scenario :
Conclusion :
What have we understood till now?
On the off chance that the work process went to blunder state because of certain information issue,
- We can regularly restart the work process utilizing exchange SWUS however doing so will produce another work thing and the entire interaction, Past advances that were at that point finished will be again executed.
Consider the possibility that there are in excess of 10 stages in work process and work process went to blunder state at the ninth step.
Isn’t it baffling that again similar clients for stage 1-8 will get the new turn out thing for similar record and they will execute similar advances in the future to finish a similar work and furthermore in future, the client should erase the old work thing from his work process inbox on the grounds that it is of no utilization.
Totally frustrating
- Presently let us accept that work process was restarted from the exchange SWPR, then no new work thing is produced and the work process is restarted from where it went to mistake.
Amazing
Presently if it’s not too much trouble, visit the following piece of the post where we will see the situation when the work process went to blunder state on the grounds that the qualities in the work process compartments were not populated at run-time or wrongly populated.
YOU MAY LIKE THIS
Flexible Workflow in SAP: Empowering Business Processes
Streamlining SAP Workflows: The Power Automate SAP Advantage
WhatsApp us