Search Results hxc_absence_type_elements




Overview
Explore in AI Chat

Overview

HXC_ABSENCE_TYPE_ELEMENTS is a table owned by the HXC schema within the Oracle E-Business Suite Time and Labor Engine product. It functions as a cross-reference or association table that links absence attendance types to element types. In Oracle EBS 12.1.1 and 12.2.2, this table enables the Time and Labor Engine to determine which payroll or compensation elements correspond to a particular absence category, thereby supporting accrual, absence tracking, and element feed processing across the HRMS suite.

The table is documented as having five columns and is classified, using a heuristic Data Vault model, as standalone. This classification is a modeling suggestion rather than a mandated design; it implies the table does not sit within a broader hub-and-satellite dependency chain in the mined foreign-key structure. Functionally, however, it behaves as an intersection or link-style object, resolving a many-to-many relationship between absence attendance types and element types.

Key Information Stored

The table contains five documented columns, of which the following are the most significant:

  • ABSENCE_ATTENDANCE_TYPE_ID — Identifies the absence attendance type to which the element association applies. This is one component of the composite business key.
  • ELEMENT_TYPE_ID — Identifies the element type linked to the absence attendance type. This is the other component of the composite business key.
  • EDIT_FLAG — Controls whether the associated context of the absence type and element mapping may be edited by end users, governing maintenance behaviour within the configuration UI.
  • UOM — Unit of measure associated with the mapping, typically expressing whether the element is measured in hours, days, or another unit relevant to the absence entry.
  • ABSENCE_CATEGORY — Categorizes the absence, providing a grouping attribute that may drive reporting, eligibility, or processing rules.

The primary key is documented as HXC_ABSENCE_TYPE_ELEMENTS_UK, a unique index defined over (ELEMENT_TYPE_ID, ABSENCE_ATTENDANCE_TYPE_ID). A second unique index, HXC_ABSENCE_TYPE_ELEMENTS_FK, is documented over (ELEMENT_TYPE_ID, ABSENCE_ATTENDANCE_TYPE_ID), reinforcing the composite uniqueness of the relationship. Notably, no separate single-column surrogate key is documented; the business key itself serves as the primary key. The documented unique indexes therefore represent the business-key candidates.

Common Use Cases and Queries

Typical use cases centre on absence configuration and element feed reporting. Administrators and developers query this table to validate which elements are attached to a given absence type before running absence processing, or to audit mappings after a configuration change.

A representative query retrieves all element mappings for a specific absence type:

  • SELECT element_type_id, absence_attendance_type_id, edit_flag, uom, absence_category FROM hxc.hxc_absence_type_elements WHERE absence_attendance_type_id = :p_absence_type_id;

To identify elements without a corresponding absence mapping, a NOT EXISTS pattern against the table is commonly used. Reporting extracts frequently join this table back to element and absence definition tables to produce configuration listings, and to confirm the EDIT_FLAG and UOM values that govern end-user behaviour.

Related Objects

The following objects are most significant in relation to HXC_ABSENCE_TYPE_ELEMENTS, joined on the documented key columns:

  • HXC_ABSENCE_ATTENDANCE_TYPES — joined on ABSENCE_ATTENDANCE_TYPE_ID to resolve absence type definitions.
  • PAY_ELEMENT_TYPES_F (Payroll) — joined on ELEMENT_TYPE_ID to resolve element type names and classifications.
  • HXC_ABSENCE_CATEGORIES or equivalent category reference — aligned to the ABSENCE_CATEGORY column.
  • PAY_ELEMENT_TYPES_VL and related element views — used in reporting to present element descriptions alongside absence mappings.
  • HXC_ABSENCE_TYPE_ELEMENTS_UK and HXC_ABSENCE_TYPE_ELEMENTS_FK — the unique indexes enforcing relationship integrity.

Collectively, these objects support the configuration and validation of absence-to-element associations within the Time and Labor Engine.