Search Results hxc_resource_rules_pk

Overview

HXC_RESOURCE_RULES is a table in the HXC schema of Oracle E-Business Suite, belonging to the Time and Labor Engine product. It stores Resource Rules, the configuration records that determine how resources — most commonly people, but potentially other resource types — are evaluated, filtered, and sequenced during time and labor processing. In the Oracle Time and Labor (OTL) architecture, these rules drive eligibility decisions: which resources qualify for a given preference hierarchy, in what evaluation order, and under what effective-dating constraints.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table's dominant dependency is a single parent reference to HXC_PREF_HIERARCHIES through PREF_HIERARCHY_ID, which is characteristic of descriptive, attribute-bearing detail that hangs off a core parent rather than a many-to-many link construct. This classification should be treated as a modeling suggestion rather than a definitive architectural statement.

Key Information Stored

The documented physical schema in 12.2.2 carries 18 columns, of which the following are the most significant:

• RESOURCE_RULE_ID — the surrogate primary key, enforced by the HXC_RESOURCE_RULES_PK index. This is the unique identifier referenced by dependent objects.
• ZD_EDITION_NAME — the editioning column. It participates in the primary key alongside RESOURCE_RULE_ID in the unique index HXC_RESOURCE_RULES_PK (RESOURCE_RULE_ID, ZD_EDITION_NAME), making the composite a business-key candidate under the edition-based redefinition model used in 12.2.2.
• PREF_HIERARCHY_ID — foreign key to HXC_PREF_HIERARCHIES, defining the preference hierarchy to which the rule belongs.
• NAME — the user-facing name of the rule.
• ELIGIBILITY_CRITERIA_TYPE and ELIGIBILITY_CRITERIA_ID — together they identify the criteria used to determine resource eligibility.
• RULE_EVALUATION_ORDER — the sequence in which rules are applied when multiple rules compete.
• RESOURCE_TYPE — the category of resource the rule governs.
• START_DATE and END_DATE — the effective-dating window for the rule.
• LEGISLATION_CODE and BUSINESS_GROUP_ID — the multi-tenant and localization keys scoping the rule to a legal jurisdiction and business group.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit and optimistic-locking columns.

Common Use Cases and Queries

Resource rules are queried primarily to diagnose why a resource qualified for (or was excluded from) a preference hierarchy, and to report on active rule configuration. A typical retrieval of active rules for a hierarchy is:

• SELECT rr.resource_rule_id, rr.name, rr.rule_evaluation_order, rr.resource_type FROM hxc_resource_rules rr WHERE rr.pref_hierarchy_id = :p_id AND trunc(sysdate) BETWEEN rr.start_date AND rr.end_date ORDER BY rr.rule_evaluation_order;
• Joining to HXC_PREF_HIERARCHIES to resolve the parent hierarchy name for a configuration listing.
• Filtering by BUSINESS_GROUP_ID and LEGISLATION_CODE for multi-org and localization-aware reporting.
• Reconciling ELIGIBILITY_CRITERIA_ID values against their criteria source to explain evaluation outcomes.

Because the table is effective-dated, reporting queries should always constrain on START_DATE and END_DATE unless historical rule state is explicitly required. In 12.2.2 environments, queries that must span editions should account for ZD_EDITION_NAME.

Related Objects

• HXC_PREF_HIERARCHIES — the parent object, joined via HXC_RESOURCE_RULES.PREF_HIERARCHY_ID = HXC_PREF_HIERARCHIES.PREF_HIERARCHY_ID. This is the sole documented foreign-key relationship.
• HXC_RESOURCE_RULES_PK — the primary key index on (RESOURCE_RULE_ID, ZD_EDITION_NAME), used for direct row retrieval.
• Preference and eligibility criteria tables referenced indirectly through ELIGIBILITY_CRITERIA_TYPE and ELIGIBILITY_CRITERIA_ID.
• Time and Labor rule-processing APIs that consume resource rule rows during preference evaluation.
• Standard OTL concurrent programs and BI Publisher reports that read preference hierarchy configuration.