Search Results create_timecard

Overview

HXT_TIME_GEN is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Time and Labor (OTL) application. Its core business function is the automated generation of timecards and time-related records. In the OTL architecture, time must frequently be created without direct user entry — for example, when an employee holds a schedule-based or rotation-based assignment, has a recurring weekly work pattern, or when a batch process needs to pre-create timecard rows for a population of workers. HXT_TIME_GEN supplies exactly this capability: it drives the logic that transforms shift schedules, rotation plans, and holiday calendars into concrete, datable timecards and detail-hour records.

Because time generation is deterministic and schedule-driven, the package serves as the engine behind OTL's automatic timecard creation, whether invoked interactively through the Timekeeper or Time Collection flows or executed in bulk by the HXT_BATCH_PROCESS concurrent program.

Key Procedures and Functions

The ETRM metadata documents nine callable units. Their names indicate the following responsibilities:

• GENERATE_TIME — The primary driver that generates timecard rows for a defined criteria set (person, assignment, or organization) over a date range, orchestrating the remaining routines.
• GEN_WORK_PLAN — Generates time according to a worker's assigned work plan, applying the weekly or shift work schedule.
• GEN_ROT_PLAN — Generates time for rotation-based schedules, using the rotation schedule definition to determine which shift falls on each day.
• CREATE_BATCH — Establishes a batch record so that a generation run can be grouped, tracked, and processed as a unit.
• CREATE_TIMECARD — Builds an individual timecard header and associated detail rows for a worker and period.
• CREATE_HRW — Creates hours-worked records, posting generated time into the hours-worked detail store used by payroll and costing.
• GET_HXT_SEQNO — Returns the next sequence value used to uniquely number generated records.
• GET_NEXT_BATCH_ID — Supplies the identifier for a new batch, ensuring uniqueness across batch runs.
• GET_WORK_DAY — Determines whether a given date is a working day, consulting the individual's schedule and holiday definitions.

Tables Accessed

The package reads and writes core OTL and HR configuration and transaction tables via APPS synonyms. HXT_WORK_SHIFTS, HXT_SHIFTS, and HXT_WEEKLY_WORK_SCHEDULES provide the schedule definitions used to decide when a worker is expected to work. HXT_ROTATION_SCHEDULES supplies rotation logic for GEN_ROT_PLAN. HXT_HOLIDAY_CALENDARS and HXT_HOLIDAY_DAYS provide non-working dates so that GET_WORK_DAY and the generators skip holidays. PER_TIME_PERIODS defines the time periods for which records are created, while HR_ORGANIZATION_UNITS and FND_USER identify the people and organizations in scope. The package writes results to HXT_TIMECARDS_F and HXT_DET_HOURS_WORKED_F (the interface tables for timecards and detailed hours), with summarized data in HXT_SUM_HOURS_WORKED_F, and applies earning and premium rules from HXT_EARNING_POLICIES. HXT_BATCH_STATES tracks batch progress, and HXT_SEQNO supplies sequence numbers. FND_PROFILE and FND_GLOBAL supply session and profile-option context, and HXT_ERRORS is used for error logging.

Usage Notes

HXT_TIME_GEN is not intended for direct end-user invocation. It is typically called from OTL forms and concurrent programs — notably HXT_BATCH_PROCESS, HXT_TIME_CLOCK, and HXT_TIME_COLLECTION all reference it — as well as from custom extensions that require programmatic timecard generation. The presence of batch-oriented routines indicates that bulk generation runs are executed through the batch process framework, where CREATE_BATCH and GET_NEXT_BATCH_ID manage run identity and GET_HXT_SEQNO ensures record uniqueness. Custom code should invoke the package only within a properly initialized OTL session (FND_GLOBAL, FND_PROFILE) and should honor the holiday and schedule configuration, since correctness depends entirely on those setup tables. Error conditions are surfaced through HXT_ERRORS, and callers should check for failures before committing generated timecards.