Search Results project_job_level




Overview
Explore in AI Chat

Overview

APPS.PA_SETUP_JOB_LEVELS_V is a Projects (PA) module setup view that exposes the valid project job levels available for assignment to project resources. It is a reporting and integration-oriented object rather than a transactional table. In Oracle EBS 12.1.1 and 12.2.2, it forms part of the Project Resource Management configuration layer, where job levels are used to grade resources, drive billing rate derivation, control cost and revenue generation, and determine rate schedules in project costing.

The view harmonizes data from Human Resources (PER) job definitions with Projects lookup values stored under the PROJECT_JOB_LEVEL lookup type. Because job levels are maintained as lookup codes and attached to jobs through descriptive flexfield segments, this view provides a denormalized, query-ready projection that exposes only active and currently effective setup records. It is typically consumed by project setup validation reports, resource configuration extracts, and downstream rate and billing integrations.

Underlying Base Objects

The view is constructed from the following documented base objects:

  • PER_JOBS (SYNONYM) — the HR jobs definition. The view selects pj.job_id and pj.job_group_id, restricting results to the project resource job group by comparing the job group against PA_JOB_UTILS.GET_PROJ_RES_JOB_GROUP(NULL).
  • PER_JOB_EXTRA_INFO (SYNONYM) — the job extra information (descriptive flexfield) table. Only rows with information_type = 'Job Category' participate, and the flexfield segment jei_information4 supplies the job level value.
  • PA_LOOKUPS (VIEW) — the Projects lookup values. The view joins pjei.jei_information4 to pl.lookup_code where lookup_type = 'PROJECT_JOB_LEVEL' and enabled_flag = 'Y'.
  • PA_JOB_UTILS (PACKAGE) — supplies the project resource job group identifier through GET_PROJ_RES_JOB_GROUP, used to scope the job population.

The joins follow the path: PER_JOBS → PER_JOB_EXTRA_INFO → PA_LOOKUPS, with the lookup acting as the authoritative source of job level meaning, start and end dates.

Key Columns

  • grade_id / business_group_id / grade_definition_id / name — returned as NULL literals, present for structural compatibility with grade-based views.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range of the job level lookup, sourced from pl.start_date_active and pl.end_date_active.
  • JEI_INFORMATION4 (exposed as a numeric value) — the job level code attached to the job, converted with TO_NUMBER.
  • MEANING — the descriptive name of the job level, sourced from pa_lookups.meaning.

Common Use Cases and Queries

This view is commonly used to validate that project resources carry a recognized job level, to build resource rate configuration extracts, and to populate interfaces where a job level identifier or meaning is required.

A typical query returning all active, effective job levels is:

  • SELECT jei_information4, meaning, start_date_active, end_date_active FROM apps.pa_setup_job_levels_v ORDER BY meaning;

To list job levels that expire within a given period:

  • SELECT meaning, end_date_active FROM apps.pa_setup_job_levels_v WHERE end_date_active BETWEEN SYSDATE AND SYSDATE + 90;

Because the view already filters on enabled_flag = 'Y' and excludes expired lookups, consumers need not reapply those predicates; it is best treated as a read-only setup source for reporting and integration rather than a maintenance surface.