Search Results xtr_holiday_rules




Overview

The XTR_HOLIDAY_RULES table is a core data object within the Oracle E-Business Suite (EBS) Treasury (XTR) module. It serves as the master repository for defining non-working day rules associated with specific currencies. Its primary role is to provide the system with the necessary logic to accurately calculate settlement dates, value dates, and maturity dates for financial instruments and transactions, such as foreign exchange deals, money market trades, and derivatives. By centralizing holiday rules per currency, it ensures that date calculations automatically roll forward to the next valid business day, adhering to market conventions and preventing the scheduling of payments or settlements on bank holidays or weekends. This functionality is critical for cash flow forecasting, risk management, and operational compliance within the treasury function.

Key Information Stored

The table stores rule-based definitions for holidays rather than a simple list of calendar dates. Key columns include CURRENCY, which links to the XTR_MASTER_CURRENCIES table, and HOLIDAY_RULE, which defines the rule type (e.g., fixed date, relative day like "second Monday"). Supporting columns specify the rule's parameters: HOLIDAY_DAY, HOLIDAY_MONTH, and HOLIDAY_YEAR for fixed dates; DAY_RULE for day-of-week logic; and EXTRA_HOLIDAY_DAYS for offsets. The HOLIDAY_TYPE may classify the holiday (e.g., public, bank). Crucially, the WEEKEND_ADJ column dictates how the system handles dates that fall on a standard weekend (Saturday/Sunday), typically instructing a roll-forward or roll-backward to the nearest business day.

Common Use Cases and Queries

The primary use case is the automated adjustment of financial dates within Treasury workflows. For instance, when a deal is entered with a trade date, the system will reference this table to compute the correct settlement date. Common reporting and validation queries include listing all defined rules for a currency or identifying rules for a specific holiday type. A typical SQL pattern to audit rules would be:

  • SELECT currency, holiday_rule, holiday_day, holiday_month, weekend_adj FROM xtr_holiday_rules WHERE currency = 'USD' ORDER BY holiday_month, holiday_day;

Another critical use is in batch processes that generate cash flow projections, where the table is queried en masse to adjust all projected payment dates across a portfolio for multiple currencies.

Related Objects

The most direct relationship, as defined by its foreign key, is with the XTR_MASTER_CURRENCIES table, ensuring referential integrity for the CURRENCY field. This table is fundamentally referenced by the core date calculation engines and APIs within the XTR module, particularly in packages responsible for financial date arithmetic. While not explicitly listed in the provided metadata, it is intrinsically linked to transaction tables like XTR_DEALS and XTR_CASHFLOWS, whose date fields are derived using these holiday rules. Views or interfaces that expose holiday calendars for reporting or integration will also likely source their data from this table.