Search Results record_time

Overview

HXT_TIME_CLOCK is a PL/SQL package in the Oracle E-Business Suite Time and Labor (OTM) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its business purpose is to provide a programmatic interface for importing raw time entry data into the OTM system, primarily from external time-collection devices such as mechanical or electronic time clocks. The package creates a new OTM Timecard for a given employee and time period when one does not already exist, or appends time to an existing Timecard, provided that Timecard was not automatically generated by the application. As the embedded header comment states, the API is designed to log discrete blocks of time worked by an employee and is intended to be called repetitively—for example, once per PUNCH-OUT event, with both PUNCH-IN and PUNCH-OUT times supplied as parameters. Package-level global variables capture the session user context, the current business group from the PER_BUSINESS_GROUP_ID profile option, and error identifiers for batch, timecard, hours-worked, and time-period errors, alongside a user-defined g_error_log_error exception.

Key Procedures and Functions

The package exposes two documented procedures:

• RECORD_TIME — The core import routine. It accepts time entry data and creates or updates an OTM Timecard for the identified employee and time period. The documentation notes several prerequisites: the employee_number must resolve to a unique person in PER_PEOPLE_F considering date effectivity; the assignment_id parameter is currently NOT USED and may be passed as NULL, with the assignment instead derived as the first applicable row queried from PER_ASSIGNMENTS_F; and start_time is treated as the date worked for the block of time being logged. The routine is meant to be invoked repetitively for each distinct block of worked time.
• LOG_CLOCK_ERRORS — A companion error-handling routine that records failures encountered during clock data import into the HXT error structures, using the package globals g_batch_err_id, g_timecard_err_id, g_hours_worked_err_id, and g_time_period_err_id to categorize the error context.

Tables Accessed

The package reads and writes a range of OTM and Oracle HRMS objects via APPS synonyms. Timecard and time data are persisted in HXT_TIMECARDS_F and aggregated through HXT_SUM_HOURS_WORKED_F. Scheduling and policy validation draw on HXT_WORK_SHIFTS, HXT_WEEKLY_WORK_SCHEDULES, HXT_ROTATION_PLANS, HXT_ROTATION_SCHEDULES, HXT_HOLIDAY_CALENDARS, HXT_HOLIDAY_DAYS, and HXT_EARNING_POLICIES. Sequence values are obtained from HXT_SEQNO. Employee and assignment validation reference PER_TIME_PERIODS, PER_ASSIGNMENT_STATUS_TYPES, FND_USER, and FND_SESSIONS. Batch-level information is recorded in PAY_BATCH_HEADERS. These tables collectively support employee identification, schedule lookup, timecard creation, and error/batch tracking.

Usage Notes

HXT_TIME_CLOCK is typically invoked from external time-collection integrations, custom concurrent programs, or interface code that feeds punch data into Time and Labor, rather than from standard OTM forms. Because it relies on FND_PROFILE.Value for business group context and FND_GLOBAL for user identity, it must run within an initialized EBS session. The assignment_id limitation and the restriction against modifying automatically generated Timecards are important implementation constraints. The package is not referenced by any other documented package, indicating it is a top-level entry point for inbound clock data.