Results for “hxt_time_detail”

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

Overview

HXT_TIME_DETAIL is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the Oracle Time and Labor (OTL) module. Its header declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the defining owner, which is consistent with an internal engine component invoked from within the OTL processing stack rather than a public, externally supported API. The package is primarily concerned with the detailed calculation and re-explosion of timecard hours — that is, decomposing a worked time entry into its constituent earning lines, applying earning policies and rules, resolving shift differentials, hour deduction rules, rotation schedules, and summary hour structures, and persisting the resulting detail rows in the HXT_DET_HOURS_WORKED tables.

The source header identifies internal bug fix identifiers (for example Bug 7359347 and Bug 10123886), reflecting the package's role as a maintained internal utility that has evolved with OTL patch levels. Notably, the package maintains global state such as a session date (g_det_session_date), a flag governing holiday paid status (g_holiday_sdp_paid), and a PL/SQL associative array (g_parent_to_re_explode) used to queue parent timecard records that require recalculation. This design supports batch re-processing of affected timecard hierarchies after upstream changes.

Key Procedures and Functions

The documented package metadata lists a single procedure: GENERATE_SPECIAL. Based on the package's record type definitions — particularly re_explode_det_info, which carries earning policy, assignment, element type, rate, cost center, shift, and timekeeping attributes — GENERATE_SPECIAL is understood to generate and persist special time detail rows, typically associated with non-standard earning conditions such as special shift premiums, holiday pay, or manually adjusted detail. It operates within the broader re-explosion logic in which parent timecard entries are queued (via the parent-to-re-explode table) and their associated detail lines regenerated.

No parameter lists are documented in ETRM, and no signature details should be assumed. The remaining members of the package are internal, including record and table type declarations that support cursor processing and detail row construction.

Tables Accessed

The package reads and writes a substantial set of OTL and payroll configuration tables:

• HXT_DET_HOURS_WORKED_F / HXT_SUM_HOURS_WORKED_F — the primary detail and summary hour tables into which calculated time lines are inserted or updated.
• HXT_TIMECARDS_F — the timecard header source driving detail generation.
• PAY_ELEMENT_TYPES_F — element definitions used to link calculated hours to payroll elements.
• HXT_ADD_ELEM_INFO_F — supplementary element information for earnings assignment.
• HXT_EARNING_POLICIES, HXT_EARNING_RULES, HXT_EARN_GROUPS, HXT_EARN_GROUP_TYPES — the earning policy framework determining how hours are credited.
• HXT_HOUR_DEDUCTION_RULES — rules governing deduction of hours (for example, meal breaks).
• HXT_ROTATION_SCHEDULES, HXT_SHIFTS, HXT_WORK_SHIFTS, HXT_SHIFT_DIFF_RULES — shift and rotation structures used to derive shift differential treatment.
• PLITBLM — the standard EBS PL/SQL index-by table of numbers utility type, used internally for bulk processing.

Usage Notes

HXT_TIME_DETAIL is an internal engine package rather than a supported public API. It is referenced by three other packages, meaning it is invoked programmatically from the OTL calculation, retry, or timecard processing stack. Direct invocation from custom code is not recommended, as neither parameter lists nor behavior are documented. It is typically triggered indirectly through OTL concurrent programs and forms that create or correct timecard entries, and through the re-explosion mechanism after earning rules or labor schedules change. Implementers extending OTL should rely on supported APIs and concurrent processes rather than calling this package directly.