Results for “date_notification”

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

Overview

PER_ABSENCE_ATTENDANCES is the core Human Resources (PER) transaction table in Oracle E-Business Suite that records an individual employee's absence from, or attendance at, work for a defined period. Each row captures a single absence or attendance event — for example sickness, maternity, or other absence types — together with its start and end dates, duration, authorisation, and workflow context. In Enterprise Business Suite releases 12.1.1 and 12.2.2 the table resides in the HR schema and is exposed through the Absence Management functionality of Oracle HRMS, including the SSP statutory sick pay and SMP maternity processes in the localised UK payroll solution.

Following standard Data Vault heuristics derived from its foreign key structure, PER_ABSENCE_ATTENDANCES is classified as satellite-leaning. It carries a surrogate primary key of its own while depending on parent entities such as the person, the absence type, and the business group, and it holds the descriptive, time-bound attributes (dates, hours, days, status) that describe a single absence event. It is best modelled as a satellite over the absence/person hub rather than as a hub in its own right.

Key Information Stored

The table contains 97 documented columns. The following are the most significant:

• ABSENCE_ATTENDANCE_ID — Surrogate primary key (PER_ABSENCE_ATTENDANCES_PK). Uniquely identifies each absence or attendance record.
• BUSINESS_GROUP_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS, scoping the record to a legislative business group.
• ABSENCE_ATTENDANCE_TYPE_ID — Foreign key to PER_ABSENCE_ATTENDANCE_TYPES, defining the category of absence (e.g. sickness, maternity).
• ABS_ATTENDANCE_REASON_ID — Foreign key to PER_ABS_ATTENDANCE_REASONS, giving the specific reason.
• PERSON_ID — The employee or applicant to whom the absence belongs.
• DATE_START, DATE_END — Actual start and end dates of the absence or attendance period.
• DATE_PROJECTED_START, DATE_PROJECTED_END — Anticipated dates where the actuals are not yet known.
• ABSENCE_DAYS, ABSENCE_HOURS — Quantified duration of the absence.
• AUTHORISING_PERSON_ID, REPLACEMENT_PERSON_ID — The approver and any replacement covering the absence.
• ABSENCE_CASE_ID — Foreign key to PER_ABSENCE_CASES, linking the record to a broader absence case.
• MATERNITY_ID — Foreign key to SSP_MATERNITIES, used for SMP-related absences.
• APPROVAL_STATUS, OBJECT_VERSION_NUMBER — Workflow approval state and optimistic locking column.
• LINKED_ABSENCE_ID — Self-referencing foreign key allowing linked absences.
• ATTRIBUTE1–ATTRIBUTE20 and ABS_INFORMATION1–ABS_INFORMATION30 — Descriptive flexfield segments for client-specific configuration.

The surrogate key is ABSENCE_ATTENDANCE_ID; there is no separate documented business-key unique index other than the primary key itself.

Common Use Cases and Queries

Typical reporting needs include absence frequency, sickness duration, and statutory pay eligibility. A common pattern lists all absences for a person within a date range:

SELECT a.absence_attendance_id,
       a.person_id,
       t.name        AS absence_type,
       a.date_start,
       a.date_end,
       a.absence_days,
       a.approval_status
FROM   per_absence_attendances a,
       per_absence_attendance_types t
WHERE  a.absence_attendance_type_id = t.absence_attendance_type_id
AND    a.person_id  = :p_person_id
AND    a.date_start BETWEEN :p_from AND :p_to;

Absence aggregation by type and business group supports HR analytics dashboards, while joins to SSP_MEDICALS and SSP_STOPPAGES support statutory sick pay calculations in UK payroll. Workflow-based queries filter on APPROVAL_STATUS to surface pending notifications, and self-joins on LINKED_ABSENCE_ID reconstruct related absence chains.

Related Objects

• PER_ABSENCE_ATTENDANCE_TYPES — Provides absence categorisation via ABSENCE_ATTENDANCE_TYPE_ID.
• PER_ABS_ATTENDANCE_REASONS — Supplies the reason through ABS_ATTENDANCE_REASON_ID.
• HR_ALL_ORGANIZATION_UNITS — Business group definition via BUSINESS_GROUP_ID.
• PER_ABSENCE_CASES — Parent case referenced by ABSENCE_CASE_ID.
• SSP_MATERNITIES and SSP_MEDICALS — Statutory pay records referencing ABSENCE_ATTENDANCE_ID.
• SSP_STOPPAGES — SSP stoppage entries keyed to the absence.
• PER_NL_ABSENCE_CHANGES and PER_NL_ABSENCE_ACTIONS — Dutch absence change and action history.
• PQP_GAP_ABSENCE_PLANS — Absence plans referencing the attendance record.

These relationships make PER_ABSENCE_ATTENDANCES the central transaction anchor for absence analytics, statutory pay processing, and workflow-driven absence management across Oracle EBS Human Resources.