Submitting Blitz Reports via FND_REQUEST API

To submit a Blitz Report using `fnd_request.submit_request`, you must first initialize the application context using `xxen_report.apps_initialize` (User Name, Responsibility Key, Resp. App. Short Code) , . The request is submitted under the application short code ‘XXEN’ and program name ‘XXEN_REPORT’ . The arguments must be precisely mapped: Arguments 1 through 15 are reserved for the report name and runtime options (Email, Output Format, Row Limit, etc.), while the user-entered report parameters start from Argument 16 onwards .

Yes, for easier, name-based submission, you should use the Blitz Report concurrent program API `XXEN_API.REPORT_SUBMIT_CONCURRENT_` . This procedure allows you to reference the report name, parameter names, and template names by name, instead of relying on the argument’s sequential position . After calling `REPORT_SUBMIT_CONCURRENT_` to initiate the run ID, you use `XXEN_API.SET_PARAMETER_VALUE_` and `XXEN_API.SET_RUNTIME_OPTION` to set the specific values by name , .

You can specify several runtime options . Key options include: `TEMPLATE_NAME`, `EMAIL`, `OUTPUT_FORMAT`, `ROW_LIMIT`, and `TIME_LIMIT` . Other options like `OUTPUT_FILENAME`, `ADDITIONAL_OUT_DIR_DB`, and `CUSTOM_POSTPROCESS` can also be set, allowing you comprehensive control over the execution and delivery of the concurrent request .

If `fnd_request.submit_request` returns 0, indicating failure, you retrieve the detailed Oracle error message by calling `fnd_message.get` . This message should be displayed to the user for debugging purposes . You must remember to commit the transaction after a successful submission that returns a request ID greater than 0 , .