Debugging Form Assignment Parameter Retrieval

The PL/SQL logic, typically executed in a `when-button-pressed` trigger on the EBS form, uses the `XXEN_API.CREATE_RUN_ID_` function to start a report instance, followed by conditional calls to `XXEN_API.SET_PARAMETER_VALUE_` , . For instance, you first check if the RFQ Header field is populated (`:rfq_header.rfq_number is not null`) before setting that parameter . Then, a nested condition checks if the line number is available (`:rfq_line.rfq_line_number is not null`) before setting the second parameter value , .

To trigger the file download, the PL/SQL procedure must call `XXEN_UTILS.DOWNLOAD_FILE` . This function requires the file ID, which is retrieved using `XXEN_API.REPORT_FILE_ID(l_run_id)` . Note that to use this functionality within a custom Oracle Form, you must ensure the `XXEN.pll` library is attached to your custom form , as `XXEN_UTILS.DOWNLOAD_FILE` is contained within it .

The most reliable way to identify the correct Form Name and Block Name is through the standard Oracle Forms interface . You navigate to the target form, go to the top menu, and select Help > About Oracle Applications > Current Form . This window provides the necessary Form Name and typically enough context to determine the Block and Item names for parameter referencing .

Yes, runtime options such as the template name can be set using the `XXEN_API.SET_RUNTIME_OPTION` procedure . You specify the option name (e.g., `’TEMPLATE_NAME’`) and the desired value . You can even set the value dynamically, for instance, by calling `XXEN_API.DEFAULT_TEMPLATE_` to retrieve the user’s default template for that report before executing .