When you define a concurrent request set you have to either specify the default parameters for a program in the request set definition, or set them at the point of submitting.
Can you please give an example.
I am new to oracle applications.
But what I exactly want is I have to run the report in a request set as well as manually.
If there is any mode then I want to handle that in my PL/SQL package.
Because while running in the request set the parameters should have NULL values and while running manually the parameters are mandatory.
If possible can you suggest me how to handle this
So... when you run manually you want to force parameters, but when running as part of a request set you need all parameters to be empty?
If it was me I'd just create a separate concurrent program definition for each, one with the parameters set as mandatory and one with them not. Add the former into the request set and the latter into the request group for the responsibility to run manually.
You are right, even I would do that.
But the business want it in one single report.
The only option then is to make your report parameters none-mandatory and then set them in the request set parameters definition (see above screenshot) - Uncheck the "modify" option which will prevent the user from changing them when submitting the request. In fact, you might want to choose to not even display them.
In the concurrent program I have not enabled the "required" check box for the parameters.
In the cursor I am using NVL of parameters and included a validation for manual.
If all the parameters are null then l_status = 'n'
else if all the parameters are not null then l_status ='s'
update staging table status ='ignore'
if l_status in ('s','n')
then open cursor
Since I had no choice I had to handle everything in PL/SQL only.