Workflow errors not reported in SAP mail?

Fri Jul 18 04:13:43 EDT 2003

Sergey,

First of all, Phil's and your explanation are very clear. I understand the difference between a workflow error
and an application error that cannot be handled by the workflow if you do not 'define' the error during modeling
of the workflow.

The workflow instance actually got status 'Error' and the SWWERRE job did NOT notify me (the workflow
administrator.) SWWERRE is scheduled to run at an interval of 20 minutes. As you stated, the administrator
should be informed of workflows in error by SWWERRE, which doesn't occur in this case (other errors are reported
in my SAP inbox). So I still think I have a problem.

I use standard method EDIT of object BUS2081, for which no exception for this error is defined (which I think is
logical, otherwise all methods should return an exception in case the user has no authorisation to execute the
transaction called from the method). I was able to use SWPR (Restart work item after error) to change the status
of the workflow instance to ready.

Regards,

Fred Kouw

"Breslavets, Sergey" wrote:

> Fred,
>
> does your workitem actually gets "Error" status after the Application Error
> happens in the called transaction, or it remains "Stated" and another error
> message is added to the WF technical log.
> In the first case the SWWERRE job must notify you (as for any workitem in
> Application or System Error status).
> In the second case, this is not an error from the workflow point of view. From
> the workflow perspective, the task (workitem) was not completed by user due to
> some reasons beyond the control of the Workflow Manager (cancelled workitem,
> transaction errored out, etc.) - it does not receive any error code back from
> transaction and does not know why it was not completed. (Phil described it
> perfectly in his email).
> To make workflow manager recognize particular application errors use
> exceptions(or terminating events) in the task method and model outcomes in your
> workflow. This way you'll let workflow know what's happenned and how to react to
> it.
>
> Thanks,
> Sergey
>
> -----Original Message-----
>> From: Kouw, FA - SPLTX [mailto:fa.kouw at td.klm.com]
> Sent: Thursday, July 17, 2003 2:31 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow errors not reported in SAP mail?
>
> Thank you for sharing your thoughts Phil !
>
> For most part I agree with you, but on one point not:
>
> The workflow goes into error after the user tries to execute the work item, so I
> have a workflow (in) error, caused by an error in the application (in this case
> a lack of authorization). An error in a workflow should be handled (in this case
> restarting the workflow in error after the correct authorizations have been
> assigned) and in my opinion the workflow administrator should be notified of
> workflows in error.
>
> The workitem is routed to the right person: we just went live and it won't
> surprise you that we bump into many authorization issues. The user should be
> assigned the right authorizations by the team responsible for authorizations.
> This team is notified
> by me because I monitor the workflows in error (the workflow administrator).
>
> Regards,
>
> Fred
>
> "Soady, Phil" wrote:
>
> > Why should a dialog error in a called transaction be a "workflow problem" ?
> > Why not consider it an "application error".
> > If the specific issue was Authorization. I would say you have an
> "authorization problem".
> >
> > When a dialog method calls a transaction, the transaction gets control,
> > the transaction does its stuff, the control passes back to the point
> > after the call in the method. The workflow view is situation 100% ok.
> > If the fact that an authorization error occurred is to be considered
> > a workflow problem, then that fact must be captured in the workflow.
> > Note: Unless an error or exception is raised in the dialog method itself,
> > then the call to this dialog method is considered successful since
> > it has successfully called a transaction and gained the control again.
> >
> > Why not treat it as an authorization error ?
> > Ie the System trace ST01 or individual check SU53
> > will show it as an auth error.
> >
> > Workflow has done its job... the Security administrator is behind the
> > game, or the workflow builder didn't match true business requirements.
> > Why route the workflow to someone with no authorization ?
> >
> > If you know what authorizations are causing troubles in a specific
> > situation, you could always check these directly in the method
> > before calling  the transaction. Or Try to check the current Sy-msgty
> > after the call and then throw an error (temp or application) inside the
> method.
> >
> > But surely this issue is best handled elsewhere. Otherwise you might be adding
> > lots of code to methods.
> >
> > My question: Why send a workitem to someone when they have no auth in the
> first place.
> > Surely this has been sent the wrong person? Then the workflow
> > doesn't match the business process. The workflow should have been sent some
> where
> > else.  Eg Put some form of auth check inside a custom RULE (AC 9999999) as an
> > addition to role resolution.
> >
> > OR If they are the right person....
> > Give them the authorization.
> >
> > My view anyway....
> >
> > Phil Soady
> > Senior Consultant
> > Business Technologies
> > SAP Australia
> > * : 0412 213 079
> > * : phil.soady at sap.com
> >
> > -----Original Message-----
> > From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> > Sent: Monday, July 14, 2003 8:12 PM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Re: Workflow errors not reported in SAP mail?
> >
> > Hi,
> > I've noticed thia in a 4.6c system, found and applied some notes to that
> effect, but still many errors are not mailed. As I usually work with
> SWI2_DIAG/ADM1, thia hasn't been a priority so I didn't really get too deeply
> into the cause. Cheers Mike
> >
> > On Mon, Jul 14, 2003 at 11:28:04AM +0200, Kouw, FA - SPLTX wrote:
> > > Hello,
> > >
> > > I have a situation in which there are a few workflows in error
> > > (authorization problem so the user can't execute a synchroneous
> > > method) that are NOT reported via SAP mail in the SAP Business
> > > Workflow inbox. The errors are (of course) visible when using 'SWI1 -
> > > Selection report for workitems'.
> > >
> > > Can someone tell me if this is what the system is supposed to do?
> > >
> > > Regards,
> > >
> > > Fred
> > >
> > >
> > > **********************************************************************
> > > This e-mail and any attachment may contain confidential and privileged
> > > material intended for the addressee only. If you are not the
> > > addressee, you are notified that no part of the e-mail or any
> > > attachment may be disclosed, copied or distributed, and that any other
> > > action related to this e-mail or attachment is strictly prohibited,
> > > and may be unlawful. If you have received this e-mail by error, please
> > > notify the sender immediately by return e-mail, and delete this
> > > message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> > > subsidiaries and/or its employees shall not be liable for the
> > > incorrect or incomplete transmission of this e-mail or any
> > > attachments, nor responsible for any delay in receipt.
> > > **********************************************************************
> > >
> > > ______________________________________________________________________
> > > _______________________
> > > This outbound message from KPN has been checked for all known viruses by KPN
> IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl
> > >
> ________________________________________________________________________________
> _____________
> >
> >
> ________________________________________________________________________________
> _________
> > This inbound message from KPN has been checked for all known viruses by KPN
> IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >
> ________________________________________________________________________________
> _____________
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have received
> this e-mail by error, please notify the sender immediately by return e-mail,
> and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> subsidiaries and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor responsible
> for any delay in receipt.
> **********************************************************************
>
> ________________________________________________________________________________
> _____________
> This outbound message from KPN has been checked for all known viruses by KPN
> IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> ________________________________________________________________________________
> _____________
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________

**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************

_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________