Search Results pji_lookups




Overview
Explore in AI Chat

Overview

PJI_LOOKUPS is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PJI – Project Intelligence product family, which Oracle classifies as obsolete in the current ETRM documentation. The view exposes translatable constant values (lookups) that are presented to users in the Project Intelligence application and in any downstream component that consumes its reference data.

Functionally, PJI_LOOKUPS is a filtered, language-aware projection of the Oracle Applications lookup repository. Rather than querying the shared FND_LOOKUP_VALUES table directly, consumers of Project Intelligence reference data query this view, which restricts the result set to lookup types owned by the PJI application and applies language and security-group filtering automatically. This makes the view suitable for reporting, concurrent programs, and integration extracts where only Project Intelligence lookup values are relevant.

The view is documented as VALID in the APPS schema. Its metadata is recorded in ETRM 12.2.2, and the definition is consistent with the 12.1.1 Applications technology stack, since the underlying lookup infrastructure (FND_LOOKUP_VALUES, FND_GLOBAL) is common to both releases.

Underlying Base Objects

The ETRM metadata documents two referenced base objects:

  • FND_LOOKUP_VALUES (SYNONYM) – The core Applications lookup values table, exposed through the APPS synonym. It stores each lookup code, its meaning and description, effective dates, enabled flag, tag, audit columns, and the fifteen descriptive flexfield attribute columns.
  • FND_GLOBAL (PACKAGE) – The Applications global context package, invoked in the view predicate through FND_GLOBAL.LOOKUP_SECURITY_GROUP to resolve the caller's lookup security group at runtime.

The view text selects the standard lookup columns from FND_LOOKUP_VALUES LV with three predicates: LANGUAGE = USERENV('LANG'), VIEW_APPLICATION_ID = 1292 (the application identifier for Project Intelligence), and SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID). The result is that only rows belonging to application 1292 and visible to the session's language and security group are returned. Because the view is defined over a synonym rather than a fully qualified table name, it resolves against the APPS-owned FND_LOOKUP_VALUES object in the standard EBS configuration.

Key Columns

The view exposes the complete set of FND_LOOKUP_VALUES columns, without renaming or derivation:

Common Use Cases and Queries

Typical uses include validating lookup codes in extracts, generating translated reference lists for reports, and driving list-of-values logic in custom Project Intelligence interfaces. A representative query listing all enabled Project Intelligence lookups for a given type is:

SELECT lookup_type, lookup_code, meaning, description FROM apps.pji_lookups WHERE lookup_type = :p_lookup_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY lookup_code;

Because the view is pre-filtered by language and security group, no additional language predicate is required; the session's NLS settings determine which translated MEANING values are returned. Note that the PJI product is marked obsolete, so new development should verify whether the view remains the supported access path in the target release. Reusable code should be capitalized to match the APPS-standard naming convention.