Results for “hxc_resource_elig_pref_v”

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

Overview

HXC_RESOURCE_ELIG_PREF_V is an APPS-owned view within the HXC – Time and Labor Engine product of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. The view exposes the effective eligibility preferences assigned to a resource, resolved to a single row per resource and preference code. Its defining characteristic is the correlated subquery in the WHERE clause: a row qualifies only when its RULE_EVALUATION_ORDER equals the maximum RULE_EVALUATION_ORDER returned by HXC_RESOURCE_ALL_ELIG_PREF_V for the same RESOURCE_ID and PREFERENCE_CODE pairing. In effect, the view presents the highest-priority (last-evaluated) rule outcome for each resource/preference combination rather than the complete rule population.

Because it returns one deterministic value per preference, the view functions as a reporting and integration surface for consumers that require the final resolved eligibility preference without applying rule-ranking logic themselves. It is read-only and is not a table, so no DML is permitted against it.

Underlying Base Objects

The documented referenced base objects are HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), HXC_RESOURCE_ALL_ELIG_PREF_V (VIEW), and HXC_RESOURCE_RULES_UTILS (PACKAGE). The view's own SELECT text confirms HXC_RESOURCE_ALL_ELIG_PREF_V as its immediate and structurally dominant source; all forty-three projected columns originate from that view alias (V1). The HR packages supply supporting logic — HR_GENERAL for date and business-group utilities, HR_PERSON_NAME for formatted person name derivation, HR_SECURITY for security profile enforcement at the row level, and HXC_RESOURCE_RULES_UTILS for the rule-evaluation machinery embedded in the underlying eligibility preference view. HR_SECURITY participation indicates that query results may be filtered according to the operator's security profile, which is significant when the view is used to drive self-service or administrative reports.

Key Columns

• RESOURCE_ID – Identifier of the resource (person) to whom the preference applies; the primary correlation key.
• RULE_EVALUATION_ORDER – Sequence value determining the priority of the rule that produced the row. Only the maximum value per RESOURCE_ID/PREFERENCE_CODE survives the filter.
• RULE_NAME – Name of the eligibility rule that generated the preference result.
• BUSINESS_GROUP_ID – Owning business group, supporting multi-organization and legislative partitioning.
• LEGISLATION_CODE – Country or legislation context of the preference.
• PREFERENCE_ID, PREFERENCE_CODE, PREFERENCE_NAME – Identifier, code, and descriptive name of the eligibility preference.
• EDIT_ALLOWED, DISPLAYED – Flags controlling whether the preference may be modified and whether it is surfaced in the user interface.
• HIERARCHY_NAME – Name of the hierarchy associated with the preference, indicating the structural context of rule inheritance.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE30 – Descriptive flexfield segments carrying customer-defined information.

Common Use Cases and Queries

Typical uses include validating which preference value ultimately prevails for a worker, diagnosing rule conflicts, and feeding downstream payroll or scheduling logic that expects a single resolved preference per code.

Retrieve resolved preferences for a specific resource:

• SELECT resource_id, preference_code, preference_name, rule_evaluation_order, rule_name, displayed
• FROM apps.hxc_resource_elig_pref_v
• WHERE resource_id = :p_resource_id
• ORDER BY preference_code;

Identify resources whose prevailing rule came from a particular rule name within a business group:

• SELECT resource_id, preference_code, rule_name, rule_evaluation_order
• FROM apps.hxc_resource_elig_pref_v
• WHERE business_group_id = :p_bg_id
• AND rule_name = :p_rule_name;

Because the row-projection logic duplicates a correlated MAX subquery, performance is optimized by predicates on RESOURCE_ID and PREFERENCE_CODE. Reporting queries should also anticipate HR_SECURITY filtering, which may restrict visible rows to those within the operator's authorized organization hierarchy. The view references date-effective logic in HXC_RESOURCE_ALL_ELIG_PREF_V, so results reflect the eligibility state as currently effective rather than the full historical rule set.