Results for “per_absence_cases”

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

Overview

The PER_ABSENCE_CASES table resides in the HR schema and belongs to the Oracle Human Resources (PER) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the details of absence cases, where an absence case represents a collection of absences belonging to a single employee that is grouped manually according to user-defined criteria. Rather than treating each absence record in isolation, this table provides a container that consolidates multiple absence events into a single logical case, supporting tracking, categorization, and analysis of extended or related absence patterns such as sickness episodes, medical leave groupings, or disciplinary tracking.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests the table behaves primarily as an independent entity rather than a pure hub, link, or satellite. In practice, it functions like a hub-like container anchored on a surrogate key, with descriptive and descriptive-flexfield columns acting as satellite-style attributes. Modelers should treat it as a central entity that other absence records reference.

Key Information Stored

The table contains 75 documented columns in the 12.2.2 physical schema. The most operationally significant columns are:

• ABSENCE_CASE_ID — the surrogate primary key, sourced from PER_ABSENCE_CASES_PK. This is the unique identifier referenced by child absence records.
• BUSINESS_GROUP_ID — the operating unit/legislative context segregating data across business groups.
• PERSON_ID — identifies the employee whose absences are being grouped, the principal business-key candidate for locating cases per person.
• NAME — the user-defined name or label assigned to the absence case, the most common searchable business-key attribute.
• INCIDENT_ID — links the case to an incident or event record where relevant.
• ABSENCE_CATEGORY — categorizes the type of absence (for example sickness or unauthorized absence) grouping.
• AC_INFORMATION_CATEGORY and AC_INFORMATION1–AC_INFORMATION30 — the descriptive flexfield (DFF) context and segment values capturing client-specific case attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — supplementary attribute flexfield values.
• COMMENTS — free-text notes describing the case.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard audit and optimistic-locking columns.

While no secondary unique index is documented, PERSON_ID combined with NAME is the practical business-key candidate for identifying a case.

Common Use Cases and Queries

Typical scenarios include retrieving all cases for an employee, reporting on open cases by category, and joining cases to the individual absences they contain. Sample query patterns:

• List cases for a person: SELECT absence_case_id, name, absence_category FROM per_absence_cases WHERE person_id = :p_person_id AND business_group_id = :p_bg_id;
• Summarize case counts by category for a business group for reporting dashboards.
• Join cases to their constituent absences via PER_ABSENCE_ATTENDANCES.ABSENCE_CASE_ID to compute total absence days per case.
• Extract descriptive flexfield content (AC_INFORMATION_CATEGORY / AC_INFORMATIONn) for reporting on client-specific attributes.

Reporting use cases include absence-trend analysis, case aging, and compliance monitoring by absence category.

Related Objects

The principal documented relationship is a child-to-parent link from the absence attendance records:

• PER_ABSENCE_ATTENDANCES — references this table through ABSENCE_CASE_ID, making it the primary dependent object. Each attendance row can be assigned to a case.

Other significant associated objects, inferred from the PER product model, include PER_ALL_PEOPLE_F (joined via PERSON_ID), PER_BUSINESS_GROUPS (via BUSINESS_GROUP_ID), and the absence-category lookup objects referenced by ABSENCE_CATEGORY. The PER absence-case APIs and the Absence Management UI operate against this table and its child attendances as the underlying persistence layer.