Is there any specific reason why you want to run 40 times, instead run the program with out any parameter so that all the 40 scenarios are covered and populated in one output.
If left blank, it will not break out the report by that parameter nor is there anything on the report that indicates which values are for that parameter say 1 as opposed to which values on output is for parameter 2. I think the only way to go is to have it run 40 times but I was just looking for ideas on making this easier....
Thanks for your help!
That is not a good way of using the parameter via a request set. If this gets scheduled in production you would be created more number of data in fnd_cuncurrent_requests tables for no use.
You have to utilize the parameter and request set functionality to the most, by making your code appropriate.
What kind of report is this ? PL/SQL ? RDF ? XMLP ?
It's a standard Oracle report (Invoice Print Selected Invoices report) but customized to add one more parameter. Now the requirement is to run one report per value on this new parameter-values on the parameter are about 40.
Does it need to be run 40 times ? Or can't you create a lookup/valueset with 40 values and have a cartesian join with the if no parameter is passed ?
Will you always have 40 values for the parameter or it could increase.
You could create another custom program which loops your 40 values and submit from the PL/SQL program.
For this you will need to create a custom program which actually submits the program 40 times in back ground.
The output of your wrapper program should display the request id.. I could think of this as this avoids 40 submissions apart from Request set=
Schedule the request set with the values required for each value 40 times.