BAPI CALL IN BACKGROUND TASK

Sudhir Pargaonkar pargov at gmail.com
Wed Mar 26 11:10:03 EDT 2008


Hi Pratima,

if the BAPI fails due to the lock, in your method, you can create a
temporary error.. system will automatically try to execute the step again.
You need not inform the user.

Regards,
Sudhir
(713) 922-9016

2008/3/26 Pratima Poojary <pratima_poojary at yahoo.com>:

> Hi,
>
> We have a sales order workflow for exceptional demand.
> In one of the steps of the workflow,the corresponding task executes in
> background.
>
> Sales Order Change BAPI is called within this task.
> Now the problem is that in case the sales order is locked for execution by
> some other user, the BAPI call returns a message of type 'E'.
> Currently we send a mail to the concerned people to indicate that the
> sales order change has failed. However the users are concerned, since there
> is no immediate feeback on the errors.
> Is there any way that the user's can be informed instantly that an error
> has occured and also a retry option so that the BAPI call can be reexecuted
> at a later time.
>
> Regards,
> Pratima Poojary
>
> ------------------------------
> Never miss a thing. Make Yahoo your homepage.<http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080326/7268199d/attachment.htm


More information about the SAP-WUG mailing list