In this blog, the second in a 73-part series, we discuss the use of SAP Workflow as an extension of ABAP: a kind of 'ABAP++'.
Plus-Plus building blocks
Workflow is often thought of as 'simply' a tool for collecting approvals: approve a Purchase Order, reject an employee's leave request, etc. It's usually all about decisions, inboxes, agent assignment and so on.
But workflow can also serve as a rich programming tool for deftly handling complex sequences of background steps. We can in fact use it when there is no human interaction at all.
Let's start with a real-world example from one of our recent clients, a state tax office.
We all pay tax. Let's say you appealed against a harsh assessment of your 2012 return, and the tax office reduced your tax bill by $1000. That's called a 'reassessment', and while it's great news for you, it‘s a practical burden for the tax office. A reassessment requires significant post-processing:
Can you imagine a tax officer doing all that manually, and in the right order? I can't. So we decided to automate it. The tax office liked this idea a lot, but had some strict stipulations:
Can you imagine a clever ABAP program doing all of this? I can't. When do we trigger the program? Where do you keep this audit trail? What about restarts and locking errors?
OK, maybe it could be done. But to any workflow developer, the above requirements clearly spell out the word 'W-O-R-K-F-L-O-W'.
What seems like an impossible set of requirements is really no problem at all, once you approach it from a workflow perspective.
The use of SAP workflow technology then provides the following snappy features for free:
Returning to our tax office client, the above workflow was successfully implemented and now handles hundreds of reassessments a week. This saves the tax officers many hours of drudge work, and ensures that all steps are done correctly and in the right order. Errors are very rare, especially after we sorted out a few issues with temporary error handling.
Once they felt the power of workflow, our client embraced the idea. We now have 'ABAP++' workflows handling processes such as:
I'm sure many other people have explored this same concept; I just haven't seen many examples of it yet. I'd love to hear your stories..
* obscure 80's music reference
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 |