Results for “hxc_time_entry_rules”

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

Overview

HXC_TIME_ENTRY_RULES is the configuration table that stores Time Entry Rules within the Oracle E-Business Suite Time and Labor Engine (HXC) product. Time entry rules define the conditional validation and derivation logic applied to timecards as they are entered, validated, approved, and processed. Each row represents a discrete rule definition that the Time and Labor Engine evaluates against time entry data, determining whether recorded time is valid, how it should be grouped, and which formula logic should be invoked to derive or transform values.

The table resides in the HXC schema and is present in both Oracle EBS 12.1.1 and 12.2.2. The documented physical schema for 12.2.2 exposes 48 columns, reflecting the standard EBS pattern of a compact set of functional attributes accompanied by a broad set of descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE30) and audit columns. From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification: the table carries descriptive attributes and depends on a parent reference to HXC_MAPPINGS through MAPPING_ID, while itself being referenced by usage records. This is a heuristic suggestion rather than a documented architectural mandate.

Key Information Stored

The most significant columns in this table are:

• TIME_ENTRY_RULE_ID — the surrogate primary key, uniquely identifying each rule row. It is the column named in the HXC_TIME_ENTRY_RULES_PK constraint.
• NAME and DESCRIPTION — the user-facing rule identifier and its explanatory text.
• RULE_USAGE — indicates the context in which the rule applies, distinguishing rule categories within the Time and Labor Engine.
• FORMULA_ID — references the formula that implements the rule's computation or validation logic.
• MAPPING_ID — the foreign key to HXC_MAPPINGS, linking the rule to its mapping definition.
• LEGISLATION_CODE and BUSINESS_GROUP_ID — scope the rule to a specific legislative environment and business group, enforcing multi-tenant and localization constraints.
• START_DATE and END_DATE — the effective dating window during which the rule is active.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• The audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — record row provenance.

The documented unique index, HXC_TIME_ENTRY_RULES_PK, spans TIME_ENTRY_RULE_ID and ZD_EDITION_NAME. The presence of ZD_EDITION_NAME indicates this object participates in the EBS edition-based redefinition scheme used to support online patching in Release 12.2.x. The ATTRIBUTE1–ATTRIBUTE30 columns constitute the descriptive flexfield segment storage.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include retrieving active rules for a business group, identifying which formula backs a given rule, and auditing rule usage across applications. A representative query joining the rule to its mapping is:

• SELECT r.TIME_ENTRY_RULE_ID, r.NAME, r.RULE_USAGE, r.FORMULA_ID, m.MAPPING_ID FROM HXC.HXC_TIME_ENTRY_RULES r, HXC.HXC_MAPPINGS m WHERE r.MAPPING_ID = m.MAPPING_ID AND r.BUSINESS_GROUP_ID = :p_bg_id AND SYSDATE BETWEEN r.START_DATE AND NVL(r.END_DATE, SYSDATE);

Additional use cases include auditing which rules are referenced by application usages, exporting rule metadata for migration between environments, and tracing date-effective rule changes. Because rows are edition-aware, queries in a 12.2.x environment should account for ZD_EDITION_NAME when running against the editioned view.

Related Objects

• HXC_MAPPINGS — parent reference joined via HXC_TIME_ENTRY_RULES.MAPPING_ID = HXC_MAPPINGS.MAPPING_ID.
• HXC_DATA_APP_RULE_USAGES — dependent table linking rules to data application contexts through TIME_ENTRY_RULE_ID; the FK direction runs from the usage table to this table.
• HXC_TIME_ENTRY_RULES_PK — the primary key constraint enforcing uniqueness on TIME_ENTRY_RULE_ID and ZD_EDITION_NAME.
• HXC_TIME_ENTRY_RULES — self-referenced by its own constraints and frequently joined with HXC_MAPPINGS to resolve rule-to-mapping relationships.

These relationships establish HXC_TIME_ENTRY_RULES as a central configuration reference consumed by the Time and Labor Engine's validation and mapping framework.