How to Run a Request Set on specific days and at specific hours

Question

Hi community,
The question is simple, how to rin a Request Set on Specific Days and at Specific hours?
Let me explain the scenario.
E-Business Suite, Release 11.5.9.
We have a request set under Sysadmin user. This Request set is running 24x7, during all year, and we want to restrict the execution from Monday to Friday since 08:00 a.m. to 20:00 p.m. in order to increase the productivity of our system and more over, to avoid the size increase of a table (OE_EXPOSURE_INTERFACE)
The Request Set includes 5 Requests:
10. Workflow Background Process.
20. GUZMAN: Cálculo metodo pago en pedidos.
30. GUZMAN: Exposición de crédito externo.
40. Credit Exposure Import.
50 Initialize Credit Summaries Table.
As you can see three of them are standar Oracle Order Management Processes and two of them are custom Oracle Order Management Processes; and the requests must be executed in that order.
We have just thinking about to create a Custom Manager with a workshift from Monday to Friday since 08:00 a.m. to 20:00 p.m., and include the requests as specialization rules or assigning those request to a Request Type and then include that Request Type as specializated rule, but this does not assure us that the request will be executed in that order.
Any suggestion?
Thanks a lot for your answer in advice.
Luis.

Answer 1

Hi Anchorage,
It could be a solution, but not the exact solution that we want. Let me say why.
With the Request set we have the security that each concurrent request is executed when the prior one finishes; is that to say 20, does not begin till 10 finishes, and 30 does not begin till 20 finishes and so on. The most critical concurrent requests are 40 and 50, cause those are the ones that import an external credit exposure in the OE_EXPORURE_INTERFACE table (40) and are the ones that delete those external credit exposures imported (50). The problem is (and we do not know why) that these actions makes grow the size of the table and each time the 40 and 50 processes takes more minutes to finish. That's why we need to truncate the table in order to avoid the excesive grow of itself.
Making each process independent, with a begining time and hoping and expecting that the following one does not begin till the prior one ends is not an admisible or realizable solution due to the problem with the 40 and 50 processes.
So at the end, we need a request set in order to know that each one began when the prior one ends.
And Due to in order to truncate the table, as I said before, the processes that have a relationship whit it, must be stopped (just the 40 and 50 processes) prior to the truncation.
So as you see, it is difficult, very difficult.
Regards.