Home » Applications » Oracle Fusion Apps & E-Business Suite » FND_CONCURRENT.WAIT_FOR_REQUEST (Oracle 10g)
FND_CONCURRENT.WAIT_FOR_REQUEST [message #343434] Wed, 27 August 2008 05:11 Go to next message
spmano1983
Messages: 269
Registered: September 2007
Senior Member
Hi,

I am using the following codes. I am submitting one reprt first.
after that i am calling FND_CONCURRENT.WAIT_FOR_REQUEST to sleep.

But the second request is called before first request completed.

I need that, first request should completed, then only the request request should start. How can i achieve this?? any ideas?? Please find the code below which i am using...

L_REQ_ID := FND_REQUEST.SUBMIT_REQUEST
             ('GECA',
              'XX_CWB_IND_LETTER
	      '',
	      '',
	      FALSE,
	      OHR_LOOP.OHRID,
	      P_FROM_DATE,
	      P_TO_DATE
 	     );

IF FND_CONCURRENT.WAIT_FOR_REQUEST(
 		  REQUEST_ID=>L_REQ_ID,
 		  INTERVAL=>60,
 		  MAX_WAIT=>0,
 		  PHASE =>L_PHASE,
 		  STATUS=>L_STATUS,
 		  DEV_PHASE=>L_DEV_PHASE,
 		  DEV_STATUS=>L_DEV_STATUS,
 		  MESSAGE=>L_MESSAGE )  THEN

L_REQ_ID1 := FND_REQUEST.SUBMIT_REQUEST(
             'GECA',
	     'XX_CWB_IND_EFMS_INTER_CONC',
	     '',
	     '',
	     FALSE,
	     L_XML_FILE,
	     L_XML_DEST,
             L_PDF_FILE,
	     L_PDF_DEST
            );



Thanks
Re: FND_CONCURRENT.WAIT_FOR_REQUEST [message #343700 is a reply to message #343434] Wed, 27 August 2008 18:29 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
Have you tried commit after the first request submission?
By the way why don't you use a request set in this situation?

By
Vamsi
Re: FND_CONCURRENT.WAIT_FOR_REQUEST [message #343773 is a reply to message #343434] Thu, 28 August 2008 02:07 Go to previous messageGo to next message
spmano1983
Messages: 269
Registered: September 2007
Senior Member
Hi Vamsi,

Thank you very much. COMMIT logic is working fine.

But can you tell me why the COMMIT is necessary here??
Re: FND_CONCURRENT.WAIT_FOR_REQUEST [message #344455 is a reply to message #343773] Fri, 29 August 2008 19:52 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
I tried a lot to find out some documentation on that. But didn't get any.

By practice I found that or someone told me:
commit is necessary after you submit request using fnd_submit.submit_request.

You can also search the forum "fnd_submit.submit_request commit".

By
Vamsi
Re: FND_CONCURRENT.WAIT_FOR_REQUEST [message #346052 is a reply to message #343773] Fri, 05 September 2008 14:11 Go to previous message
annagel
Messages: 220
Registered: April 2006
Senior Member
spmano1983 wrote on Thu, 28 August 2008 02:07
But can you tell me why the COMMIT is necessary here??



COMMIT is required after submitting a request because all the SUBMIT_REQUEST procedure is doing is inserting data into the relevant tables. Just like any other data insert, until a COMMIT is issued that data is only visible from your session. As a result the concurrent manager which is actually responsible for running the job is not able to see it and does not start it.
Previous Topic: Requisitions
Next Topic: assign the responisibilties in query mode
Goto Forum:
  


Current Time: Fri Dec 09 10:08:56 CST 2016

Total time taken to generate the page: 0.07958 seconds