Search Results xtr_holiday_rules




Overview
Explore in AI Chat

Overview

XTR_HOLIDAY_RULES is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the holiday calendar definitions applied to individual currencies. Foreign exchange, money market, and cash management processing depend on accurate holiday calendars to determine value dates, maturity dates, settlement dates, and interest accrual periods. Each row defines a rule that determines whether a given date is treated as a holiday for a specific currency, along with the adjustment behavior to apply when a calculated date falls on a weekend or holiday.

The table is owned by the XTR schema and is documented as VALID in the ETRM 12.2.2 data model. Its documented description is "Holiday rules defined for different currencies." Under the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning: it carries descriptive, rule-oriented attributes that depend on a parent business key (CURRENCY) rather than acting as an independent hub or as a link between two hubs. It should therefore be modeled as a satellite attached to the currency hub represented by XTR_MASTER_CURRENCIES.

Key Information Stored

The table exposes 12 documented columns. The most significant are:

  • CURRENCY — The currency code the rule applies to. This column is the foreign key to XTR_MASTER_CURRENCIES.CURRENCY and is the parent business key of the satellite.
  • HOLIDAY_TYPE — Classifies the nature of the holiday rule (for example, fixed-date, floating, or rule-based holidays).
  • DAY_RULE — The day-of-week or ordinal rule used to derive a floating holiday.
  • EXTRA_HOLIDAY_DAYS — Additional offset days applied to the calculated holiday date.
  • HOLIDAY_DAY — The calendar day component of a fixed holiday.
  • HOLIDAY_MONTH — The calendar month component of a fixed holiday.
  • HOLIDAY_YEAR — The year component, when a holiday is defined for a specific year.
  • HOLIDAY_RULE — The governing rule expression that determines how the holiday date is computed.
  • WEEKEND_ADJ — The weekend adjustment indicator defining how dates falling on a weekend are shifted.
  • HOLIDAY_DESC — Descriptive text for the holiday rule.
  • HOL_SEQ — Sequence used to order holiday rules within a currency.
  • CALCULATED_OUT_TO — The date through which holiday dates have been calculated and stored.

The documented unique key is XTR_HOLIDAY_RULES_UK, defined over the combination of CURRENCY, HOLIDAY_TYPE, DAY_RULE, EXTRA_HOLIDAY_DAYS, HOLIDAY_DAY, HOLIDAY_MONTH, HOLIDAY_RULE, HOLIDAY_YEAR, and WEEKEND_ADJ. This composite uniqueness constraint is the business-key candidate; no separate surrogate primary key column is documented in the metadata, so the composite unique key effectively serves as the row identifier.

Common Use Cases and Queries

Typical usage centers on date validation and date roll logic. Applications query this table to determine whether a proposed settlement or value date is a holiday for a given currency, and to obtain the adjusted date when it is. Reporting scenarios include listing all holidays for a currency within a period, auditing weekend adjustment behavior, and reconciling calculated-out-to coverage.

A representative query retrieves rules for a currency:

  • SELECT CURRENCY, HOLIDAY_TYPE, HOLIDAY_DAY, HOLIDAY_MONTH, HOLIDAY_YEAR, WEEKEND_ADJ, HOLIDAY_DESC FROM XTR_HOLIDAY_RULES WHERE CURRENCY = :currency ORDER BY HOL_SEQ;
  • Join to the parent currency definition to obtain descriptive currency attributes: SELECT h.*, c.* FROM XTR_HOLIDAY_RULES h, XTR_MASTER_CURRENCIES c WHERE h.CURRENCY = c.CURRENCY;
  • Filter on the calculation horizon to detect stale calendars: SELECT CURRENCY, MAX(CALCULATED_OUT_TO) FROM XTR_HOLIDAY_RULES GROUP BY CURRENCY;

These patterns support operational checks before trade capture, batch recalculation of holiday calendars, and data quality audits of weekend adjustment configuration.

Related Objects

The following objects are the most significant dependencies based on the documented key relationships:

  • XTR_MASTER_CURRENCIES — Parent table referenced by XTR_HOLIDAY_RULES.CURRENCY; holds the currency definition that each holiday rule belongs to.
  • XTR_HOLIDAY_RULES_UK — The composite unique index enforcing the business key across the nine documented rule columns.
  • Treasury deal and settlement tables — Trade, FX, and money market records that consume holiday calendars indirectly through date roll logic.
  • Cash management and payment objects — Objects that depend on currency holiday calendars to derive value dates and settlement dates.
  • Concurrent programs and calendar maintenance routines — Processes that populate CALCULATED_OUT_TO and maintain holiday rows over time.

Because the table is satellite-leaning, downstream joins should always anchor on CURRENCY and preserve the composite business key defined by XTR_HOLIDAY_RULES_UK.