A report generated via custom PL/SQL code (building the report and print job manually through the Archive/Print Job APIs) shows different data values than the exact same report run manually through the standard right-click Execute action on the same record. What's a good way to actually diagnose the difference?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Compare the actual underlying data rows in the report's own _REP view for both runs, rather than just comparing the two final rendered PDF outputs — there will be multiple rows of data per report result key/job in that view. Differences visible directly in the _REP view's row-level data for each specific result key are much easier to pin down than trying to spot differences purely by eyeballing two PDF outputs, which adds an extra layer of potentially misleading formatting/rendering noise on top of whatever the actual underlying data difference turns out to be.

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

← Browse Developer Studio, deployment, and upgrades questions