Search Results cp_data_extract_name




Overview
Explore in AI Chat

Overview

The APPS.PSB_PSBRPPOS_XMLP_PKG package body is a report logic package generated for the Oracle E-Business Suite XML Publisher (BI Publisher) report associated with the Public Sector Budgeting (PSB) module. Its name derives from the concurrent program short name PSBRPPOS, which corresponds to the "Account Position Set" reporting function within the PSB application. In Oracle EBS 12.1.1 and 12.2.2, this package serves as the server-side PL/SQL companion to the report's XML data template, supplying the report-level parameters, NLS message constants, and the logic that resolves the display names for optional runtime parameters.

The core business purpose of the package is to prepare descriptive context for the report heading. When the report is submitted, the user may optionally specify an Account Position Set, a Data Extract, both, or neither. The package determines the appropriate display value for each of these parameters, substituting the localized message PSB_ALL (the word "All") when a given parameter is left blank. This ensures the executed report clearly communicates its filtering scope to the reader, regardless of which combination of parameters the requestor supplied.

Notably, the user search term psb_all maps directly to the FND_MESSAGE token retrieved repeatedly in the BEFOREREPORT logic, where FND_MESSAGE.SET_NAME('PSB','PSB_ALL') is used to populate both CP_POSITION_SETS and CP_DATA_EXTRACT_NAME whenever the corresponding identifier is null.

Key Procedures and Functions

The package exposes ten documented program units. Their documented purposes are as follows:

  • BEFOREREPORT — Executes before the report is generated. It captures the concurrent request ID, determines display names for the Data Extract and Account Position Set parameters (using the PSB_ALL message where a parameter is absent), and initializes the NLS constants for "no data exists" and "end of report" messages.
  • AFTERREPORT — Executes after report generation, providing a hook for post-processing such as terminating the report session initiated by the SRW initialization call.
  • BEFOREPFORM — Executes before the report's parameter form is displayed, granting an opportunity to preset or validate parameter values prior to user entry.
  • AFTERPFORM — Executes after the parameter form is submitted, used to validate or transform user-entered parameter values before the main report query runs.
  • BETWEENPAGE — Executes between report pages, typically used for page-level formatting, headers, or control-break processing.
  • P_CONC_REQUEST_ID_P — A getter/setter for the P_CONC_REQUEST_ID package variable that holds the concurrent request identifier.
  • C_NLS_END_OF_REPORT_P — Accessor for the C_NLS_END_OF_REPORT constant containing the localized end-of-report text.
  • C_NLS_NO_DATA_EXISTS_P — Accessor for the C_NLS_NO_DATA_EXISTS constant containing the localized no-data message.
  • CP_DATA_EXTRACT_NAME_P — Accessor for the CP_DATA_EXTRACT_NAME variable holding the resolved Data Extract display name.
  • CP_POSITION_SETS_P — Accessor for the CP_POSITION_SETS variable holding the resolved Account Position Set display name.

Tables Accessed

The package reads from two PSB tables, addressed through APPS synonyms:

Both tables are queried read-only, purely to resolve identifiers into human-readable labels. No inserts, updates, or deletes are performed against them by this package.

Usage Notes

This package is not invoked directly by end users or custom code. It is generated and managed by Oracle's XML Publisher/BI Publisher report definition infrastructure and is called automatically by the report engine during the execution lifecycle of the PSBRPPOS concurrent program. The report engine invokes BEFOREPFORM and AFTERPFORM around the parameter form, BEFOREREPORT before data retrieval, BETWEENPAGE during pagination, and AFTERREPORT upon completion.

Because the ETRM metadata records zero packages referencing this object, it functions as a terminal leaf in the dependency graph — it is consumed only by the report runtime. The P_CONC_REQUEST_ID value it resolves supports concurrent-program diagnostics and is typically written into the report's log or completion record. Administrators troubleshooting PSB report parameter display issues, particularly unexpected "All" values, should inspect the PSB_ALL message definition and the BEFOREREPORT branching logic documented above.