Search Results pa_pjp_pvt




Overview
Explore in AI Chat

Overview

PA_PJP_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema, owned by the Projects (PA) module and classified under the ETRM registry as a Private (PVT) API. The package name references the Project PJP schema, associating it with the Oracle Projects Scorecard and Project Performance reporting infrastructure. In Oracle EBS 12.1.1 and 12.2.2, private packages such as this one are not intended for direct customer invocation; they are consumed internally by other Oracle Projects components and deliver behavior through a small, tightly scoped set of entry points. The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema, and its header bears a 2005 source revision consistent with the family of Project Scorecard APIs carried forward from 11i into Release 12.

Key Procedures and Functions

  • Submit_Project_Aw — A procedure that submits a project for the Award (AW) workflow or scorecard processing path, keyed by the supplied project identifier. It follows the standard Oracle API contract, accepting API version, message list initialization, and commit control flags on input, and returning the conventional x_return_status, x_msg_count, and x_msg_data output parameters for error handling. This mirrors the canonical PL/SQL API pattern used across Oracle Projects so that callers can standardize exception and message retrieval.
  • proj_scorecard_link_enabled — A function that accepts a function name and project identifier and returns a VARCHAR2 value indicating whether the Project Scorecard link is enabled for that context. This is a configuration/eligibility check typically used to control navigation or rendering of scorecard-related UI elements, allowing the caller to conditionally expose scorecard functionality based on project-specific setup.

Tables Accessed

The ETRM metadata for this package does not enumerate any directly referenced tables through APPS synonyms. This is characteristic of a private package that delegates data access to underlying base packages, views, or helper routines rather than issuing DML itself. Access to project setup, scorecard configuration, and award-processing data is therefore expected to occur indirectly through the packages and views owned by the Oracle Projects Scorecard components. Where tables are touched, they would relate to project definitions and scorecard enablement settings, but no specific base table is documented.

Usage Notes

Because PA_PJP_PVT carries the PVT classification, it should not be called directly from customer extensions; Oracle does not guarantee backward compatibility for private APIs across patches or releases. The package is referenced by two other packages within the Oracle Projects codebase, confirming that its primary callers are sibling Oracle modules rather than external code. Typical invocation occurs from the Project Scorecard and Award processing flows, where the calling layer resolves eligibility via proj_scorecard_link_enabled and then triggers submission through Submit_Project_Aw. Deployment context spans both 12.1.1 and 12.2.2, with the same header lineage, and any supported customization should instead target the corresponding public (PUB) APIs exposed by Oracle Projects.