How To Schedule a Concurrent Request on completion of a Spawned Request

Question

As soon as the concurrent request submitted through Oracle Form(Consolidation Transfer)is completed we need to schedule another Concurrent Request which had to be kicked off automatically on completion of the First concurrent request. Since, the First concurrent request of Consolidation Transfer is a Spawned Program, the request set could not be created, to kick off the second concurrent program.
I would Appreciate if anyone can advise any solution to achieve this objective.

Answer 1

Hi Harish,
Doesn't matter what you need to do all you need is the hook!
a) Nice. Force the request to print and use print driver to call CONCSUB to submit your new "child" request
-- Since the Consolidation Trasnfer concurrent request could only be submitted through Consolidation Trasnfer Form only, I am not sure how we can do Force Print for this request.
GR: Set printer and style on concurrent program definition. Set profile option "Concurrent:Report Copies" to 1 (even by Forms Personalization if you want to). Sorted. Still think this is the best option.
c) Abstraction. Replace the C executable with a shell script that takes arguments and calls the C program and then submits new "child" request via CONCSUB
-- Appreciate, if you can elaborate this option. I think we can try this, with the help of your detailed input.
GR: Change the executable on the concurrent program to a host shell script under your mods application. Initially just get the shell script to capture program call and arguments. Run the program to get arguments. Next iteration, change shell script to call the C program from your shell script with correct arguments. Verify okay. Next iteration do the same plus call CONCSUB to submit request / set.
d) Nasty. Trigger on fnd_concurrent_requests to call new "child" request via fnd_request.submit_request - NB: very unsupported! Make sure trigger doesn't raise an exception.
-- On completion of the Consolidation Transfer concurrent request, we tried to submit the request set using the Trigger on Consolidation History table and/or fnd_concurrent_requests table. But it is entering into infinite loop.
GR: Need to use trigger condition to capture update of status_code to C (Completed) and other codes e.g. Warning. Personally I'd avoid this option because you have others! Although once I did use this method when I wanted absolute transparency :-)
Update: Changed "Print: Copies" to "Concurrent:Report Copies"
Regards,
Gareth
Edited by: gareth.roberts on Dec 8, 2008 4:55 PM