Search Results hxt_tim_col_util




Overview
Explore in AI Chat

Overview

HXT_TIM_COL_UTIL is the core utility package body within the Oracle E-Business Suite Time and Labor (ETRM) module, owned by the APPS schema and classified as a utility API. It provides the shared validation, lookup, and derivation services that support time collection and timecard processing across self-service and batch interfaces. The package encapsulates the logic required to resolve human-resources and payroll entities — people, assignments, grades, locations, projects, tasks, elements, and earning policies — and to validate the attributes submitted during timecard entry. Its status is VALID, and it is a well-established dependency within the Time and Labor object graph.

Key Procedures and Functions

The package exposes seventeen documented procedures and functions, organized around resolution and validation:

No parameter lists are documented here; callers should reference the package specification for exact signatures.

Tables Accessed

The package reads and writes across Time and Labor, payroll, and HR tables, including HXT_EARNING_POLICIES, HXT_PREV_WAGE_BASE, HXT_SUM_HOURS_WORKED, and the HXT_ALL_PROJECTS_V and HXT_ALL_TASKS_V views for earning policy, wage base, and project/task lookups. Payroll integration draws on PAY_ASSIGNMENT_LINK_USAGES_F, PAY_COST_ALLOCATION_KEYFLEX, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, and PAY_ELEMENT_TYPES_F_TL. Human resources data comes from PER_ALL_ASSIGNMENTS_F, PER_GRADES, PER_PEOPLE_F, and PER_BUSINESS_GROUPS, while FND_SESSIONS, HR_LOCATIONS, and HR_LOOKUPS support session, location, and lookup resolution. PLITBLM is referenced for PL/SQL index-by table handling.

Usage Notes

HXT_TIM_COL_UTIL is an internal utility, not a user-facing API; it is invoked by six other Time and Labor packages and by timecard entry forms and concurrent processes that need consistent entity resolution and validation. Typical invocation occurs when a timecard is submitted or approved, when a payroll element must be derived for time transfer, or when a batch process validates large volumes of time entries. Custom extensions integrating with Time and Labor should call the package specification rather than replica its logic, ensuring validation rules remain consistent across releases. Because the body reports VALID and is referenced by other database objects, it should be treated as a stable dependency in any deployment.