Search Results psb_psbrpprm_xmlp_pkg

Overview

PSB_PSBRPPRM_XMLP_PKG is an Oracle EBS PL/SQL package owned by the APPS schema. The "_XMLP_PKG" suffix is the standard Oracle naming convention for packages generated automatically when a report is authored using Oracle XML Publisher (BI Publisher). The package encapsulates the report-level and formula-level PL/SQL logic that a BI Publisher concurrent program requires at runtime: it exposes entry points invoked at specific lifecycle stages of report execution so that report-specific data, formatting attributes, and NLS literals can be supplied to the XML Publisher engine.

The package is associated with the Public Sector Budgeting module (the "PSB" prefix) and specifically with the budget group parameter report identified by the "PSBRPPRM" token, which aligns with the PSB_BUDGET_GROUPS table accessed by the package. The status of the object is VALID, indicating the compiled package and package body reside in the APPS schema and are successfully resolved against their dependencies. The package is classified as "OTHER" in the ETRM API classification, meaning it is not a published or supported integration API; it is internal report machinery.

Key Procedures and Functions

ETRM documents fifteen procedures and functions in this package. They fall into distinct groups reflecting the XML Publisher report lifecycle:

• BEFOREREPORT / AFTERREPORT — The canonical XML Publisher report triggers. BEFOREREPORT executes prior to report data retrieval, typically used to initialize package globals and to resolve the concurrent request ID. AFTERREPORT executes once data retrieval completes, and is normally used to release resources and perform end-of-report cleanup.
• BEFOREPFORM / AFTERPFORM — Pre- and post-format triggers invoked around the formatting phase of the report. These support logic that must run before or after the XML Publisher layout is applied, such as resetting layout state or finalising formatting attributes.
• BETWEENPAGE — The between-pages trigger, invoked as each page of the report is produced, and typically used for page-level counters, running totals, or repeated page headers and footers.
• M_SET_GRPFRFORMATTRIGGER, M_1FORMATTRIGGER, F_1FORMATTRIGGER, F_2FORMATTRIGGER — Format triggers bound to specific report data groups and fields. The "M_" prefix denotes a group-level (master) format trigger and the "F_" prefix a field-level format trigger; the naming pattern identifies the group and field to which each trigger is attached. These control conditional display, suppress or emphasise data, and can modify the value or visibility of a column at runtime.
• P_CONC_REQUEST_ID_P — Holds or resolves the concurrent request ID parameter used to correlate the report run with the concurrent manager request, a prerequisite for logging and for retrieving any request-specific parameters.
• CP_NLS_NO_DATA_EXISTS_P / CP_NLS_END_OF_REPORT_P — Character-string globals holding NLS-translated messages displayed when a report returns no data and at the end of a report, ensuring the output respects the session language.
• CP_SOB_P, CP_BGP_P, CP_SET_P — Report-level globals carrying the set of books/ledger context (SOB), the budget group parameter (BGP), and associated set/parameter values, populated from the concurrent program parameters and consumed by the report query and format triggers.

Tables Accessed

The package references a single documented base table through an APPS synonym: PSB_BUDGET_GROUPS. This table stores the budget group definitions maintained by Public Sector Budgeting, including the group name, owning set of books or ledger, and related control attributes. The report package reads PSB_BUDGET_GROUPS to populate the budget group parameter list and to derive the budget group context (CP_BGP_P) that drives the report output. The dependency metadata lists SYS and STANDARD as the only external dependencies, confirming that, apart from this table and standard Oracle built-ins, the package is self-contained.

Usage Notes

PSB_PSBRPPRM_XMLP_PKG is not intended for direct invocation by custom code. ETRM records that the package is referenced by zero other packages; its only inbound reference is its own package body. This confirms that the package is a leaf component, invoked exclusively by the Oracle XML Publisher runtime when the associated concurrent program executes.

Users searching for this object are typically diagnosing a report failure, validating that a report was regenerated after a patch, or confirming object status in the APPS schema following an upgrade between EBS 12.1.1 and 12.2.2. Because the package is registered as a concurrent program's report logic, the appropriate troubleshooting sequence is to query the concurrent program definition, review the request log in the concurrent manager, and recompile the package only if it is reported as invalid. Modifications should never be applied directly, as the package body is regenerated whenever the report definition is redeployed from its source.