Results for “pji_pmv_profitability_trend”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PJI_PMV_PROFITABILITY_TREND is a PL/SQL package that belongs to the Oracle Projects (PJI) application family within Oracle E-Business Suite. Its name associates it with the Profitability Management and Project Management Views reporting layer, specifically the revenue forecasting (RF) subcomponent, as indicated by the source file header PJIRF05S.pls. The package is defined with the AUTHID CURRENT_USER clause, meaning it executes with the privileges of the invoking database user rather than the package owner, a common convention for shared reporting utilities in the APPS schema. In ETRM 12.2.2 the object is classified under the API classification OTHER, indicating that Oracle does not publish it as a supported public API and does not expose a formal interface contract for external callers. The package body as documented is effectively a stub declaration in the visible excerpt, and the vendor metadata records no documented procedures or functions, no referenced tables via APPS synonyms, and no internal dependents. Consequently the business function is best understood as an internal helper for aggregating and presenting project profitability trend data rather than as a transactional interface.

Key Procedures and Functions

The documented metadata lists zero procedures and functions for APPS.PJI_PMV_PROFITABILITY_TREND. No callable entry points are published, and no parameter lists are recorded. Any public routines that may exist inside the deployed package body are not part of the documented interface and must not be assumed. The visible source excerpt shows the package specification opening with the AUTHID CURRENT_USER declaration and then terminating with an END statement, which is consistent with an interface whose implementation is either minimal or deliberately withheld from documentation. Consumers should treat the package as non-public and avoid direct invocation, since the absence of documented signatures means there is no stability guarantee across patches, including the 12.1.1 to 12.2.2 upgrade path.

Tables Accessed

The ETRM documentation records no tables referenced through APPS synonyms for this package. Because the body is not exposed and the dependency listing is empty, the underlying physical tables cannot be confirmed from metadata alone. Functionally, a profitability trend package in the Projects suite would ordinarily read project funding, revenue, cost, and budget baseline data to compute period-over-period margin and revenue trends for Profitability Management dashboards. That expected data footprint is inferred from the package name and the PJIRF05S source identifier; it is not documented and should be verified against the deployed object in a given environment before any analysis that depends on specific tables.

Usage Notes

Given the classification and the lack of documented entry points, APPS.PJI_PMV_PROFITABILITY_TREND is normally invoked indirectly, through Oracle Projects Profitability Management reporting or Project Management Views components, rather than being called from custom code. It is not referenced by any other documented package in the APPS schema per the metadata, which further supports its role as a leaf-level reporting utility. When investigating behavior in a 12.1.1 or 12.2.2 instance, the reliable approach is to inspect the deployed package body and its USER_DEPENDENCIES entries directly, since the public ETRM record provides no parameter, return value, or table access detail. The presence of the “thepsi.com turnover” search term suggests interest in metrics derived from such trend utilities, but no turnover calculation is documented for this object; any such figure should be traced to the specific reporting layer or query that produces it.