workflow error report
Klika, Michael
Michael.Klika at ids-scheer.com
Fri Mar 11 05:30:58 EST 2005
Hi Austin
Please correct me, but I think you might want to go for another approach:
- Usually Workflows go into error because of technical problems (wrong coding, forgotten exceptions, missing user rights, ...). In this case the (technical) workflow admin receives a message in his/her inbox. Those errors occurr because of technical problems that should be solved soon(!) that they won't occurr again.
- Problems from inside the process with a process related reason, e.g. "status cant be changed", should be covered by a concept of modelled error handling and should produce a workitem in a "Process Admin Inbox". In other words: A person that is a PROCESS specialist, not a technician.
To cut a long story short, think about such a functionality instead of reporting on wf-standard error management. You'll please your users and take away a burdon from the technical guys...
H.t.h.
Michael
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> jomyjoseph at smartsoftus.com
> Sent: Donnerstag, 10. März 2005 23:07
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: workflow error report
>
>
>
> Hi friends
>
> I'm developing a workflow error report(sales
> order/quotation). The inputs for this report are 1.date 2.
> sales doc no . 3.WF id 4.task id and the outputs are 1.sales
> order no. 2 created by 3.work item id , 4.failed task id , 5.
> reason for failure 6. timestamp of failure.
>
> There the real challenge I'm facing is 'reason for failure'
> i know the tables SWFRLMSG and SWFRLERR. But i don't know how
> to you them. Can anyone give me some inputs?. As I'm new to
> workflow you sug. fill be very helpful
>
> Thank you
>
> Austin Blobe
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
More information about the SAP-WUG
mailing list