Search Results cp_data_extract_name_p




Overview
Explore in AI Chat

Overview

PSB_PSBRPPOS_XMLP_PKG is an Oracle Application Object Library (AOL) generated PL/SQL package that resides in the APPS schema and carries a VALID status in Oracle EBS 12.1.1 and 12.2.2. It is the technical backbone of the Oracle Grants / Public Sector Budgeting (PSB) report commonly known as the Position Sets report, delivered through the Oracle Reports XML Publisher (XMLP) concurrent program architecture. In the EBS XML Publisher pattern, a report definition named PSBRPPOS is registered as a concurrent program; Oracle Reports runs the report's data model and invokes this package so that the report's formula columns, user exits, and parameter validations are executed as named PL/SQL program units. The package therefore does not implement business logic in the transactional sense — its role is to orchestrate report runtime behavior, evaluate the concurrent request context, and surface the extract and position-set data required by the printed or PDF output. Its API classification is OTHER, indicating a support/reporting component rather than a public integration API, and the ETRM record documents exactly ten packaged program units.

Key Procedures and Functions

  • BEFOREREPORT — report-level initialization exit, executed once before the report body is processed to establish setup data the report requires.
  • AFTERREPORT — report-level finalization exit, run after the main body to release or finalize report state.
  • BEFOREPFORM — before-parameter-form exit, invoked prior to the report's parameter form so defaults and validations can be established.
  • AFTERPFORM — after-parameter-form exit, invoked once the user has supplied report parameters, typically used to derive dependent parameter values.
  • BETWEENPAGE — between-page exit, executed as the report paginates to maintain running values or page-level context.
  • P_CONC_REQUEST_ID_P — supplies/returns the concurrent request identifier, the standard mechanism by which an XML Publisher report links back to its concurrent request record.
  • C_NLS_END_OF_REPORT_P — returns the NLS-translated label used at the end of the report output.
  • C_NLS_NO_DATA_EXISTS_P — returns the NLS-translated message displayed when the report query returns no rows.
  • CP_DATA_EXTRACT_NAME_P — returns or holds the name of the data extract used to source report content.
  • CP_POSITION_SETS_P — returns or holds the position set identifier(s) that scope the report's results.

No parameter signatures are documented in the ETRM record; consumers should treat these as internal report callbacks rather than callable APIs.

Tables Accessed

Two base tables are documented, both reached through APPS synonyms and both central to Public Sector Budgeting position control:

  • PSB_ACCOUNT_POSITION_SETS — defines the position sets associated with accounts; the package reads this table to resolve the position-set criteria that drive the report, supporting CP_POSITION_SETS_P.
  • PSB_DATA_EXTRACTS — stores the configured data extract definitions used by PSB reporting; the package reads it to identify the extract whose name is surfaced by CP_DATA_EXTRACT_NAME_P and whose contents populate the report.

The dependency listing shows only SYS.STANDARD in addition to these objects, confirming that the package relies on minimal infrastructure and that its functional footprint is limited to PSB position-set and extract data.

Usage Notes

PSB_PSBRPPOS_XMLP_PKG is not intended for direct invocation. It is called by the Oracle Reports runtime when the PSBRPPOS XML Publisher concurrent program executes, and by the report's parameter form during submission. The ETRM metadata records zero packages referencing it, so no other PL/SQL component depends on it — a strong indicator that it is a leaf-level, report-dedicated unit safe to leave untouched during upgrades and patches. Custom code should never call its procedures directly; where extension is required, the supported approach is to modify or clone the underlying report definition and its concurrent program registration. Administrators troubleshooting missing output should focus on the associated concurrent request, the two PSB tables above, and the request ID returned by P_CONC_REQUEST_ID_P, since those are the only external touchpoints the package exposes.