Search Results pji_pmv_util




Overview
Explore in AI Chat

Overview

APPS.PJI_PMV_UTIL is a utility package body within the Oracle EBS Projects (PJI) application module, delivered in the APPS schema and reported as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its classification as a UTIL object indicates that it exists to support other components of the Projects intelligence and performance management infrastructure rather than to expose a standalone business transaction. The package concentrates on resolving top-level organization context and validating organization membership, using the Oracle HR organization hierarchy and the security model that governs which organizations a user may access.

The package depends on FND_GLOBAL, FND_PROFILE, and FND_USER to establish the current application user and session context, on PER_ORGANIZATION_LIST and PER_SECURITY_PROFILES to respect HR security profile restrictions, and on PJI_SYSTEM_SETTINGS to honor Projects-specific configuration. This combination confirms that the package serves as a controlled access layer for organization data consumed by downstream Projects reporting and intelligence logic.

Key Procedures and Functions

  • GET_TOP_ORG_DETAILS — Returns the top-level organization details for the current reporting or security context. The routine walks the organization hierarchy defined by PER_ORG_STRUCTURE_ELEMENTS and HR_ALL_ORGANIZATION_UNITS to identify the highest applicable organization, applying the user's security profile so that only permitted organizations are returned. Callers use the output to scope subsequent queries and reporting to the correct business unit or top organization.
  • PJI_ORGANIZATION_EXISTS — Validates whether a given organization exists and is visible within the caller's security context. This function supports defensive coding in dependent packages and reports, allowing them to confirm organization validity before executing potentially expensive or user-visible processing. It relies on the same HR organization and security profile tables as GET_TOP_ORG_DETAILS.

Both routines are documented as package-level procedures or functions; their exact parameter lists are not enumerated in the ETRM metadata and should be confirmed against the deployed package specification in the target instance.

Tables Accessed

The package reads organization definitions and translations through HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL, the secure organization listing through PER_ORGANIZATION_LIST, and the hierarchy structure through PER_ORG_STRUCTURE_ELEMENTS. Security context is derived from PER_SECURITY_PROFILES together with PER_ALL_ASSIGNMENTS_F, which ties the current user to an assignment and therefore to an organization. FND_USER and the FND_GLOBAL and FND_PROFILE APIs supply the session user and profile option values. PJI_SYSTEM_SETTINGS provides Projects-specific control parameters, and DUAL is used for scalar evaluation. No writes to these tables are documented; the package operates in a read-only capacity.

Usage Notes

PJI_PMV_UTIL is an internal helper. ETRM records that it is referenced by zero other database objects, meaning no shipped package, view, or trigger declares a hard dependency on it — a pattern typical of utility code invoked dynamically or through the package specification at runtime. It is most likely called from Projects intelligence forms, concurrent programs, and custom extensions that need to determine the correct top organization for a user or to verify organization access before proceeding. Because the package enforces HR security profiles, behavior varies with the signed-in user's security configuration, and results should be interpreted per user session. Custom code should call the documented routines rather than replicating organization hierarchy logic, ensuring consistent respect for security profiles and PJI system settings. As with all APPS schema utilities, it should not be modified in place; extensions should wrap the delivered API.