Search Results pji_pmv_engine




Overview
Explore in AI Chat

Overview

PJI_PMV_ENGINE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name derives from the Project Manufacturing (PJI) product family combined with the PMV (Project Manufacturing Value or Project Manufacturing Variance) engine designation, and it is classified under the ETRM API classification of OTHER. This classification indicates that the package is neither a fully published open interface nor a standard public API, but rather an internal engine component invoked by other project manufacturing processes.

The package is declared with AUTHID CURRENT_USER, which means that all unqualified object references inside the package body are resolved against the privileges of the calling user rather than the package owner. This design choice is consistent with an internal engine that is expected to execute in the context of the invoking application, form, or concurrent program, typically the APPS schema itself. The header comment included in the source identifies the file as PJIRX01S.pls, with a revision level of 120.7 dated 2011/09/22, reflecting maintenance activity in the 12.1.x and early 12.2.x release cycle.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents zero procedures or functions for PJI_PMV_ENGINE. The visible source excerpt consists solely of the package specification header, the revision control comment, and the terminating END statement, with no declarations exposed between them. This indicates that the package specification is intentionally empty from an external calling perspective.

Because no public procedures or functions are documented, no parameter lists can be stated. The engine logic associated with this package is therefore presumed to reside either in private declarations within a package body that accompanies the specification, or to be invoked indirectly through other project manufacturing components that reference the PMV engine internally. Consumers should not assume any callable entry points exist based on the specification alone.

Tables Accessed

The documented metadata lists no tables referenced via APPS synonyms. This means the package specification exposes no direct dependency on project manufacturing tables such as PJI_ or PJM_ base objects at the specification level. Any table access performed by the PMV engine would occur within the package body or through private cursors and dynamic SQL, which are not surfaced in the specification metadata. No reads, writes, or DML operations can be attributed to this package from the documented facts.

Usage Notes

The metadata records that PJI_PMV_ENGINE is referenced by zero other packages. Combined with the empty specification and the absence of documented procedures, this suggests the package is either a stub retained for upgrade compatibility or an engine whose public surface has been deliberately minimized. It is not intended for direct invocation from custom code, Oracle Forms, or concurrent programs using standard PL/SQL call syntax.

In practice, customizations should avoid calling PJI_PMV_ENGINE directly. Any requirement to extend project manufacturing variance or valuation logic should be pursued through the supported project manufacturing APIs and concurrent programs that internally reference the engine, rather than through this package. Because the specification is empty and the AUTHID is CURRENT_USER, any attempted direct call would fail to resolve a procedure, and code depending on internal behavior would be unsupported across patch levels. Developers reviewing this object during an upgrade from 12.1.1 to 12.2.2 should treat it as a non-public internal component and verify dependencies through the project manufacturing application modules rather than through this package.