Search Results pa_job_assignment_overrides_u4

Overview

PA.PA_JOB_ASSIGNMENT_OVERRIDES is a transactional table in the Oracle E-Business Suite Projects (PA) schema that stores special employee job assignments and billing titles negotiated for specific projects or tasks. These overrides take precedence over an employee's primary job assignment. When job bill rates are used on a project, the Generate Draft Revenue process references the override rather than the employee's default job assignment to calculate revenue, and the Generate Draft Invoice process displays the override billing title and job title on invoice lines where the project's invoice format supports job and billing title display.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. From a Data Vault modeling perspective, the mined foreign key structure suggests classifying this object as a link, since it resolves relationships among persons, projects, tasks, and jobs. Practitioners may alternatively treat it as a satellite if modeling the override attributes (billing title, effective dates) against a person/project core hub.

Key Information Stored

• JOB_ASSIGNMENT_OVERRIDE_ID — System-generated surrogate primary key. It is enforced by unique index PA_JOB_ASSIGNMENT_OVERRIDES_U4, making it the documented unique business-key candidate.
• PERSON_ID — Identifier of the employee billed under the job assignment override; part of the composite primary key.
• PROJECT_ID — Identifier of the project for which the override is entered; part of the composite primary key.
• TASK_ID — Identifier of the task for which the override applies; part of the composite primary key.
• START_DATE_ACTIVE — First effective date of the override; part of the composite primary key.
• END_DATE_ACTIVE — Last effective date of the override, bounding the override's validity window.
• JOB_ID — Identifier of the job that overrides the employee's primary job assignment.
• BILLING_TITLE — Negotiated billing title displayed on invoices where the format supports it.
• RECORD_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — audit tracking for inserts and updates.

Note that the physical primary key PA_JOB_ASSIGNMENT_OVERRIDES_PK is composite (PERSON_ID, PROJECT_ID, TASK_ID, START_DATE_ACTIVE), while the documented unique index U4 keys on JOB_ASSIGNMENT_OVERRIDE_ID.

Common Use Cases and Queries

Typical scenarios include retrieving all active overrides for a project, verifying which job or billing title applies to a specific employee on a task as of a given date, and driving revenue and invoice generation. A representative query joining to PA_PROJECTS_ALL and PA_TASKS follows:

• SELECT p.project_number, t.task_number, o.person_id, o.job_id, o.billing_title FROM pa.pa_job_assignment_overrides o, pa.pa_projects_all p, pa.pa_tasks t WHERE o.project_id = p.project_id AND o.task_id = t.task_id AND o.project_id = :project_id AND TRUNC(SYSDATE) BETWEEN o.start_date_active AND NVL(o.end_date_active, TRUNC(SYSDATE));
• Join to PER_JOBS on JOB_ID to resolve the overriding job name for reporting.
• Filter by PERSON_ID to audit an individual's negotiated assignment history across projects.

Nonunique index N1 (PROJECT_ID, PERSON_ID) supports project-scoped lookups, while N2 (TASK_ID, PERSON_ID) supports task-scoped retrieval.

Related Objects

• PA.PA_PROJECTS_ALL — referenced via PROJECT_ID.
• PA.PA_TASKS — referenced via TASK_ID.
• PER.PER_JOBS — referenced via JOB_ID, supplying the overriding job definition.
• PER.PER_ALL_PEOPLE_F — supplies employee details for PERSON_ID joins.
• PA.PA_JOB_ASSIGNMENTS — the primary job assignment that this override supersedes.
• PA.PA_DRAFT_REVENUE_ITEMS / draft invoice tables — consume override data during Generate Draft Revenue and Generate Draft Invoice processing.