Search Results hxt_absence_type




Overview
Explore in AI Chat

Overview

APPS.HXTFV_ADD_ELEM_INFO is a read-only Oracle E-Business Suite view that exposes configuration data for time and labor element information records. It is part of the HXT (Time and Labor / OTL) schema family and is defined over the HXT_ADD_ELEM_INFO_F base table, joined to PAY_ELEMENT_TYPES_F to resolve the human-readable element name. The view is intended for reporting and integration scenarios where additional element information — such as earning categories, absence types, premium types, and premium amounts — must be surfaced alongside the underlying payroll element definition.

In the context of the user search for hxt_premium_type, this view is the primary published object where the HXT_PREMIUM_TYPE lookup values are decoded into display values via HR_GENERAL.DECODE_LOOKUP. The column premium_type returns the decoded meaning rather than the raw lookup code, making the view directly suitable for end-user reports and extracts without further lookup translation.

Underlying Base Objects

The view is defined over three documented base objects:

  • HXT_ADD_ELEM_INFO_F (synonym) — the primary table holding additional element information records, including premium type, premium amount, earning category, absence type, and absence points.
  • PAY_ELEMENT_TYPES_F (synonym) — the payroll element type definition table, joined on element_type_id to supply element_name.
  • HR_GENERAL (package) — supplies the DECODE_LOOKUP function used to translate lookup codes for HXT_EARNING_CATEGORY, HXT_ABSENCE_TYPE, and HXT_PREMIUM_TYPE.

Both base tables are filtered by effective date ranges so that only currently active rows are returned: the join and filters require SYSDATE to fall between the effective_start_date and effective_end_date of both HXT_ADD_ELEM_INFO_F and PAY_ELEMENT_TYPES_F. The view carries the WITH READ ONLY clause, enforcing that no DML is permitted through it.

Key Columns

  • premium_type — decoded HXT_PREMIUM_TYPE lookup meaning; the column most relevant to the hxt_premium_type search.
  • premium_amount — the numeric premium amount associated with the element information record.
  • earning_category — decoded HXT_EARNING_CATEGORY value describing how earnings are categorized.
  • absence_type — decoded HXT_ABSENCE_TYPE value identifying the absence classification.
  • absence_points — points assigned for absence processing.
  • processing_order — sequence in which the element information is evaluated.
  • expenditure_type — expenditure classification associated with the record.
  • element_name — the payroll element name sourced from PAY_ELEMENT_TYPES_F.
  • attribute_category — the descriptive flexfield context for the record.
  • element_info_id and element_type_id — surrogate identifiers for the element information row and its parent element type.

Common Use Cases and Queries

Typical uses include reporting on premium-eligible elements, validating absence and earning category assignments, and feeding downstream extracts. A representative query listing premium configuration by element is:

  • SELECT element_name, premium_type, premium_amount, earning_category FROM apps.hxtfv_add_elem_info WHERE premium_type IS NOT NULL ORDER BY element_name;
  • SELECT element_name, absence_type, absence_points FROM apps.hxtfv_add_elem_info WHERE absence_type IS NOT NULL;
  • SELECT element_info_id, element_type_id, premium_type FROM apps.hxtfv_add_elem_info WHERE element_type_id = :p_element_type_id;

Because the view decodes lookups and resolves element names, it eliminates the need for callers to join PAY_ELEMENT_TYPES_F or invoke DECODE_LOOKUP manually. Queries referencing hxt_premium_type should target the premium_type column of this view rather than the raw HXT_ADD_ELEM_INFO_F table.