Enhancement Request regarding sysdate usage in reporting and bursting query

srividhya-Oracle

Requirement: Customer has a specific window (around 8 pm UKT) where they schedule their report jobs daily. Business date parameter value is set to sysdate while scheduling.

Expectation: Reporting query and bursting query uses the same date (date on which the job starts).

Issue: On billing day, when data volume is high, the reports run for long ~5.5 hours. What is happening currently is that the reporting query is taking the date as of the job execution but the bursting query is crossing over to the next day and resolving the date as the next day's date. This is causing issues - job is showing successful, xmls are generated, but bursting query doesnt create any files.

What is needed: While, as a workaround, customer is trying to run this report the next day with sysdate-1 as the parameter value to complete the reports with same date, if there is an option to specify what date should be used when there is a crossing over to the next day from the scheduled date, it will be helpful.