Search Results address_date_to




Overview

APPS.PA_C_JOBLEVEL_RES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle Projects (PA) product family and consolidates resource, job, grade, organization, and address information for project resources into a single denormalized projection. The "C" prefix and design data reference PA.PA_C_JOBLEVEL_RES_V indicate that the object is an internal, cursor-based view used by Oracle Projects forms and concurrent programs rather than a supported public interface. Oracle documents it with the standard warning that it is for Oracle Internal Use Only and that it must not be accessed directly except from standard Oracle Applications programs.

In practice, the view presents a snapshot of resources with their associated job levels, effective-dated assignment details, and effective-dated address ranges. It is most relevant to developers and analysts investigating how Oracle Projects resolves resource job level, grade, and address-date attributes for a given resource, and it is frequently examined when troubleshooting date-effective logic in Oracle Projects.

Underlying Base Objects

The view draws on Oracle Projects, Oracle Human Resources, and Oracle Application Object Library objects. The documented dependencies are:

Because PER_ASSIGNMENTS_F, PER_ADDRESSES, PER_PEOPLE_F, and PER_JOBS are date-effective (datetracked) entities, the view returns effective-dated rows, which is why the ADDRESS_DATE_FROM, ADDRESS_DATE_TO, GRADE_DATE_FROM, and GRADE_DATE_TO columns appear. Note that GRADE_DATE_FROM and GRADE_DATE_TO are defined as VARCHAR2 rather than DATE, and this is the column family most closely associated with the user's search term "address_date_to".

Key Columns

Common Use Cases and Queries

The view is typically queried to resolve a resource's job level together with its effective-dated address interval, for example when reconciling the range an address was active against the assignment period. A representative query follows:

SELECT RESOURCE_ID,
       RESOURCE_NAME,
       RESOURCE_JOB_NAME,
       RESOURCE_JOB_LEVEL,
       ASSIGNMENT_START_DATE,
       ASSIGNMENT_END_DATE,
       ADDRESS_DATE_FROM,
       ADDRESS_DATE_TO
FROM   APPS.PA_C_JOBLEVEL_RES_V
WHERE  RESOURCE_ID = :resource_id
ORDER  BY ADDRESS_DATE_FROM DESC;

A second common pattern filters resources active on a given date, using ADDRESS_DATE_FROM and ADDRESS_DATE_TO to bound the address interval and ASSIGNMENT_START_DATE/ASSIGNMENT_END_DATE for the assignment:

SELECT RESOURCE_NAME,
       RESOURCE_JOB_LEVEL,
       RESOURCE_ORGANIZATION_NAME
FROM   APPS.PA_C_JOBLEVEL_RES_V
WHERE  :effective_date BETWEEN ADDRESS_DATE_FROM AND ADDRESS_DATE_TO;

Because the object is unsupported and its logic depends on datetracked HR tables and internal PL/SQL, direct queries should be restricted to diagnostic and reporting purposes; production integrations should use supported Oracle Projects APIs such as PA_HR_UPDATE_API and PA_RESOURCE_UTILS.