Search Results hxc_time_entry_rule_outcome

Overview

APPS.HXC_TIME_ENTRY_RULE_COMPS_V is a reporting view within the Oracle E-Business Suite Time and Labor (shared with Oracle Time and Labor / OTL and Project Time) module. It exposes the components that make up Time Entry Rules — the configured definitions that determine how timecards are validated, processed, and routed through the time entry workflow. Each row represents a single rule component belonging to a Time Entry Rule Group, together with descriptive attributes resolved from related lookup and rule views. Rather than requiring report and integration developers to join the low-level entity group component table against rule and lookup definitions manually, this view performs those joins internally and presents a denormalized, human-readable result set. The view is commonly used to build rule configuration extracts, audit reports, and interface queries where a rule's outcome must be displayed by its descriptive meaning rather than its internal code. The view carries the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER, supporting both reporting and controlled updates where the underlying components are maintained.

Underlying Base Objects

The view is defined over three principal sources joined together, as documented in the ETRM metadata:

• HXC_ENTITY_GROUP_COMPS (accessed through its synonym) — supplies the core component rows, aliased as egc. The join predicates restrict rows to egc.entity_type = 'TIME_ENTRY_RULES', ensuring only rule components are returned. This table provides the component identifier, the parent entity group identifier, the rule entity identifier, and the descriptive flexfield attribute columns.
• HXC_TIME_ENTRY_RULES_V — supplies rule-level descriptive data, aliased as ter, joined via ter.time_entry_rule_id = egc.entity_id. It contributes the rule name, rule usage, mapping, formula, description, and effective dates.
• HR_LOOKUPS (view) — aliased as lk, joined on lk.lookup_type = 'HXC_TIME_ENTRY_RULE_OUTCOME' and lk.lookup_code = egc.attribute1. This resolves the stored outcome code into its display meaning.

The referenced base objects also include the packages FND_GLOBAL, HR_API, and HR_GENERAL. HR_GENERAL supplies the END_OF_TIME constant used in the DECODE expression that nulls out the maximum end date, while FND_GLOBAL and HR_API are invoked by the underlying rule view for session and HR security context.

Key Columns

• row_id — the ROWID of the underlying component row, used for direct row addressing.
• time_entry_group_comp_id — primary identifier of the rule component.
• time_entry_rule_group_id — identifier of the parent rule group.
• time_entry_rule_id — identifier of the individual Time Entry Rule.
• time_entry_rule_name — the rule's descriptive name.
• rule_outcome — the raw outcome code stored in egc.attribute1.
• rule_outcome_name — the lookup meaning for the outcome, resolved from HR_LOOKUPS. This is the column users typically search on to display outcomes by description.
• rule_usage / rule_usage_name — the rule usage code and its descriptive name.
• mapping_id / mapping_name — the mapping applied by the rule.
• formula_id / formula_name — the fast formula identifier and its description.
• description, start_date, end_date — rule narrative and effective dating; end_date is returned as null when it equals the HR_GENERAL.END_OF_TIME sentinel.
• attribute_category and attribute1–attribute30 — descriptive flexfield context and segment values, with ATTRIBUTE1 also surfaced as rule_outcome.

Common Use Cases and Queries

Typical scenarios include extracting rule configuration for review, reporting which outcome each component produces, and auditing effective-dated rule definitions. Because the view resolves the outcome lookup, it is well suited to presenting outcomes by name.

List all components for a rule group:

• SELECT time_entry_rule_name, rule_outcome, rule_outcome_name, rule_usage_name FROM apps.hxc_time_entry_rule_comps_v WHERE time_entry_rule_group_id = :group_id ORDER BY time_entry_rule_name;

Filter by outcome description:

• SELECT time_entry_rule_id, time_entry_rule_name, rule_outcome_name FROM apps.hxc_time_entry_rule_comps_v WHERE rule_outcome_name = 'Reject';

Report currently effective rules and their formulas:

• SELECT time_entry_rule_name, rule_usage_name, formula_name, start_date, end_date FROM apps.hxc_time_entry_rule_comps_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)) ORDER BY time_entry_rule_name;