Search Results hxt_earn_group_types_pk




Overview
Explore in AI Chat

Overview

HXT_EARN_GROUP_TYPES is a reference and setup table within the Oracle E-Business Suite Time and Labor (HXT) module. It stores the definitions of earning group types, which act as a classification layer above individual earning groups. In Oracle Time and Labor, earnings are organized hierarchically: earning group types categorize earning groups, and earning groups in turn aggregate individual earnings for processing, costing, and payroll transfer. This table provides the top-level taxonomy that governs how earning groups are grouped and retrieved by earning policies.

The table resides in the HXT schema and is marked VALID in the ETRM 12.2.2 data model. From a Data Vault modeling perspective, the metadata heuristics classify this object as hub-leaning. This suggests it functions as a stable, business-key-driven entity table that anchors descriptive attributes, with dependent tables referencing it through foreign keys. The classification is a modeling suggestion rather than a mandatory design constraint.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • ID — The surrogate primary key, enforced by the HXT_EARN_GROUP_TYPES_PK constraint. This is the value referenced by foreign keys in dependent tables.
  • NAME — The business-key candidate for the earning group type, enforced by the unique index HXT_EARN_GROUP_TYPES_UK. This is the user-facing identifier.
  • DESCRIPTION — Free-text description of the earning group type.
  • FCL_EG_TYPE — A classification or flexfield-related indicator associated with the earning group type and its earning group behavior.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — Date-effective range columns establishing when a given earning group type definition is valid. These support date-tracked setup and datetracked queries.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit and concurrency information for the row.

The distinction between ID and NAME is important: ID is the internal surrogate identifier used for joins and referential integrity, while NAME is the unique business identifier that administrators recognize and search on.

Common Use Cases and Queries

Typical usage centers on administrative validation of earning group type setup and on joining configuration data to understand how earnings flow into policies and groups. A representative query joining to earning groups is:

  • SELECT egt.id, egt.name, eg.name FROM hxt_earn_group_types egt, hxt_earn_groups eg WHERE eg.egt_id = egt.id;
  • Reporting on active, date-effective types: filter on SYSDATE BETWEEN effective_start_date AND effective_end_date.
  • Audit reporting using last_update_date and last_updated_by to track configuration changes.
  • Determining which earning policies depend on a given type by joining through HXT_EARNING_POLICIES on egt_id.

These patterns are common during implementation validation, data migration verification, and production support investigations involving Time and Labor earning setup.

Related Objects

The following objects reference or depend on HXT_EARN_GROUP_TYPES through documented foreign keys:

  • HXT_EARNING_POLICIES — References this table via EGT_ID → HXT_EARN_GROUP_TYPES.ID, linking earning policies to their earning group type.
  • HXT_EARN_GROUPS — References this table via EGT_ID → HXT_EARN_GROUP_TYPES.ID, associating individual earning groups with their parent type.
  • HXT_EARN_GROUP_TYPES_PK — The primary key constraint on ID.
  • HXT_EARN_GROUP_TYPES_UK — The unique key constraint on NAME.

Because both dependent tables carry an EGT_ID column pointing back to this table's ID, HXT_EARN_GROUP_TYPES serves as a central hub for Time and Labor earning configuration, and any change to a row in this table can cascade semantically through policies and earning groups.