Results for “per_absence_attendance_types”

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

Overview

PER_ABSENCE_ATTENDANCE_TYPES is a core Human Resources (PER) setup table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the user-defined absence and attendance types available to an enterprise. Each row defines a distinct category of absence — such as vacation, sick leave, or unpaid leave of absence — that can subsequently be assigned to employees through absence records. The table resides in the HR schema and contains 66 documented columns, making it one of the richer configuration entities in the absence management model.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as hub-leaning. This heuristic suggestion reflects that the table anchors a stable business key (the absence attendance type identity) around which transactional and descriptive data accumulates. It is effectively the reference or lookup hub for absence events, with the actual absence occurrences captured in satellite-style detail tables.

Key Information Stored

The table is keyed by a surrogate primary key, ABSENCE_ATTENDANCE_TYPE_ID, defined through the constraint PER_ABSENCE_ATTENDANCE_TYP_PK. A separate unique index, PER_ABSENCE_ATTENDANCE_TYP_UK2, enforces the business-key combination of NAME and BUSINESS_GROUP_ID, ensuring that absence type names are unique within each business group.

The most significant columns include:

• ABSENCE_ATTENDANCE_TYPE_ID — the surrogate primary key referenced throughout the absence subsystem.
• NAME — the user-defined display name of the absence type; a business-key candidate.
• BUSINESS_GROUP_ID — scopes the type to a specific business group and is a foreign key to HR_ALL_ORGANIZATION_UNITS.
• ABSENCE_CATEGORY — classifies the absence (for example, sickness or vacation).
• ASSIGNMENT_STATUS_TYPE_ID — a foreign key to PER_ASSIGNMENT_STATUS_TYPES controlling the assignment status applied during absence.
• HOURS_OR_DAYS — indicates whether the absence is measured in hours or days.
• INCREASING_OR_DECREASING_FLAG — denotes whether the accrual balance increases or decreases.
• ADVANCE_PAY and ABSENCE_OVERLAP_FLAG — control payroll advance handling and overlap rules.
• DATE_EFFECTIVE and DATE_END — the effective-dating range for the type.
• INPUT_VALUE_ID — links to the input value used for payroll element processing.
• Audit columns such as CREATION_DATE, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER, plus the ATTRIBUTE1–20 and INFORMATION1–20 descriptive flexfield segments.

Common Use Cases and Queries

Typical usage centers on reporting absence type configuration, joining to transactional absence records, and validating setup before data load. A common query retrieves all absence types for a business group:

• SELECT absence_attendance_type_id, name, absence_category, hours_or_days FROM per_absence_attendance_types WHERE business_group_id = :p_bg_id;
• Counting absence records per type by joining to PER_ABSENCE_ATTENDANCES on ABSENCE_ATTENDANCE_TYPE_ID.
• Auditing effective dates to identify expired or future-dated types.
• Checking the ASSIGNMENT_STATUS_TYPE_ID linkage to understand status behavior during leave.

These patterns support HR administration, absence trending reports, and integration extracts feeding downstream payroll or benefits processing.

Related Objects

The table participates in several referential relationships documented in the ETRM metadata. It references HR_ALL_ORGANIZATION_UNITS through BUSINESS_GROUP_ID and PER_ASSIGNMENT_STATUS_TYPES through ASSIGNMENT_STATUS_TYPE_ID. Conversely, it is referenced by PER_ABSENCE_ATTENDANCES, PER_ABS_ATTENDANCE_REASONS, and PAY_NET_CALCULATION_RULES, all of which carry an ABSENCE_ATTENDANCE_TYPE_ID foreign key. The Benefits module extends this through BEN_ELIG_LOA_RSN_PRTE_F and BEN_LOA_RSN_RT_F. Together these objects form the absence management and leave-of-absence ecosystem within Oracle EBS.