Search Results psb_psbrpcal_xmlp_pkg

Overview

PSB_PSBRPCAL_XMLP_PKG is an Oracle Application Object Library (AOL) report-generation package in the APPS schema. It belongs to the PSB module, which supports Oracle Public Sector Budgeting (also referred to as Enterprise Performance Foundation budgeting within the E-Business Suite 12.1.1 and 12.2.2 release streams). The name embeds the "XMLP" token, which identifies the package as the PL/SQL support unit automatically generated and registered against an Oracle XML Publisher (BI Publisher) report definition. The package is classified as OTHER in the ETRM metadata, indicating that it is not an open public API for external integration; rather, it is an internal support component consumed by the concurrent program framework when the associated budget calendar report is executed.

The primary business purpose is to satisfy the data and formatting requirements of a report that presents budget calendar setup information. The package orchestrates the standard report lifecycle by supplying initialization values, resolving the concurrent request identifier, handling format-trigger break logic, and emitting the NLS message tokens that the report template resolves at runtime. Because the package is marked VALID in the documented ETRM extract, its compiled state is consistent and usable in the supported EBS environments.

Key Procedures and Functions

The metadata documents nine named program units within the package. Their responsibilities align with the report-trigger framework used by XML Publisher concurrent programs:

• BEFOREREPORT — Executed before the report query runs. It initializes session-level report variables and prepares the runtime environment for the extract.
• BEFOREPFORM — Executed before the report body is formatted, establishing values needed by the formatting phase.
• AFTERPFORM — Executed after the report body has been formatted, used to finalize format-stage processing.
• BETWEENPAGE — Invoked between logical page boundaries, supporting pagination or break control across report sections.
• AFTERREPORT — Executed after the report execution completes, handling cleanup of report-level state.
• C_NLS_NO_DATA_EXISTS_P — Returns the translated NLS text emitted when the extract yields no qualifying budget calendar records.
• C_NLS_END_OF_REPORT_P — Returns the translated NLS text appended at the conclusion of the report output.
• P_CONC_REQUEST_ID_P — Supplies or exposes the concurrent request identifier, allowing the report to associate its output with the parent concurrent request.
• CP_CALENDAR_P — Represents the calendar parameter used to drive the report query, allowing the run to be scoped to a particular budget calendar.

Tables Accessed

The ETRM metadata documents a single table reference: PSB_BUDGET_CALENDARS, accessed through an APPS synonym. This table stores the definition of budgeting calendars, including the organization and calendar configuration used when budget periods are generated. The report package queries this table to populate the calendar selection and to display the calendar-level attributes rendered on the XML Publisher output. No other table dependencies are documented.

Usage Notes

PSB_PSBRPCAL_XMLP_PKG is not intended for direct invocation by end users or custom code. It is registered as the supporting PL/SQL package for a concurrent program that is defined against an XML Publisher report template. The package is therefore invoked by the Concurrent Manager during report execution, following the standard sequence: BEFOREREPORT, BEFOREPFORM, AFTERPFORM, BETWEENPAGE at page breaks, and AFTERREPORT at completion.

Because the package references only SYS.STANDARD and is referenced by no other packages according to the documented dependency listing, its blast radius for upgrades and patching is narrow. Customization should occur through the XML Publisher template and the underlying concurrent program definition rather than by modifying this generated package; direct edits would be overwritten by applied patches. The NLS-related units confirm that report text should be sourced from message dictionary entries to preserve multilingual support across EBS 12.1.1 and 12.2.2 installations.