Results for “per_absence_attendance_typ_pk”

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

Overview

APPS.PER_ABS_ATTENDANCE_TYPES_VL is a multilingual (VL) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents the definition of absence and attendance types used by the Oracle HRMS/Advanced Benefits absence management functionality. Absence attendance types are the configurable building blocks that classify how employee time away from work is recorded — for example sickness, vacation, maternity leave, or overtime — and drive entitlement, accrual, and payroll processing rules.

The view's role in reporting and integration is to expose a single, language-resolved, application-owned source of truth for these type definitions. Because it is owned by APPS and follows the standard Oracle Multilingual (MLS) pattern, it returns the name of each absence type translated into the session's language. External systems, Discoverer workbooks, BI Publisher reports, and custom PL/SQL integrations query this view rather than the underlying tables directly, ensuring they respect language settings and the standard column set.

The user searched for "per_absence_attendance_typ_pk", which is the primary key index on the base table PER_ABSENCE_ATTENDANCE_TYPES. This hint is embedded in the view text to force an index-driven join between the base table and the translation table, making the view efficient for lookups by absence attendance type identifier.

Underlying Base Objects

The view is defined over two documented synonyms: PER_ABSENCE_ATTENDANCE_TYPES, aliased as B in the view text, and PER_ABS_ATTENDANCE_TYPES_TL, aliased as TL. The first holds the core (language-independent) attributes of each absence attendance type, keyed by ABSENCE_ATTENDANCE_TYPE_ID. The second is the translation table, which stores the display NAME of the type per LANGUAGE and shares the same ABSENCE_ATTENDANCE_TYPE_ID.

The two are joined on ABSENCE_ATTENDANCE_TYPE_ID, with the translation table further restricted by TL.LANGUAGE = userenv('LANG'), so only the row matching the current session language is returned. A pair of index hints references PER_ABSENCE_ATTENDANCE_TYP_PK and PER_ABSENCE_ATTENDANCE_TYPES_TL_PK to promote an efficient nested-loop join on the primary keys rather than full table scans.

Key Columns

• ABSENCE_ATTENDANCE_TYPE_ID — Primary key that uniquely identifies each absence/attendance type.
• BUSINESS_GROUP_ID — The HR business group (organization) that owns the definition.
• NAME — The translated display name sourced from the TL table; the main descriptor shown to users.
• ABSENCE_CATEGORY — Classification of the absence (for example sickness or vacation).
• HOURS_OR_DAYS — Unit of measure for the type, indicating whether duration is recorded in hours or days.
• INCREASING_OR_DECREASING_FLAG — Indicates whether the entry increases or decreases the related balance.
• INPUT_VALUE_ID — Link to the input value used to drive element/balance processing.
• DATE_EFFECTIVE / DATE_END — Effective dating that bounds when the definition is active.
• ABSENCE_OVERLAP_FLAG — Controls whether overlapping absences are permitted.
• ASSIGNMENT_STATUS_TYPE_ID, USER_ROLE, ADVANCE_PAY — Supporting configuration attributes for assignment status and pay handling.
• ATTRIBUTE1–20 and INFORMATION1–20 — Descriptive flexfield segments and extra information fields for extensibility.
• ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER — Standard WHO/audit and concurrency columns.

Common Use Cases and Queries

Typical uses include building absence-type lookup lists for reports, validating a type ID passed from an interface, and reconciling configured types against payroll elements. A multilingual join is handled automatically, so translated names appear without extra effort.

Selecting active types for a business group:

SELECT absence_attendance_type_id, name, absence_category, hours_or_days
FROM apps.per_abs_attendance_types_vl
WHERE business_group_id = :p_bg_id
AND SYSDATE BETWEEN date_effective AND NVL(date_end, SYSDATE);

Looking up a single type (leverages the PER_ABSENCE_ATTENDANCE_TYP_PK index):

SELECT name, absence_category, increasing_or_decreasing_flag
FROM apps.per_abs_attendance_types_vl
WHERE absence_attendance_type_id = :p_type_id;

These patterns support reporting, validation, and integration while honoring the documented base-object structure and session-language resolution.