UWL Batch Processing

[Former Member]

The UWL How-to Guide talks about batch processing in the UWL (via Submit Decisions action), and has examples for three different handlers: user decision, terminating event, and container update.

I want to provide a new batch processing view for requisition release using SAP-supplied standard task TS00007986. The method used is BUS2009.SingleRelease, which in turn calls transaction ME54. I'm having trouble figuring out how to use the UWL batch processing capability for this type of object and method. None of the handlers seems exactly appropriate.

We are running EP6 SP2 Patch 31 and a 4.6C R/3 system.

My guess is that I will have to modify the existing workflow to add a 1-from-2 split for this step. The new leg would include a listen for event step (requiring a new event for BUS2009) and a new step (and BUS2009 method) to perform the release in background. With these changes to the business object and workflow definition made, I could then use the terminating event handler.

Is this correct?

Thanks for any help!

John

[Jocelyn_Dart · Accepted solution]

Hi John,

You are correct in thinking that your workflow/task needs to be able to respond correctly to whatever multiple exeuction "batch processing" mechanism you use, as is usual with any multiple execution scenario regardless of which workflow inbox you use.

Of course you should copy the workflow and modify your copy rather than change the standard workflow. Its usual to treat the standard workflow as a starting point.

Your main problem is going to be to find a background routine for updating the release step on the requisition - as this needs to be provided by the application. The rest is simple enough to include in the workflow.

In 4.6c you should have function module BAPI_REQUISITION_RELEASE, check it works ok in your release/support pack level, as this should do what you need.

Rather than have a 1 from 2 split you could also add a new terminating event to your task TS00007986. However its six of one half a dozen of the other as you still need to include the background update after the event is raised.

You'll probably also need two terminating events - one for approval and the other for rejection.

Regards,

Jocelyn