Search Results hxc_preference_evaluation




Overview
Explore in AI Chat

Overview

APPS.HXC_PREFERENCE_EVALUATION is a PL/SQL package body in the Oracle E-Business Suite Time and Labor (HXC) module. Its business purpose is to resolve, evaluate, and apply worker time preferences and scheduling rules at the point of time entry, approval, or processing. Preferences in Time and Labor govern behaviours such as which timecard layout a worker sees, how time is defaulted, whether certain entries are permitted, and how resource-level rules are interpreted against hierarchies of workers, organizations, and assignments. The package evaluates the applicable preference definitions for a given resource (typically a person or assignment) by traversing preference hierarchies and matching them against the resource rules, then returns or stores the resolved result set.

The object is validated and status VALID in the documented environment. It is classified under API classification OTHER, indicating it is an internal engine package rather than a published open interface. Notably, the package is referenced by 46 other database objects, confirming its role as a foundational utility within the Time and Labor preference framework, despite not itself being referenced by any foreign key–style dependency in the dependency listing.

Key Procedures and Functions

The documented package exposes 26 procedures and functions. Core preference operations are handled by RESOURCE_PREFERENCES, RESOURCE_PREFS_BULK, SET_RESOURCE_PREFERENCES, and GET_RESOURCE_PREFERENCES, which respectively evaluate preferences for a resource, perform bulk evaluation, persist resolved preferences, and retrieve them. RESOURCE_PREF_SEP and RESOURCE_PREF_ERRCODE act as supporting accessors for separated preference data and error code reporting.

Utility and control routines include CLEAR_SORT_PREF_TABLE_CACHE, which clears cached sort-preference data, and NUM_HIERARCHY_OCCURANCES, which counts occurrences within a preference hierarchy. Migration-related behaviour is governed by MIGRATION_MODE and SET_MIGRATION_MODE, used when preference data is being transitioned between representations or releases.

Worker context is resolved through EMPLOYMENT_ENDED, ASSIGNMENT_LAST_EFF_DT, EVALUATION_DATE, CHECK_NUMBER, RETURN_VERSION_ID, and GET_TC_RESP. These functions determine whether employment has ceased, identify the last effective date of an assignment, establish the correct evaluation date for preference matching, and retrieve the timecard responsibility or version identifier relevant to the evaluation. Together they ensure preferences are evaluated against the worker's correct employment and assignment state at a specific point in time.

Tables Accessed

The package reads preference definitions and hierarchy metadata from HXC_PREF_DEFINITIONS and HXC_PREF_HIERARCHIES, and resolves applicability through HXC_RESOURCE_RULES. Worker and assignment context is drawn from PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_PERIODS_OF_PLACEMENT, PER_PERSON_TYPES, PER_PERSON_TYPE_USAGES_F, PER_ASSIGNMENT_STATUS_TYPES, PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_ELEMENTS, and PER_ORG_STRUCTURE_VERSIONS. Organizational context derives from HR_ALL_ORGANIZATION_UNITS, while security and access context come from FND_USER and FND_RESPONSIBILITY.

Time-specific data is read from HXC_TIME_ATTRIBUTES, HXC_TIME_ATTRIBUTE_USAGES, HXC_TIME_BUILDING_BLOCKS, HXC_TIMECARD_SUMMARY, and HXC_LATEST_DETAILS, enabling preferences to be evaluated against existing timecard content. The package also depends on FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_UTILITY, HXC_RESOURCE_RULES_UTILS, and the PLITBLM PL/SQL table utility, which supply session context, profile values, HR lookups, and in-memory collection handling.

Usage Notes

HXC_PREFERENCE_EVALUATION is an internal engine package rather than a directly callable public API. It is invoked indirectly by Time and Labor forms, self-service timecard pages, and concurrent programs that build or validate timecards, where it supplies the resolved preference set for the current worker and responsibility. Because it is referenced by 46 other packages, custom code should avoid modifying or bypassing its logic; extensions should instead call the appropriate public Time and Labor APIs or mirror its evaluation ordering through supported interfaces. Any custom invocation should respect session initialization via FND_GLOBAL and profile settings, and should account for migration mode where active.