Results for “hxt_variances”

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

Overview

HXT_VARIANCES is a table in the Oracle E-Business Suite Time and Labor (HXT) product schema, introduced and supported across the 12.1.1 and 12.2.2 release lines. It stores earning variance thresholds — high and low boundaries — that Time and Labor uses to evaluate calculated timecard results against expected values. When an employee's processed earnings fall outside the configured tolerance band, the variance acts as a rule-driven signal for exception handling, approval routing, or downstream payroll correction.

The table functions as a rule and threshold repository rather than a transactional fact store. It is keyed by a combination of a functional period and a variance type, and it carries both the boundary values and the dimensional context (organization, location, element type, balance) that determine where the threshold applies. Under the heuristic Data Vault classification derived from its foreign key structure, HXT_VARIANCES is modeled as a standalone object — it holds no dependent child tables and behaves as a reference or configuration satellite of its own, anchored by its composite primary key rather than referencing a parent hub through a foreign key.

Key Information Stored

The primary key is HXT_VARIANCES_PK, a composite business key defined on FCL_PERIOD and VAR_TYPE_ID. These two columns uniquely identify a variance threshold definition and are the only documented unique index, making them the authoritative business key candidates for integration and lookup logic.

• FCL_PERIOD — the functional period to which the threshold applies; part of the primary key.
• VAR_TYPE_ID — the variance type identifier; part of the primary key and the principal discriminator for a threshold row.
• VAR_TYPE — the descriptive form of the variance type, useful for reporting without joining to a lookup.
• HIGH and LOW — the upper and lower tolerance boundaries that define the acceptable band for the earning.
• AVERAGE — the central or expected value against which the high and low limits are compared.
• DATE_FROM and DATE_TO — the effective date range that controls when the threshold row is active.
• ELEMENT_TYPE_ID — the earning or element against which the variance is evaluated.
• ORGANIZATION_ID and LOCATION_ID — the organizational and location scope of the threshold.
• BALANCE_NAME, BALANCE_DIMENSION, and BALANCE_LEVEL — the balance context used to resolve which accumulated value the variance applies to.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO audit columns.

Common Use Cases and Queries

The table is consulted during Time and Labor rule evaluation to flag timecards whose computed earnings exceed the configured high or low bound. Typical reporting asks include: which thresholds are currently effective for a given period, and which variance types are defined for a specific organization or element.

• Effective threshold lookup: query rows where FCL_PERIOD matches the period in review and the effective window brackets the current date (DATE_FROM <= SYSDATE AND (DATE_TO IS NULL OR DATE_TO >= SYSDATE)).
• Scoped threshold list: filter on ORGANIZATION_ID, LOCATION_ID, and ELEMENT_TYPE_ID to retrieve the tolerance band applicable to a population.
• Boundary reporting: select VAR_TYPE, AVERAGE, LOW, and HIGH to present a simple variance band report for auditors.
• Integration extract: use the FCL_PERIOD and VAR_TYPE_ID composite key as the stable identifier when moving threshold definitions between environments.

Related Objects

HXT_VARIANCES is a standalone table with no documented foreign keys to parent hubs, so related objects are referenced through the identifier columns it carries rather than through PK/FK constraints.

• HXT_VARIANCES_PK — the primary key index over FCL_PERIOD and VAR_TYPE_ID that enforces uniqueness.
• Variance type lookups — resolved via VAR_TYPE_ID and VAR_TYPE for descriptive reporting.
• Pay element definitions — joined through ELEMENT_TYPE_ID to identify the earning being tested.
• Organization and location masters — joined through ORGANIZATION_ID and LOCATION_ID to scope thresholds to the correct HR context.
• Balance and dimension definitions — referenced by BALANCE_NAME, BALANCE_DIMENSION, and BALANCE_LEVEL.
• Time and Labor rule processing — the runtime consumer that applies HIGH, LOW, and AVERAGE during timecard evaluation.