Search Results psp_psprcpgd_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.PSP_PSPRCPGD_XMLP_PKG is a valid PL/SQL package body in the Oracle E-Business Suite Applications schema. It belongs to the Oracle Enterprise Talent/Resource Management (ETRM) product family, specifically the PSA (Professional Services Automation / Grants) module, and serves as the backend program unit that generates the "Pre-Generated Cost Distribution" report output in XML Publisher (BI Publisher) format. The package operates as an XMLP report package: the "XMLP" suffix and the presence of a BEFOREREPORT trigger confirm that it is bound to an XML Publisher data template and executed by the Oracle Reports/XML Publisher concurrent program engine.

Its business purpose is to extract, format, and present pre-generated cost distribution lines from the PSA distribution history tables — principally PSP_PRE_GEN_DIST_LINES_HISTORY and PSP_SUMMARY_LINES — alongside project, task, award, organization, person, and time-period context. It is classified as OTHER in the API classification scheme, meaning it is not a supported public API; it is an internal report implementation object.

Key Procedures and Functions

The package body exposes approximately 36 documented procedures and functions, most of which are the standard "CF_*" group functions that XML Publisher invokes to resolve placeholder columns in the data template. Documented members include:

Each formula component is referenced by the XML Publisher template; the package body also contains the anonymous SQL statements that populate the report's intermediate result sets.

Tables Accessed

The package reads from both ETRM/PSA-specific tables and shared EBS reference tables:

Usage Notes

PSP_PSPRCPGD_XMLP_PKG is executed exclusively by the XML Publisher concurrent program that produces the Pre-Generated Cost Distribution report. It is invoked through the Oracle Reports/XML Publisher runtime rather than by direct API calls. Because the ETRM metadata confirms it is referenced by zero other database objects, it has no inward dependencies — it is a leaf report package. Customizations should not modify the package body directly; instead, the associated data template or a copied custom report should be used. The package runs under the APPS schema with standard EBS profile and currency resolution, so its output respects the user's session profile options (currency format, reporting organization) at run time.