Access in workflow container to method exception outcome (code and message)

Michael Pokraka workflow at quirky.me.uk
Mon Mar 24 08:39:42 EST 2003


Hi Fred,
That's roughly what I gathered. Though I've done similar things in the past where I just ended up checking for any exception and sending the user an "BUS9999.EDIT" task with a description "Please post blahdiblah manually", all were happy with that - it just means that the actual problem only becomes apparent in the transaction itself...
 
Cheers
Mike
 
On Mon, Mar 24, 2003 at 02:00:04PM +0100, Fred Lunaspa wrote:
> Mike,
>
> I want to display the error code and the message in a dialog task that
> provides the user the functionality to manually do the posting (or deletion)
> of the invoice. So I'll copy the method and bind the error code and message
> to the task/workflow. Thanks for your advise!
>
> Regards,
>
> Fred
>
>
>
>
>
>
> >From: Michael Pokraka <workflow at quirky.me.uk>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: Access in workflow container to method exception outcome (code
> >and message)
> >Date: Mon, 24 Mar 2003 11:05:49 +0000
> >
> >Hmmm, I see the problem. It builds a nice fancy message that just gets
> >returned as the workflow error.
> >I don't know if this is feasible, but may work if you copy the task and
> >define it as a dialog item. Thus if the original fails, reroute the new
> >("dialog") version to a user. They execute and get the error message
> >displayed....
> >
> >The other alternative (not so nice) is to copy the method into a new one
> >and fill the container with the message using SWC_SET_CONTAINER etc. In
> >short this will involve some ABAP and a delegated subtype of ZBUS2081.
> >The task needs to have an element - type BAPIRET works well - as well as
> >the WF, and then you can just bind it back.
> >
> >Cheers
> >Mike
> >
> >
> >On Mon, Mar 24, 2003 at 11:23:37AM +0100, Fred Lunaspa wrote:
> >> Hello,
> >>
> >> Can someone tell me how to pass the error no./message back to the flow
> >in a
> >> container element? I'm using standard SAP (4.6C) business object BUS2081
> >> (invoice), method PreliminaryPost. This method has one exception
> >defined:
> >> 1001 BUS2081 00 398 & & & &.
> >>
> >> When looking at the task I do not have the option to define the binding
> >from
> >> the method to the task (no parameters defined).
> >>
> >> Regards,
> >>
> >> Fred Kouw
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> >From: Michael Pokraka <workflow at quirky.me.uk>
> >> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >> >To: SAP-WUG at MITVMA.MIT.EDU
> >> >Subject: Re: Access in workflow container to method exception outcome
> >(code
> >> >and message)
> >> >Date: Thu, 20 Mar 2003 12:50:38 +0000
> >> >
> >> >Hi,
> >> >Pass the error no./message back to the flow in a container element.
> >> >
> >> >Though why you need to do this may be a valid question: Why not raise
> >> >different exceptions and model different outcomes based on these?
> >> >
> >> >Cheers
> >> >Mike
> >> >
> >> >On Thu, Mar 20, 2003 at 01:03:41PM +0100, Fred Lunaspa wrote:
> >> >> Hello,
> >> >>
> >> >> My method has an exception defined. When this exception occurs an
> >> >outcome of
> >> >> my step is 'raised' (error occurred). Can someone tell me how to have
> >> >access
> >> >> to the error code and error message in my workflow (i.e. in the tasks
> >> >> description and/or workitem text)?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Fred Kouw
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> _________________________________________________________________
> >> >> MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
> >>
> >>
> >> _________________________________________________________________
> >> Hotmail en Messenger on the move
> >> http://www.msn.nl/communicatie/smsdiensten/hotmailsmsv2/
>
>
> _________________________________________________________________
> MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
 


More information about the SAP-WUG mailing list