Search Results create_holiday_hours

Overview

APPS.HXT_TIME_CLOCK is a PL/SQL package body belonging to the Oracle E-Business Suite time and labor module (HXT schema, "Time and Labor"). Its business purpose is to provide the programmatic backbone for recording employee time against a time clock, translating raw clock events (start and end times) into timecard records, work hours, holiday hours, and the batch structures that payroll requires. The package encapsulates the logic needed to determine the applicable time period for a date worked, verify or create a timecard for a person, assemble payroll batches, and persist hours into the HXT tables. Because it is the implementation body, all logic resides here; the corresponding package specification exposes only the entry points the application layer is intended to call. The metadata catalogues the package with an API classification of OTHER, indicating it is an internal rather than a published public API, and it is referenced by zero other packages, so it is used directly by front-end forms and concurrent process code rather than being consumed by other PL/SQL units.

Key Procedures and Functions

The documented package metadata lists two named routines for ETRM 12.2.2: RECORD_TIME and LOG_CLOCK_ERRORS. The source excerpt additionally reveals a broader set of internal helper functions, including GET_TIME_PERIOD, CHECK_FOR_TIMECARD, CREATE_TIMECARD, CREATE_BATCH, FIND_EXISTING_BATCH, CREATE_HOLIDAY_HOURS, and RECORD_HOURS_WORKED.

• RECORD_TIME — The principal public entry point. It accepts an employee identifier and assignment plus start and end times, and returns a status code and error buffer. It orchestrates the clock-in/clock-out recording flow, resolving the person, locating or creating the timecard, and delegating the hour-writing work to the internal helpers.
• LOG_CLOCK_ERRORS — The routine the user searched for. It captures and persists errors arising during time-clock processing. Given the package's dependency on FND_USER and FND_SESSIONS, it records diagnostic information associated with the current user session, allowing administrators to trace failed clock transactions.
• GET_TIME_PERIOD — Resolves the payroll time period covering a date worked, returning period identifier, start date, and end date.
• CHECK_FOR_TIMECARD / CREATE_TIMECARD — Determine whether a timecard already exists for a person and period, and create one when absent, returning the auto-generation flag and timecard identifier.
• CREATE_BATCH / FIND_EXISTING_BATCH — Build or locate the payroll batch header used to group timecard data, keyed by payroll and time period (per SIR343 modification).
• CREATE_HOLIDAY_HOURS — Writes holiday hours to a timecard based on rotation plan and calendar data.
• RECORD_HOURS_WORKED — Persists individual hours-worked entries, optionally triggering holiday generation.

Tables Accessed

The package reads and writes a defined set of application tables through APPS synonyms:

• FND_USER, FND_SESSIONS — Identify the current user and session context, used chiefly by error logging.
• HXT_TIMECARDS_F, HXT_SUM_HOURS_WORKED_F — Core write targets for timecard and summarized hours data.
• HXT_EARNING_POLICIES, HXT_WORK_SHIFTS, HXT_WEEKLY_WORK_SCHEDULES — Supply earning and scheduling rules that govern how clock time is interpreted.
• HXT_HOLIDAY_CALENDARS, HXT_HOLIDAY_DAYS, HXT_ROTATION_PLANS, HXT_ROTATION_SCHEDULES — Drive holiday and rotation logic for CREATE_HOLIDAY_HOURS.
• HXT_SEQNO — Generates sequence numbers for new records.
• PAY_BATCH_HEADERS — Stores the payroll batch created by CREATE_BATCH.
• PER_TIME_PERIODS, PER_ASSIGNMENT_STATUS_TYPES — Resolve payroll periods and validate assignment status.

Usage Notes

HXT_TIME_CLOCK is typically invoked from the Time and Labor time-clock forms and from concurrent or background processes that process clock events, rather than from custom code, given its OTHER classification. The presence of a RECORD_TIME procedure with a status code and error buffer suggests callers should check the return code and inspect the error buffer on failure. LOG_CLOCK_ERRORS is the corresponding diagnostic routine, and custom integrators replicating clock behaviour should call it after catching a non-zero status so failures are recorded against the user session. Because the package is referenced by no other package, it should be treated as an internal implementation layer; direct invocation from custom concurrent programs is possible but unsupported, and upgrades in 12.1.1 versus 12.2.2 may alter internal helper signatures, as evidenced by the SIR343 batch-finding change.