Search Results hxc_time_entry_rules_pk




Overview
Explore in AI Chat

Overview

The HXC_TIME_ENTRY_RULES table is a core data repository within the Oracle E-Business Suite (EBS) Time and Labor Engine (HXC). It serves as the master definition table for time entry rules, which are fundamental business rules governing how timecards are entered, validated, and processed. These rules are critical for enforcing organizational policies related to time reporting, such as allowed entry periods, rounding rules, and validation criteria. The table's role is to store the rule definitions that are subsequently associated with specific timecard layouts, time recipients, and other system components to control the time entry user experience and data integrity.

Key Information Stored

The primary data stored in this table defines the rule itself and its linkage to the rule's underlying logic. The most critical columns include:

  • TIME_ENTRY_RULE_ID: The unique primary key identifier (PK) for the rule definition.
  • MAPPING_ID: A foreign key (FK) column linking to the HXC_MAPPINGS table. This is a pivotal column, as it associates the rule definition with the specific PL/SQL function or mapping that contains the executable business logic for the rule.
  • Additional descriptive and control columns (implied by standard EBS design) would typically include creation dates, last update dates, and active status indicators, though they are not explicitly listed in the provided metadata.
The structure indicates that the table stores rule metadata, while the actual procedural logic is externalized, referenced via the MAPPING_ID.

Common Use Cases and Queries

This table is primarily accessed for configuration analysis, troubleshooting, and impact assessment during system changes. Common scenarios include identifying all rules using a specific mapping or function, and listing rules applied to a particular timecard layout. A typical query would join HXC_TIME_ENTRY_RULES with HXC_MAPPINGS to understand rule logic.

SELECT rule.time_entry_rule_id,
       map.name mapping_name,
       map.mapping_code
  FROM hxc_time_entry_rules rule,
       hxc_mappings map
 WHERE rule.mapping_id = map.mapping_id
   AND rule.time_entry_rule_id = :p_rule_id;

Another critical use case involves tracing rule usage via the foreign key relationship to HXC_DATA_APP_RULE_USAGES, which shows where the rule is applied within the system (e.g., to specific fields or blocks).

Related Objects

The HXC_TIME_ENTRY_RULES table is central to the Time and Labor rule engine, with key dependencies as per the provided metadata:

  • HXC_MAPPINGS: The parent table for the MAPPING_ID foreign key. This table stores the executable logic that the rule invokes.
  • HXC_DATA_APP_RULE_USAGES: A child table that records where and how each time entry rule is applied (e.g., to a specific time attribute or field group). The TIME_ENTRY_RULE_ID in this table is a foreign key back to HXC_TIME_ENTRY_RULES.
  • The existence of the primary key constraint HXC_TIME_ENTRY_RULES_PK ensures the uniqueness of the TIME_ENTRY_RULE_ID.
This network of relationships shows that HXC_TIME_ENTRY_RULES sits between the rule logic definition (HXC_MAPPINGS) and the rule's application points (HXC_DATA_APP_RULE_USAGES).