Home Discussions Questions & Answers Implementing Incremental Logic for Scheduled Blitz Reports

Implementing Incremental Logic for Scheduled Blitz Reports

Avatar photoCustomer November 20, 2024 at 1:38 pm

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?

Viewing 4 reply threads
  • Author
    Replies
    • Support November 22, 2024 at 7:16 am  

      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.

    • Avatar photoCustomer November 23, 2024 at 12:19 pm  

      Can you provide the core logic structure for this parameter SQL restriction?

    • Support November 25, 2024 at 2:42 am  

      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)`.

    • Avatar photoCustomer November 26, 2024 at 4:35 am  

      If a scheduled report runs but retrieves zero data rows (no changes occurred), will an empty output file still be sent?

    • Support November 27, 2024 at 8:17 am  

      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’.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: