Results for “pqp_gap_absence_plans”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQP_GAP_ABSENCE_PLANS is a Public Sector Payroll (PQP) table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the generic absence plans that underpin the Global Absence Processing (GAP) functionality used to evaluate and administer employee absences — particularly for public sector and public sector-style payroll deployments. Each row represents an absence plan header record associated with a specific assignment and absence attendance event, and it acts as the parent for the more granular daily and duration-level calculations performed against that plan.

From a modeling perspective, the Data Vault classification heuristic indicates a hub-leaning object. That is, PQP_GAP_ABSENCE_PLANS behaves primarily as a hub-like entity: it carries a stable surrogate key (GAP_ABSENCE_PLAN_ID) and a business key, with associated descriptive and processing attributes captured in a satellite-like manner via audit columns such as CREATION_DATE, LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER. This classification should be treated as a design suggestion rather than a strict architectural mandate.

Key Information Stored

The table is documented with 11 columns. The most significant are:

• GAP_ABSENCE_PLAN_ID — the surrogate primary key, enforcing the PQP_GAP_ABSENCE_PLANS_PK constraint and uniquely identifying each absence plan row.
• ABSENCE_ATTENDANCE_ID — foreign key to PER_ABSENCE_ATTENDANCES; ties the plan to the underlying absence attendance record. Together with PL_ID it forms the unique business key PQP_GAP_ABSENCE_PLANS_UK1.
• PL_ID — part of the business key. It identifies the plan definition referenced by the plan row (for example, the retirement plan or absence plan context relevant to benefits/payroll processing).
• ASSIGNMENT_ID — links the absence plan to a specific employee assignment, enabling assignment-level absence processing.
• LAST_GAP_DAILY_ABSENCE_DATE — the most recent date on which daily absence processing was performed for the plan, used to drive incremental recalculation.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — supporting the standard EBS "Who" columns and optimistic locking.

The pairing of ABSENCE_ATTENDANCE_ID and PL_ID rather than GAP_ABSENCE_PLAN_ID as the unique key emphasizes that a single absence attendance may map to multiple absence plans.

Common Use Cases and Queries

Typical scenarios include verifying which absence plan is attached to a given absence attendance, tracing the daily absence results produced for that plan, and reporting on absence plan activity for a specific assignment.

A common join pattern links the plan header to its absences:

• Join PQP_GAP_ABSENCE_PLANS to PER_ABSENCE_ATTENDANCES on ABSENCE_ATTENDANCE_ID to retrieve the underlying absence and employee context.
• Join to PQP_GAP_DAILY_ABSENCES on GAP_ABSENCE_PLAN_ID to retrieve daily absence rows for the plan.
• Join to PQP_GAP_DURATION_SUMMARY on GAP_ABSENCE_PLAN_ID to obtain aggregated duration results.

A representative query pattern:

SELECT p.GAP_ABSENCE_PLAN_ID, p.ASSIGNMENT_ID, p.ABSENCE_ATTENDANCE_ID,
       p.LAST_GAP_DAILY_ABSENCE_DATE
FROM   HR.PQP_GAP_ABSENCE_PLANS p
WHERE  p.ASSIGNMENT_ID = :assignment_id;

Reporters commonly filter on LAST_GAP_DAILY_ABSENCE_DATE to identify plans pending recalculation, and on the audit columns to perform change-tracking and data-conversion reconciliation.

Related Objects

• PER_ABSENCE_ATTENDANCES — referenced via PQP_GAP_ABSENCE_PLANS.ABSENCE_ATTENDANCE_ID; the source absence record.
• PQP_GAP_DAILY_ABSENCES — child table referencing PQP_GAP_ABSENCE_PLANS.GAP_ABSENCE_PLAN_ID; holds daily absence detail.
• PQP_GAP_DURATION_SUMMARY — child table referencing GAP_ABSENCE_PLAN_ID; holds summarized duration results.
• Business key references to PL_ID link to plan definition tables in the HR benefits/payroll domain.