Results for “hxc_resource_rules_v”

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

Overview

The HXC_RESOURCE_RULES_V view is a reporting and integration construct within the Oracle E-Business Suite Time and Labor Engine (HXC) product family. It exposes resource rule definitions used by the Time and Labor Engine to determine which workers, assignments, or populations are eligible to charge time against a given preference hierarchy or resource. In EBS 12.1.1 and 12.2.2, the object resides in the APPS schema with a status of VALID and is defined as a UNION ALL-style compound query over the HXC_RESOURCE_RULES base synonym, enriched by joins to preference hierarchies, people records, and standard lookup meanings.

Because resource rule eligibility can be defined either at a broad level (for example, all people) or at a granular level (specific persons), the view flattens these variants into a single consumable result set. This makes it well suited for reporting, diagnostic queries, and downstream integrations that need a denormalized, human-readable representation of rule eligibility without manually resolving lookup codes or preference hierarchy identifiers.

Underlying Base Objects

The view's documented definition draws on several base objects. The primary transactional table is HXC_RESOURCE_RULES (referenced via synonym), which stores the rule header including name, business group, legislation, eligibility criteria type, preference hierarchy, evaluation order, and resource type. HXC_PREF_HIERARCHIES supplies the preference hierarchy name. HR_STANDARD_LOOKUPS is central to the view's purpose: one branch of its UNION constrains LOOKUP_TYPE to 'HXC_ELIG_CRITERIA_TYPE' with APPLICATION_ID 809, and returns the lookup MEANING alongside each rule so that the otherwise opaque eligibility criteria type code becomes readable.

The second branch additionally joins PER_PEOPLE_X to resolve eligibility criteria IDs of type 'PERSON' into a full person name. The documented referenced base objects also include HR_GENERAL (used in the DECODE that normalizes the sentinel END_OF_TIME date to NULL), HR_API, HR_LOOKUPS, HR_LOCATIONS, HR_ORGANIZATION_UNITS, HR_PERSON_NAME, HR_SECURITY, PER_ASSIGNMENTS_F, PER_BUSINESS_GROUPS, PER_JOBS_TL, PER_ORGANIZATION_STRUCTURES, PER_PERSON_TYPES, PER_POSITIONS, PAY_PAYROLLS_F, PAY_PEOPLE_GROUPS, FND_GLOBAL, FND_RESPONSIBILITY_TL, and the HXC_RESOURCE_RULES_UTILS package. These supporting objects supply validation, security, and descriptive context used across the view's branches.

Key Columns

• ROW_ID — The ROWID of the underlying HXC_RESOURCE_RULES row, useful for direct row identification.
• RESOURCE_RULE_ID — Primary identifier of the resource rule.
• NAME — The user-defined name of the rule.
• BUSINESS_GROUP_ID — Owning business group for multi-tenant partitioning.
• LEGISLATION_CODE — Legislative context under which the rule applies.
• ELIGIBILITY_CRITERIA_TYPE — Code indicating how eligibility is scoped (for example 'ALL_PEOPLE' or 'PERSON').
• MEANING — The decoded lookup meaning from HR_STANDARD_LOOKUPS for the criteria type.
• ELIGIBILITY_CRITERIA_ID — Identifier used for granular criteria, such as a PERSON_ID.
• PREF_HIERARCHY_ID and the associated hierarchy NAME — The preference hierarchy the rule is bound to.
• RULE_EVALUATION_ORDER — Sequence controlling precedence when rules are evaluated.
• RESOURCE_TYPE — Classifies the resource that the rule governs.
• START_DATE / END_DATE — Effective dating; a sentinel END_OF_TIME value is normalized to NULL.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit and concurrency columns.

Common Use Cases and Queries

A frequent scenario is auditing which resource rules exist for a given eligibility criteria type, or locating rules bound to a specific preference hierarchy. The following query lists active rules joined to their hierarchy and decoded criteria meaning:

• SELECT resource_rule_id, name, meaning, eligibility_criteria_type, resource_type FROM apps.hxc_resource_rules_v WHERE business_group_id = :p_bg_id ORDER BY rule_evaluation_order;

Users who search on "hr_standard_lookups" are often troubleshooting why a resource rule resolves to an unexpected value. Because the view already joins HR_STANDARD_LOOKUPS on LOOKUP_TYPE 'HXC_ELIG_CRITERIA_TYPE' and APPLICATION_ID 809, comparing the view's MEANING column against the raw lookup definitions isolates configuration gaps:

• SELECT lookup_code, meaning FROM hr_standard_lookups WHERE lookup_type = 'HXC_ELIG_CRITERIA_TYPE' AND application_id = 809;
• SELECT name, eligibility_criteria_type, meaning FROM apps.hxc_resource_rules_v WHERE eligibility_criteria_type NOT IN ('ALL_PEOPLE','PERSON');

Integration and migration tasks benefit from the view's flattened structure when extracting rule definitions for external time collection systems, and the audit columns support incremental extraction by LAST_UPDATE_DATE. Because the view is a non-key-preserving UNION, consumers should treat it as read-only and apply business group or legislation predicates to limit result sets.