Search Results psb_end_of_report

Overview

PSB_PSBRPCAL_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite XML Publisher (BI Publisher) report "PSBRPCAL" — the Budget Report by Calendar associated with the Public Sector Budgeting (PSB) module. In EBS 12.1.1 and 12.2.2 the XML Publisher report definition is paired with a server-side PL/SQL package whose body implements the report-level triggers (Before Report, After Report, Before Parameter Form, After Parameter Form, Between Pages) and exposes report variables to the RTF template as bind parameters. The package therefore contains little business logic of its own; its primary role is to prepare NLS message strings, resolve the budget calendar name, and capture the concurrent request ID so that the XML template can render localized labels and effectively handle the "no data found" condition.

Key Procedures and Functions

The package exposes nine documented functions. The report trigger functions control the execution flow of Oracle Reports invoked from the concurrent manager. BEFOREREPORT is the substantive routine: it populates P_CONC_REQUEST_ID from FND_GLOBAL.CONC_REQUEST_ID, then resolves CP_CALENDAR by either assigning the "PSB_ALL" message when P_BUDGET_CALENDAR_ID is null or querying PSB_BUDGET_CALENDARS for the calendar name matching the passed ID. It also builds the localized strings C_NLS_NO_DATA_EXISTS and C_NLS_END_OF_REPORT through FND_MESSAGE.SET_NAME and FND_MESSAGE.GET using the PSB message dictionary. AFTERPFORM, BEFOREPFORM, BETWEENPAGE, and AFTERREPORT are placeholder trigger functions that simply return TRUE.

The remaining four functions are accessor (getter) routines that return package-level global variables to the XML template and report engine: C_NLS_NO_DATA_EXISTS_P returns the localized "no data exists" text; C_NLS_END_OF_REPORT_P returns the localized end-of-report text; P_CONC_REQUEST_ID_P returns the concurrent request ID; and CP_CALENDAR_P returns the resolved calendar name. These accessors are what the RTF template references as bind parameters (for example, to print the calendar name in the report heading or to display the no-data message).

Tables Accessed

Only one table is referenced through the APPS synonym: PSB_BUDGET_CALENDARS. The package performs a single SELECT of the NAME column, filtered by BUDGET_CALENDAR_ID, when the user has supplied a specific calendar at the report parameter form. When no calendar is supplied, the query is bypassed and the generic "PSB_ALL" message is used instead. No INSERT, UPDATE, or DELETE operations are performed, so the package is strictly read-only with respect to application data.

Usage Notes

PSB_PSBRPCAL_XMLP_PKG is not invoked directly by end users or by other PL/SQL packages — the metadata records zero referencing packages. It is called indirectly when the "Budget Report by Calendar" concurrent program is submitted (or when the request is run from an Oracle Forms menu), at which point the Oracle Reports / XML Publisher runtime fires the report triggers. The most significant diagnostic point is the message name PSB_NO_DATA_FOUND, which users frequently search for: when the query returns no rows, the BEFOREREPORT routine loads this message so the template can print a localized "no data found" line rather than failing. If a report returns blank output, the standard troubleshooting path is to confirm that valid rows exist in the PSB budget tables and that the PSB_NO_DATA_FOUND message is enabled and translated in the current session language. Because the package is generated, any customization should be applied to the underlying report definition rather than by manually editing this package body.