Search Results pji_job_levels_v

Overview

PJI_JOB_LEVELS_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PJI (Project Intelligence) product family. Within the EBS 12.1.1 and 12.2.2 release streams, Project Intelligence supplies the reporting and analytical layer for Oracle Projects, and views such as this one exist to expose controlled, denormalized value sets to reports, dashboards, and integration points without forcing consumers to navigate the underlying Projects setup schema directly. The ETRM metadata classifies PJI_JOB_LEVELS_V as an "internal summarization view," which indicates it is not intended as a standalone functional entity but as a supporting construct that presents a simplified, presentation-ready projection of job level setup data.

The view carries a status of VALID, confirming that it is a compiled, deployable object in the documented environment. It is relevant to any user searching for "job_level" because it provides a clean list of the job level identifiers and their descriptive values used to classify project assignments, resource roles, and billing or costing categories.

Underlying Base Objects

According to the documented view text, PJI_JOB_LEVELS_V is defined over a single source object: PA_SETUP_JOB_LEVELS_V, itself a view in the Oracle Projects foundation schema. The definition performs no joins, filters, or aggregations of its own:

SELECT JOB_LEVEL ID, JOB_LEVEL VALUE FROM PA_SETUP_JOB_LEVELS_V

The ETRM 12.2.2 metadata lists no additional referenced base objects, meaning the lineage terminates at PA_SETUP_JOB_LEVELS_V for documentation purposes. In practice, the setup view resolves to the Oracle Projects job level setup tables, which store the valid job level codes and their associated descriptions. The PJI view therefore acts as a thin alias layer: it renames the source columns to the generic ID/VALUE convention used elsewhere in Project Intelligence value-list views, providing a consistent interface across multiple setup dimensions.

Key Columns

The view exposes exactly two columns:

• ID — the job level identifier, aliased from JOB_LEVEL in the source view. This is the code value used to store job levels on project assignments, resource definitions, and related transaction records, and is the column to constrain or join on when filtering reports by a specific job level.
• VALUE — the descriptive job level value, aliased from JOB_LEVEL in the source view. This is the human-readable label presented in reports, list-of-values components, and analytical output.

Because both columns derive from the same source column name in PA_SETUP_JOB_LEVELS_V, the source view is expected to project a code and a description under identical column names, and the PJI wrapper maps them consistently to the ID/VALUE pair. There is no primary key enforced by the view itself; uniqueness is inherited from the underlying setup data.

Common Use Cases and Queries

This view is typically used to populate list-of-values queries, report parameters, and lookup joins where a job level code must be rendered with its description. A straightforward listing is:

SELECT ID, VALUE
FROM   APPS.PJI_JOB_LEVELS_V
ORDER BY VALUE;

To resolve a job level code stored on a project assignment or resource record, join the view on the code column:

SELECT t.job_level, v.VALUE
FROM   some_projects_table t,
       APPS.PJI_JOB_LEVELS_V v
WHERE  t.job_level = v.ID;

Because the object is documented as an internal summarization view, direct dependencies in custom code should be avoided where a supported public interface exists; however, for ad hoc reporting and read-only lookup purposes in both 12.1.1 and 12.2.2, it offers a convenient, consistent projection of Oracle Projects job level setup data.