Home › Discussions › Questions & Answers › Implementing Incremental Logic for Scheduled Blitz Reports
Customer · · Questions & Answers · 5 replies
We need to schedule a Blitz Report as an outbound interface that only transfers incremental data changes since the last run. How do I configure the report parameter’s SQL text to achieve this dynamic filtering?
You can restrict the query to records modified since the previous scheduled request run by using a specific parameter SQL logic that references the concurrent request history. An example uses the request’s actual start date from the previous run.
Can you provide the core logic structure for this parameter SQL restriction?
A successful example uses a restriction like: `rctla.last_update_date >= (select fcr0.actual_start_date from fnd_concurrent_requests fcr, fnd_concurrent_requests fcr0 where fcr.request_id = fnd_global.conc_request_id and fcr.parent_request_id = fcr0.request_id)`.
If a scheduled report runs but retrieves zero data rows (no changes occurred), will an empty output file still be sent?
By default, if a scheduled report retrieves zero data rows, Blitz Report suppresses the delivery of an empty output file. If you need empty files to be sent, you must set the profile option ‘Blitz Report Suppress Empty File Delivery’ to ‘No’.
Sign in with LinkedIn or Google to take part.
