Results for “hxt_holiday_days”

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

Overview

HXT_HOLIDAY_DAYS is a Time and Labor (HXT) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the details of user-defined holiday days. Each row represents a single holiday date associated with a named holiday calendar, together with the number of hours credited for that day. The table is owned by the HXT schema and is classified as VALID in the ETRM dictionary. Its role is foundational: Time and Labor uses this data to determine whether a given day is a recognized holiday when evaluating timecards, applying calendar rules, and calculating overtime or premium pay.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is satellite-leaning. This suggests HXT_HOLIDAY_DAYS is best understood as descriptive context attached to a parent business entity — specifically the holiday calendar — rather than as an independent hub or an associative link. The temporal attributes (HOLIDAY_DATE, HOURS) further reinforce its satellite character, since they record descriptive detail about each calendar's holiday schedule.

Key Information Stored

The table contains ten documented columns. The most significant are described below.

• ID — The surrogate primary key, enforced by HXT_HOLIDAY_DAYS_PK. This is a system-generated identifier with no business meaning.
• HCL_ID — The foreign key to HXT_HOLIDAY_CALENDARS, identifying which holiday calendar owns this holiday day. This column is part of the unique business key.
• NAME — The user-defined holiday name (for example, "New Year's Day"). This is also part of the unique business key.
• HOLIDAY_DATE — The actual calendar date of the holiday, forming the third column of the unique business key.
• HOURS — The number of hours credited or recognized for the holiday, used in time calculation logic.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard Oracle EBS who-did-what-when tracking.

The unique index HXT_HOLIDAY_DAYS_UK on (NAME, HCL_ID, HOLIDAY_DATE) establishes the business key, ensuring that a given holiday name cannot be duplicated for the same date within the same calendar. Distinguishing the surrogate ID from this business key is essential when writing joins or de-duplication logic.

Common Use Cases and Queries

Typical scenarios include validating holiday setups, reporting scheduled holidays by calendar, and reconciling credited hours. A straightforward query lists all holidays for a specific calendar:

• SELECT hd.NAME, hd.HOLIDAY_DATE, hd.HOURS FROM HXT.HXT_HOLIDAY_DAYS hd WHERE hd.HCL_ID = :p_calendar_id ORDER BY hd.HOLIDAY_DATE;
• Reporting holidays within a date range across all calendars: SELECT HCL_ID, NAME, HOLIDAY_DATE FROM HXT.HXT_HOLIDAY_DAYS WHERE HOLIDAY_DATE BETWEEN :start_date AND :end_date;
• Joining to the calendar parent for a consolidated view: SELECT hc.*, hd.NAME, hd.HOLIDAY_DATE FROM HXT.HXT_HOLIDAY_CALENDARS hc, HXT.HXT_HOLIDAY_DAYS hd WHERE hc.ID = hd.HCL_ID;

These patterns support period-end verification, audit of credited holiday hours, and feeding downstream OTL calculations.

Related Objects

The most significant dependent relationships are anchored by the documented foreign key.

• HXT_HOLIDAY_CALENDARS — The parent table, joined via HCL_ID = HXT_HOLIDAY_CALENDARS.ID. This is the primary relationship.
• HXT_HOLIDAY_DAYS_PK / HXT_HOLIDAY_DAYS_UK — The primary key and unique indexes enforcing identity and business-key uniqueness.
• Time and Labor timecard and calendar processing objects — Time calculation routines reference holiday calendars, and therefore transitively this table, when applying holiday rules.
• Payroll and OTL integration views — Retrieval views in the integrated Time and Labor / Payroll flow may query holiday hours through calendar joins.

Because documentation for HXT_HOLIDAY_DAYS is relatively narrow, developers should treat HXT_HOLIDAY_CALENDARS as the definitive parent and validate any additional dependencies against the live 12.1.1 or 12.2.2 instance.