Outbound Interface Scheduling and File Delivery

The easiest and most common way to schedule a Blitz Report is to run it once from the run window with all parameters set correctly, and then navigate to View > Requests to copy that submitted concurrent request . You then update the schedule frequency and configure the Oracle standard delivery options , . These options natively support sending the report output as an email attachment, uploading it to a WebDAV cloud storage location, or sending it to an FTP destination, making it ideal for interface requirements .

By default, when using Oracle’s standard delivery options for scheduled Blitz Reports, the system automatically suppresses the delivery of an empty output file (zero rows) , , . If your interface requirements actually demand that empty files *must* be sent, you can override this behavior by setting the profile option ‘Blitz Report Suppress Empty File Delivery’ to ‘No’ , .

When manually submitting the ‘Blitz Report’ concurrent program, you must populate the report parameters starting from argument 16 onwards . Crucially, the values must be entered in exactly the same order as they appear on the Blitz Report run window . For instance, if ‘Ledger Name’ is the second parameter on the form, its value must be entered into Parameter2 (which corresponds to Argument 17 of the concurrent request) .

Yes, the default email subject is stored in the FND message `XXEN_REPORT_EMAIL_SUBJECT` . You can modify this message text, or create a new custom message, using placeholders like `&REPORT_NAME` and `&ROW_COUNT` for automated replacement at run-time . If you create a custom message (prefixed with `XXEN_REPORT_EMAIL`), you must update the profile option ‘Blitz Report Email Subject Message’ to point to your new message name .