Results for “per_nl_absence_actions”

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

Overview

PER_NL_ABSENCE_ACTIONS is a Dutch localization ("NL") table in the PER — Human Resources product of Oracle E-Business Suite, owned by the HR schema. It stores the absence action records that support the Netherlands-specific absence and attendance tracking rules, which differ from the generic absence framework used in other legislations. Each row represents a discrete action associated with a Dutch absence record — for example, the registration, notification, or processing step tied to a period of employee absence — and links back to the parent absence entry in PER_ABSENCE_ATTENDANCES through the ABSENCE_ATTENDANCE_ID foreign key.

Under a heuristic Data Vault classification (mined from the documented FK structure), this object is modelled as standalone. In practice, it is best treated as a satellite annexed to the PER_ABSENCE_ATTENDANCES parent, since it carries descriptive and status attributes about an absence rather than acting as a hub of independent business keys. It is registered in ETRM as VALID for both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table contains 18 documented columns. The most significant are:

• ABSENCE_ACTION_ID — Surrogate primary key, enforced by PER_NL_ABSENCE_ACTIONS_PK. Uniquely identifies each Dutch absence action row.
• ABSENCE_ATTENDANCE_ID — Foreign key to PER_ABSENCE_ATTENDANCES, establishing the parent absence record to which the action belongs.
• EXPECTED_DATE — The anticipated date associated with the action, commonly used for planned absence milestones.
• DESCRIPTION — Free text describing the nature or reason of the absence action.
• ACTUAL_START_DATE / ACTUAL_END_DATE — The realised start and end of the absence period covered by the action.
• HOLDER — The person or entity (for example, the case holder or responsible party) associated with the action.
• COMMENTS — Additional narrative notes captured against the action.
• DOCUMENT_LINK and DOCUMENT_FILE_NAME — Reference and filename for an attached supporting document.
• ENABLED — Flag indicating whether the action is currently active.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATE_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY — Standard WHO audit columns recording creation and modification.

The metadata documents a unique index SYS_IL0000244026C00009$$, which is an internal LOB/index artifact rather than a business-key candidate; the surrogate ABSENCE_ACTION_ID is therefore the reliable identifier.

Common Use Cases and Queries

Typical scenarios include reporting Dutch absence actions tied to an employee's absence history, auditing document attachments, and reconciling expected versus actual absence dates.

• Actions for a given absence:
  SELECT action_id, expected_date, actual_start_date, actual_end_date, holder, enabled
FROM per_nl_absence_actions
WHERE absence_attendance_id = :p_absence_id;
• Open (enabled) actions:
  SELECT * FROM per_nl_absence_actions WHERE enabled = 'Y';
• Join to parent absence:
  SELECT a.absence_attendance_id, a.expected_date, a.description
FROM per_nl_absence_actions a, per_absence_attendances p
WHERE a.absence_attendance_id = p.absence_attendance_id;

These queries support localization reporting, absence dashboards, and data-migration validation scripts.

Related Objects

• PER_ABSENCE_ATTENDANCES — Parent table, joined via ABSENCE_ATTENDANCE_ID; the documented FK target.
• PER_NL_ABSENCE_ACTIONS_PK — Primary key constraint on ABSENCE_ACTION_ID.
• HR schema absence APIs — Dutch absence processing uses the same HR_ABSENCE API family that maintains the parent attendance record and its child actions.
• PER_ALL_PEOPLE_F — Used indirectly to resolve the person behind the absence when reporting the holder or employee.
• Standard WHO audit columns — Populated by EBS framework triggers shared across HR tables.

Because the table is a localized satellite, its dependency surface is narrow and centred on the generic absence framework.