Search Results hxc_time_entry_rule_comps_v




Overview
Explore in AI Chat

Overview

HXC_TIME_ENTRY_RULE_COMPS_V is an APPS-owned view within the Oracle Time and Labor Engine (HXC) product family, exposed across both Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the component-level definition of Time Entry Rules, resolving the raw component rows stored in the entity-group architecture into a denormalized, user-readable form. Time Entry Rules determine how reported time is processed (for example, whether an entry is accepted, rejected, or altered) based on mapping, formula, or usage logic. This view surfaces each rule component together with its rule name, outcome lookup meaning, rule usage, mapping, formula, and date-effectivity information, making it suitable for enquiry, reporting, and integration scenarios where the underlying tables would otherwise require multi-table joins.

Underlying Base Objects

The view is defined over the following documented objects. HXC_TIME_ENTRY_RULES_V is the driving rule definition view, supplying rule identifiers, names, usage, mapping, formula, description, and effective dates. HXC_ENTITY_GROUP_COMPS is a synonym for the component entity table, contributing the component surrogate key and descriptive flexfield attribute columns. HR_LOOKUPS is joined on LOOKUP_TYPE = 'HXC_TIME_ENTRY_RULE_OUTCOME' to translate the stored outcome code into a meaningful value. The view is further associated with the FND_GLOBAL, HR_API, and HR_GENERAL packages; HR_GENERAL is used in the view text to decode HR_GENERAL.END_OF_TIME to NULL for open-ended rules. The join predicate restricts HXC_ENTITY_GROUP_COMPS rows to ENTITY_TYPE = 'TIME_ENTRY_RULES', ensuring only rule components are returned.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling rule configuration across environments, auditing outcomes and formula assignments, and feeding downstream reporting. A common starting point is retrieval by rule identifier:

  • SELECT TIME_ENTRY_RULE_ID, TIME_ENTRY_RULE_NAME, RULE_OUTCOME_NAME, RULE_USAGE_NAME, FORMULA_NAME, START_DATE, END_DATE FROM APPS.HXC_TIME_ENTRY_RULE_COMPS_V WHERE TIME_ENTRY_RULE_ID = :p_rule_id;
  • SELECT RULE_OUTCOME, RULE_OUTCOME_NAME, COUNT(*) FROM APPS.HXC_TIME_ENTRY_RULE_COMPS_V GROUP BY RULE_OUTCOME, RULE_OUTCOME_NAME;
  • SELECT TIME_ENTRY_RULE_NAME, MAPPING_NAME, FORMULA_NAME FROM APPS.HXC_TIME_ENTRY_RULE_COMPS_V WHERE MAPPING_ID IS NOT NULL ORDER BY TIME_ENTRY_RULE_NAME;

Queries should be executed with the APPS schema or a synonym granting equivalent access, and callers should observe the effectivity dates when interpreting which rule versions were active for a given period.