Search Results pji_rep_prf_dflt_params




Overview
Explore in AI Chat

Overview

APPS.PJI_REP_PRF_DFLT_PARAMS is a PL/SQL package body deployed in the APPS schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its name indicates a role in deriving the default parameter values used by Project Intelligence (PJI) reporting and performance-related data extraction. In the EBS architecture, Project Intelligence reporting relies on parameters supplied at runtime to scope project performance data; the PJI_REP_PRF_DFLT_PARAMS package centralizes the logic that determines which default values should be applied when the user or calling program does not supply explicit selections. This supports consistent, repeatable reporting behavior across concurrent programs, Oracle Forms, and any custom callers that require baseline parameter derivation. The package is registered as VALID in the ETRM metadata and is classified under the generic API classification OTHER, indicating it is an internal utility rather than a published, customer-facing API. It has no documentation of being referenced by any other database object, which confirms its role as a leaf-level dependency invoked directly rather than an inter-package integration point. Its dependencies on FND_PROFILE, PA_PROJECT_STRUCTURE_UTILS, PA_PROJ_ELEMENT_VERSIONS, PJI_REP_UTIL, and the SYSTEM-defined collection type PA_NUM_TBL_TYPE are consistent with a helper that reads user profile options, resolves project structure and element version information, and reuses shared PJI reporting utilities while manipulating numeric collections.

Key Procedures and Functions

The ETRM metadata documents exactly one program unit within this package body: DERIVE_DFLT_PARAMS. As the sole entry point, this procedure encapsulates the package's entire purpose. It is responsible for computing and returning the default parameter values required by the Project Intelligence reporting process. The procedure is expected to consult the current FND_PROFILE settings (including the responsible application and responsibility) to determine the default operating context, and to consult project structure and element version data so that the derived defaults align with the applicable project hierarchy and the correct version of each project element. No parameter list is documented in the available metadata, so the exact signature is not reproduced here; consumers should inspect the package specification in APPS to confirm the precise arguments before invoking it from custom code. Organizationally, DERIVE_DFLT_PARAMS belongs to the "defaulting" tier of the PJI reporting stack: it supplies parameter values but does not itself execute the report or extract the fact data. This separation means the procedure is idempotent with respect to database state under normal conditions—it derives values rather than persisting report output.

Tables Accessed

Two tables are documented as accessed through APPS synonyms:

  • PA_PROJ_ELEMENT_VERSIONS — the project element version table. DERIVE_DFLT_PARAMS reads this table to determine the effective version of project structure elements, which is necessary because Project Intelligence reporting must resolve the project hierarchy as of the correct version. Default parameters derived against an incorrect element version would cause reports to use stale or mismatched project structures.
  • PLITBLM — the PL/SQL table (associative array) type used for collections. It is listed here in the table dependency list because PL/SQL collection types appear as dependencies of compiled package bodies; it is not a data table in the conventional sense. Its presence confirms that the package manipulates in-memory numeric collections, consistent with the PA_NUM_TBL_TYPE dependency originating from the SYSTEM schema.

No DML against persisted report tables is documented, reinforcing that the package is read-only with respect to business data.

Usage Notes

PJI_REP_PRF_DFLT_PARAMS is an internal support package and is not referenced by any other database object per the ETRM metadata. It is therefore invoked either directly by Project Intelligence reporting code paths—such as concurrent programs and OA Framework or Forms-based report submission pages—or explicitly by custom extensions that need to reproduce the standard defaulting behavior. Typical invocation occurs before report execution, when the calling program needs to fill in defaults for reporting parameters such as operating unit, project range, and element version. Because the package depends on FND_PROFILE, correct behavior requires a properly initialized EBS session context (application, responsibility, user, and org); calls made outside an authenticated session may return unexpected defaults. Customers extending Project Intelligence reporting should call DERIVE_DFLT_PARAMS rather than reimplementing profile and element-version logic, ensuring alignment with Oracle's standard defaulting rules. As with all APPS-schema objects, the package body should be treated as Oracle-owned and customized only through supported extension mechanisms.