Results for “hxt_add_elem_info_x”

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

Overview

HXT_ADD_ELEM_INFO_X is an APPS-owned database view within the HXT (Time and Labor) product of Oracle E-Business Suite, valid in both the 12.1.1 and 12.2.2 releases. It presents configuration data describing how time entries are translated into payroll or costing elements — earning categories, absence handling, premium treatment, processing order and expenditure classification. Unlike the underlying date-tracked table, this view exposes only the row that is effective as of the current system date, giving callers a single "as of today" record per configuration entry without requiring them to write date-bounded predicates themselves.

Because it is a plain (non-materialized) view, it introduces no additional storage and simply inherits the privileges, indexes and constraints of its base object. Its principal role is as a read-only reporting and integration surface: concurrent programs, Oracle Time and Labor rules, and external interfaces query it to resolve which earning, absence or premium definition applies to a given element type on the current business date.

Underlying Base Objects

The view is defined exclusively over HXT_ADD_ELEM_INFO_F, which is exposed in APPS as a synonym. The _F suffix denotes a date-tracked ("fully" dated) table carrying EFFECTIVE_START_DATE and EFFECTIVE_END_DATE; the _X view is the conventional Oracle naming counterpart that filters that date range down to the current effective row.

The defining query is a straight projection of all columns from the base table, with the predicate WHERE EFFECTIVE_START_DATE <= TRUNC(SYSDATE) AND EFFECTIVE_END_DATE >= TRUNC(SYSDATE). The use of TRUNC(SYSDATE) means effectiveness is evaluated at day granularity, so any configuration whose start date is today or earlier and whose end date is today or later is returned. Rows that are future-dated or already expired are excluded. Consequently, the view can never return more than the currently effective version of each logical configuration record, and historical or prospective enquiry must be directed to the base table instead.

Key Columns

• ID — Primary identifier of the configuration record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-track bounds; always bracket the current date in rows returned by this view.
• ELEMENT_TYPE_ID — Foreign key to the element type to which the earning, absence or premium attributes apply.
• EARNING_CATEGORY — Classification used in earning and costing calculations.
• ABSENCE_TYPE — Indicates the absence classification associated with the element, distinguishing absence-driven entries from regular earnings.
• ABSENCE_POINTS — Accrual or point value applied for the absence.
• PREMIUM_TYPE and PREMIUM_AMOUNT — Premium rule and monetary or rate value applied.
• PROCESSING_ORDER — Sequence in which the element is processed relative to others.
• EXPENDITURE_TYPE — Costing/expenditure classification passed to Projects and costing flows.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield segments for client-specific extensions.

Common Use Cases and Queries

Typical uses include validating that an element is correctly configured for the current date, listing absence-enabled elements for a given element type, and feeding external payroll or interface extracts that require only currently effective rules.

• List effective absence configuration for an element type:

  SELECT element_type_id, absence_type, absence_points, earning_category
  FROM   apps.hxt_add_elem_info_x
  WHERE  element_type_id = :p_element_type_id;

• Find elements that carry premium treatment:

  SELECT id, element_type_id, premium_type, premium_amount, processing_order
  FROM   apps.hxt_add_elem_info_x
  WHERE  premium_type IS NOT NULL
  ORDER BY processing_order;

• Join to element types for descriptive reporting:

  SELECT a.element_type_id, a.absence_type, a.expenditure_type
  FROM   apps.hxt_add_elem_info_x a
  WHERE  a.earning_category = :p_category;

For historical or future-dated comparisons, query HXT_ADD_ELEM_INFO_F directly with explicit date predicates, since the view intentionally restricts output to the current effective set.