Fw: qRFC update failure

Kris WUG kris_wug at hotmail.com
Thu Apr 1 15:05:51 EST 2004


> ----- Original Message -----
>> From: "Michael Pokraka" <workflow at quirky.me.uk>
> To: <SAP-WUG at MITVMA.MIT.EDU>
> Sent: Thursday, April 01, 2004 9:54 AM
> Subject: Re: qRFC update failure
>
>
> Hi Kris,
> Could you explain why this has to be asynch? Asynchronous and serial are a
> bit like oil and water, so it may be worth rethinking that part.
> Perhaps BAPI_SALESORDER_CREATEFROMDAT2 might be better suited?
> Cheers
> Mike
>
> Kris WUG wrote:
> > Hello experts.
> >
> > I appreciate any help related to this issue below.
> > Below issue is more ABAP related rather than a workflow.
> >
> > In the process of implementing qRFC with inbound queues, when a function
> is
> > called with the addition IN BACKGROUND TASK (eg., to create a sales
> order),
> > the caller program does not receive any importing parameters or return
> data
> > as to whether the LUW which was executed asynchronously was a success or
a
> > failure.  In the example above, the only sure way is to check the
database
> > table entry to see if the sales order has been created.  To achieve
> > serialization, the inbound queue needs to be stopped if there are any
data
> > errors.  Without knowing the results of the executed LUW, the next LUW
is
> > executed if the queue is not stopped.  It appears that it may not be
> > possible to implement serialization in inbound queues as it is not
> possible
> > to get any return data.
> >
> > Is there any way to trigger an event or capture the result of success
and
> > failure
> > of a qRFC called  IN BACKGROUND TASK(not workflow background task) ?
> >
> >
> > Thank you in advance.
> > Kris.
> >
> >
>
 


More information about the SAP-WUG mailing list