A Crystal Report using a procedure from a custom PL/SQL Utility package as its data source loads and renders correctly when previewed directly in the Crystal Reports designer, but fails with 'The table could not be found' when run through the actual application/Crystal Web Service, even with EXECUTE granted on the package to both IFSSYS and IFSPRINT. What's the actual limitation here?

All FAQ questions / Reporting and analytics

Answer

PL/SQL Package procedures aren't supported as a Crystal Report data source through the IFS reporting framework at all — this is a documented design limitation, not a permissions or configuration gap, which is why it can appear to work in the standalone Crystal designer (which doesn't go through the same framework path) but fails when run through the application. The supported alternative is a genuine Oracle Stored Procedure (not a procedure that's a member of a package) — restructure the reporting logic as a standalone stored procedure instead of a package procedure, and grant the necessary execute permissions on that stored procedure.

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