Search Results p_prj_template_id




Overview

APPS.PSP_PSPLDPRJ_XMLP_PKG is a report logic package (XML Publisher / Oracle Reports PL/SQL library) associated with the Oracle E-Business Suite project and grants reporting modules. It is regenerated automatically by the Oracle Reports-to-XML Publisher conversion utilities that Oracle seeds for concurrent programs, and as a result it is classified as an OTHER API rather than a supported public API. The package encapsulates the PL/SQL logic behind the "Project Status/Labor Distribution by Project" style report: it holds the concurrent program's runtime parameters, resolves descriptive identifiers, applies currency and date formatting, and prepares rows for the report layout. The package owner is APPS, and the header reference reflects a 2007 revision line, indicating the code has remained stable across the 12.1.1 and 12.2.2 releases.

The user search term, cf_project_nameformula, corresponds directly to the function CF_PROJECT_NAMEFORMULA declared in this package. In Oracle Reports terminology, "CF" denotes a formula column, so this function is the server-side implementation of the Project Name formula column in the report data model.

Key Procedures and Functions

The package declaration exposes the report's single-row parameter variables (P_PROJECT_ID, P_CONC_REQUEST_ID, P_BUSINESS_GROUP_ID, P_SET_OF_BOOKS_ID, P_START_DATE, P_END_DATE, P_PRJ_TEMPLATE_ID) and 29 documented program units.

Tables Accessed

The package reads through APPS synonyms to a defined set of base and interface tables, all consistent with project labor cost distribution reporting:

Usage Notes

This package is not intended to be called directly by customer code; it is invoked by the Oracle Reports/XML Publisher runtime when the associated concurrent program is executed. Because it is a generated package, any direct modification is overwritten during patching or upgrade, and it is not referenced by any other documented package (referenced-by count of zero). Developers who need the project name in custom code should rely on the supported public APIs rather than on CF_PROJECT_NAMEFORMULA. The behavior is consistent between Oracle EBS 12.1.1 and 12.2.2, although installations upgraded through the 12.2 online patching cycle may see the package recompiled with a new header revision.