Search Results pji_organization_exists




Overview

PJI_PMV_UTIL is a utility package in the Oracle EBS Projects (PJI/PMV) module, owned by the APPS schema and classified by ETRM as a Utility (UTIL) API. Its role is to provide reusable helper logic that supports Project Management and Project Portfolio Management views — specifically the determination of a user's top organization context and the validation of organization identifiers against the security model configured for Projects. The package declares AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the definer. This design makes it suitable for runtime validation where the caller's Oracle session and applied security profiles determine the accessible data set. The package header carries a version marker dated 2011, consistent with the 12.1.1 and 12.2.2 code lines, and the presence of a bug-fix comment on the get_top_org_details signature indicates it has been maintained across patch levels.

Key Procedures and Functions

  • GET_TOP_ORG_DETAILS — Returns the top-level organization context for the current user. Its output parameters communicate the organization ID and organization name, an assessment flag indicating whether a user-level assignment exists, and a flag added under bug#6623113 that signals whether a top organization record should be inserted. Because it is a procedure, all values are returned through OUT parameters rather than a return value.
  • PJI_ORGANIZATION_EXISTS — A function accepting an organization ID (p_org_id IN NUMBER) and returning a NUMBER. It serves as a boolean-style predicate to determine whether the supplied organization is valid and visible within the user's security context. This is the object referenced by the search term "pji_organization_exists," and it is the most directly reusable element of the package for validation logic.

Tables Accessed

Usage Notes

PJI_PMV_UTIL is typically invoked from Projects-related forms and concurrent programs that need to establish the invoking user's top organization before rendering project or portfolio data, and from custom code that must validate an organization ID before processing. Callers should invoke PJI_ORGANIZATION_EXISTS as a predicate within conditional logic rather than assuming an exception on failure, since it returns a numeric result. Because the package is AUTHID CURRENT_USER, results depend on the security profiles and organization access granted to the session user, and behavior may differ between a direct database session and one established through an EBS responsibility. The package is documented as referenced by zero other packages, suggesting it is called directly by forms or external code rather than being a dependency of other shipped PL/SQL units.