Search Results delete_person_absence_changes

Overview

APPS.HR_NL_DAILY_SICK_AND_RECOVERY is a Dutch (NL) localization package within Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the statutory Netherlands sickness and recovery reporting obligations by intercepting changes made to absence records through the public person absence APIs and recording them in a dedicated audit table. The package does not itself create or modify absences; instead it functions as a user hook implementation that is called by the CREATE_PERSON_ABSENCE, UPDATE_PERSON_ABSENCE, and DELETE_PERSON_ABSENCE APIs whenever an absence of category 'sickness' is affected.

The core design intent is to maintain a traceable log of every sickness-related absence event in PER_NL_ABSENCE_CHANGES, tagged with an UPDATE_TYPE of 'START', 'UPDATE', 'END', or 'DELETE'. This supports Dutch legal requirements around timely reporting of sickness and recovery to authorities and internal payroll or benefit processing. The package is registered under APPS and classified as OTHER, and it is referenced by three other packages, reflecting its role as a shared utility within the localisation layer.

Key Procedures and Functions

• INSERT_PERSON_ABSENCE_CHANGES — Invoked as a user hook from CREATE_PERSON_ABSENCE. It writes a row into PER_NL_ABSENCE_CHANGES with UPDATE_TYPE 'START' for every insert into PER_ABSENCE_ATTENDANCES for the sickness category.
• UPDATE_PERSON_ABSENCE_CHANGES — Invoked as a user hook from UPDATE_PERSON_ABSENCE. It writes a row into PER_NL_ABSENCE_CHANGES with UPDATE_TYPE 'UPDATE' or 'END' for every update to a sickness absence record.
• DELETE_PERSON_ABSENCE_CHANGES — Invoked as a user hook from DELETE_PERSON_ABSENCE. It writes a row with UPDATE_TYPE 'DELETE' for every deletion of a sickness absence record.
• PURGE_PER_NL_ABSENCE_CHANGES — A purge routine that removes rows from PER_NL_ABSENCE_CHANGES older than one year. It is intended to run through a concurrent program scheduled weekly.
• UPDATE_REPORTED_ABSENCE_CHGS — Updates previously reported absence change records, supporting reconciliation of reported versus current sickness data.
• GET_EIT_SICK_REASON — Retrieves the Extra Information Type value representing the stated sickness reason, used to enrich or validate reported absence data.

Tables Accessed

• PER_ABSENCE_ATTENDANCES — The source of sickness absence entries and updates.
• PER_NL_ABSENCE_CHANGES — The target audit table holding captured 'START', 'UPDATE', 'END', and 'DELETE' events.
• PER_ABSENCE_ATTENDANCE_TYPES — Resolves absence categories to identify sickness records.
• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — Provide person and assignment context for the absence.
• PER_PEOPLE_EXTRA_INFO and PER_ASSIGNMENT_EXTRA_INFO — Supply Extra Information Type values, including the sickness reason.
• PER_ORG_STRUCTURE_ELEMENTS — Supports organisation-level resolution for reporting.
• FND_SESSIONS and DUAL — Used for session context and singleton queries.

Usage Notes

The package is not normally called directly by end users. It is wired into the person absence APIs as a user hook, so any absence maintained through the standard absence entry forms, self-service pages, or integrated APIs triggers it automatically for Dutch sickness records. The purge procedure is exposed through a concurrent program and should be scheduled weekly to enforce the one-year retention limit. Because the package is referenced by three other packages and relies on APPS synonyms, customisations should extend rather than modify it, and any direct invocation should respect the documented hook contract to avoid duplicate or inconsistent entries in PER_NL_ABSENCE_CHANGES.