A Quick Report built on a pipelined result from a custom PL/SQL package function (e.g. `SELECT * FROM TABLE(my_custom_api.Get_Something(...))`) runs fine directly and previews correctly, but fails specifically when using the 'Export to Excel' option — what's different about that export path?

All FAQ questions / Reporting and analytics

Answer

Export to Excel generation runs under a different execution context than a normal Quick Report preview, and specifically needs an explicit EXECUTE grant on the custom package to the IFSSYS role — GRANT EXECUTE ON <owner>.<Custom_Package_API> TO IFSSYS;. Standard/built-in APIs already carry this grant, which is why only custom packages tend to hit this; granting EXECUTE to IFSSYS on the specific custom package used in the pipelined query resolves the Export to Excel failure without needing any cache refresh or other change.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions