Oracle GL v9 + Concurrent Manager problem

  Please bear with me here as I am new to Oracle Financials and Concurrent Manager.

  The site I am working at runs multiple journal postings against an Oracle 7 database using Concurrent Manager(?). The problem we are having is that when one job fails in the CM, it gets tagged with an 'I' status code, along with the rest of the following jobs and the CM bombs out. We have a job that will start the CM back up if it fails (running in cron every 15 min.), but it starts with the first job in the que with an 'I' status code, i.e. the bombed out posting job.

  When the job fails, we can get the REQUEST_ID from the FND_CONCURRENT_REQUESTS table, identifying the CM request that failed. We need to find a way to join this ID back to the JE_BATCH_ID key in the GL_JE_BATCHES table, so that the batch in error can be tagged with a 'U' status (unprocessed), and the CM will get going again on the next job in the que, therefore allowing the rest of the processing for the night to continue.

  As I said, we know when the job fails, but must manually examine output logs for a key to join back to the batch in error to set it aside and let everything else process, but this would involve many midnight dial-in sessions, which I'm sure we all like to avoid!

  Anyone have ideas?

 Thanks. Mike. Received on Fri Jan 06 1995 - 07:59:34 CET