Results for “hxt_premium_type”

26 results




Overview
Explore in AI Chat

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

Overview

HXT_PAY_ELEMENT_TYPES_F_DDF_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the HXT (Time and Labor) product family and is documented in ETRM for both release 12.1.1 and 12.2.2. The view presents descriptive flexfield (DDF) style attribute information for payroll element types as configured for the OTL (Oracle Time and Labor) application. Its purpose is to expose the additional element attributes — earning category, absence type, absence points, premium handling, processing order, and expenditure type — in a form that reports, concurrent programs, and integration interfaces can consume without directly joining the underlying flexfield definition table.

Because it is a view rather than a table, it carries no storage of its own and always reflects the current state of its underlying base object. This makes it appropriate for real-time reporting and for OTL rules and retrieval processes that need to classify time entries according to the payroll element they will eventually feed. The object status is VALID in the documented environment.

Underlying Base Objects

The view is defined over a single base object: HXT_ADD_ELEM_INFO_F, accessed through a synonym. The view text is a straightforward projection:

The "_F" suffix on the base table indicates a date-effective (datetracked) entity, and the view preserves the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns so that consumers can apply their own effective-date filtering. No joins, unions, or aggregations are present in the view definition; it is a thin exposure layer whose value lies in presenting the "additional element information" attributes under the HXT_PAY_ELEMENT_TYPES_F_DDF_V name alongside descriptive flexfield-oriented column aliases (for example, HXT_EARNING_CATEGORY, HXT_ABSENCE_TYPE, and HXT_PREMIUM_TYPE).

Key Columns

  • ELEMENT_TYPE_ID — Primary reference to the payroll element type for which additional information is defined; the principal join key to element and element-type entities.
  • HXT_EARNING_CATEGORY (EARNING_CATEGORY) — Classification of the earning, used to group elements for reporting and rules evaluation.
  • HXT_ABSENCE_TYPE (ABSENCE_TYPE) — Identifies the absence classification associated with the element, where applicable.
  • HXT_ABSENCE_POINTS (ABSENCE_POINTS) — Point value accrued or consumed by the element for absence accounting.
  • HXT_PREMIUM_TYPE (PREMIUM_TYPE) and HXT_PREMIUM_AMOUNT (PREMIUM_AMOUNT) — Define whether a premium applies and its monetary basis.
  • HXT_PROCESSING_ORDER (PROCESSING_ORDER) — Numeric sequence controlling the order in which the element is processed.
  • HXT_EXPENDITURE_TYPE (EXPENDITURE_TYPE) — Expenditure type used when the element cost is transferred to projects.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective bounds for each row of additional element information.

Common Use Cases and Queries

Typical uses include validating element configuration before enabling OTL time entry, driving premium and processing-order logic in time rules, and supplying expenditure type defaults for project costing. The following query lists currently effective additional element information:

  • SELECT element_type_id, hxt_earning_category, hxt_absence_type, hxt_absence_points, hxt_premium_type, hxt_premium_amount, hxt_processing_order, hxt_expenditure_type FROM hxt_pay_element_types_f_ddf_v WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date ORDER BY element_type_id;
  • SELECT element_type_id, hxt_premium_amount FROM hxt_pay_element_types_f_ddf_v WHERE hxt_premium_type IS NOT NULL AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Because the view is date-effective, callers should always restrict on SYSDATE or an explicit date range to avoid returning historical rows.