Results for “hxt_add_elem_info”

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

Overview

HXT_ADD_ELEM_INFO is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined over the Time and Labor (HXT) product family. Its purpose is to present the currently effective rows of the additional element information setup used by Time and Labor to describe how time is categorized and valued for elements such as earnings, absences, and premiums. The view is a date-filtered projection of the underlying transactional setup table HXT_ADD_ELEM_INFO_F, exposing the same 47 columns but restricting the result set to rows whose effective date range brackets the current application session's effective date.

Because user searches frequently converge on the premium_amount column, the view is most commonly encountered when resolving the monetary value associated with a premium element — for example, the shift differential rate or premium dollar value applied when a premium type is processed. The view therefore functions as a reporting and integration surface: it shields consumers from the underlying date-effective table, applies session-aware effective dating automatically, and presents a stable, queryable shape for extracts, custom reports, and interface programs.

Underlying Base Objects

Two objects are referenced in the documented view definition:

• HXT_ADD_ELEM_INFO_F (SYNONYM) — the base table holding the actual additional element information records, including the effective start and end dates and the premium amount attribute.
• FND_SESSIONS (SYNONYM) — the Oracle Application Object Library session table, used to establish the effective date for the current user session.

The view text selects all listed columns from HXT_ADD_ELEM_INFO_F and applies the predicate that EFFECTIVE_START_DATE is less than or equal to, and EFFECTIVE_END_DATE is greater than or equal to, the EFFECTIVE_DATE obtained from FND_SESSIONS for the session identified by USERENV('SESSIONID'). This design means the view does not perform joins that multiply rows; it is a filtered, single-source projection. The session-driven date filter is significant because it makes query results deterministic within a given session and consistent with the effective dating behavior expected by Time and Labor processing logic.

Key Columns

The columns below are the most operationally significant within the documented structure:

• ID — Primary identifier for the additional element information record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective boundaries that the view predicates against the session effective date.
• ELEMENT_TYPE_ID — Foreign reference to the element type to which the additional information applies.
• EARNING_CATEGORY — Classifies the earning context associated with the record.
• ABSENCE_TYPE / ABSENCE_POINTS — Define absence classification and the point value assigned to absence processing.
• PREMIUM_TYPE — Identifies the premium category being configured.
• PREMIUM_AMOUNT — The monetary value of the premium. This is the column most often targeted by searches for premium_amount against this view.
• PROCESSING_ORDER — Determines the sequence in which additional element information is evaluated.
• EXPENDITURE_TYPE — Maps the record to the appropriate expenditure classification.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and LAST_UPDATED_BY capture standard EBS audit information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield segments available for client-specific extension.

Common Use Cases and Queries

The most frequent scenario is retrieving the effective premium amount for a given element type or premium type. A representative query is:

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

A second common pattern filters to a specific element and inspects the effective window:

• SELECT id, element_type_id, effective_start_date, effective_end_date, premium_amount FROM apps.hxt_add_elem_info WHERE element_type_id = :p_element_type_id;

Integration and extract programs use the view to reconcile premium configuration against element definitions, comparing premium amounts across effective records. Because the result set is automatically scoped to the session effective date, developers must remember that querying the view outside an initialized EBS session — or in a session with an unexpected effective date — will yield a different set of rows than the underlying table. When historical or future-dated premium amounts are required, queries should target HXT_ADD_ELEM_INFO_F directly rather than the view.