Search Results project_job_level




Overview
Explore in AI Chat

Overview

PA_SETUP_JOB_LEVELS_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. It is a setup-oriented, non-transactional view whose stated purpose is to populate the Job Levels list of values (LOV) on the Project Roles setup page or form UI. Rather than exposing a full denormalized business entity, the view functions as a filtered lookup source: it returns the subset of project job-level lookup values that are currently enabled, that have not expired, and that correspond to the job group associated with project resources.

Because the Project Roles setup flow must present only valid, active job levels to the user, the view encapsulates the joins and filters that would otherwise have to be repeated in every form or page that renders this LOV. Within reporting and integration scenarios, the view can be treated as a ready-made source for the "valid project job level" domain, though its primary design intent remains UI lookup support rather than analytical reporting.

Underlying Base Objects

The documented view text draws from four referenced objects:

The joins connect jobs to their extra information, then to the project job-level lookup via JEI_INFORMATION4 = LOOKUP_CODE. The job group filter uses NVL(PA_JOB_UTILS.GET_PROJ_RES_JOB_GROUP(NULL), PJ.JOB_GROUP_ID), so that when the function returns a value, only jobs in that group are retained; otherwise all job groups pass through. Only enabled lookup values are included, and expired rows are excluded via the condition (PL.END_DATE_ACTIVE >= SYSDATE OR PL.END_DATE_ACTIVE IS NULL).

Key Columns

The view exposes the following columns, several of which are deliberately nulled because the source is a lookup rather than an HR grade entity:

  • GRADE_ID — Exposed as NULL; retained for interface compatibility with grade-based LOV structures.
  • BUSINESS_GROUP_ID — Exposed as NULL.
  • GRADE_DEFINITION_ID — Exposed as NULL.
  • DATE_FROM — Populated from PL.START_DATE_ACTIVE, the lookup value's effective start date.
  • JOB_LEVEL — Populated as TO_NUMBER(PJEI.JEI_INFORMATION4), the numeric job-level code derived from job extra information.
  • DATE_TO — Populated from PL.END_DATE_ACTIVE, the lookup value's expiration date.
  • NAME — Exposed as NULL.
  • DESCRIPTION — Populated from PL.MEANING, the descriptive text of the job-level lookup value.

Common Use Cases and Queries

The principal use case is LOV population on the Project Roles setup UI, where the view supplies both the code and description of selectable job levels. Technically, it is also useful for validation, data migration, and integration extracts that must reference only active project job levels.

A typical query retrieving the current job-level LOV values is:

  • SELECT job_level, description, date_from, date_to FROM apps.pa_setup_job_levels_v ORDER BY job_level;

To validate whether a specific level is enabled and unexpired:

  • SELECT job_level, description FROM apps.pa_setup_job_levels_v WHERE job_level = :p_level;

Because the view is DISTINCT and driven by PA_JOB_UTILS, its results can vary with session context and the effective project resource job group, so it should be queried in the appropriate application context. For historical or expired levels, querying PA_LOOKUPS directly is preferred, since this view intentionally excludes disabled and expired lookup values.