Results for “xtr_holidays”

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

Overview

XTR_HOLIDAYS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the holiday calendars used by treasury functions for different currencies. Its documented description is concise: "Holidays defined for different currencies." In practice, this table provides the date-level reference data that Treasury relies on to determine whether a given business day is a valid value date, settlement date, or processing date for instruments denominated in a specific currency. Because financial instruments such as foreign exchange contracts, money market deals, and loans cannot settle on a currency's non-business day, XTR_HOLIDAYS supplies the authoritative definition of non-working dates per currency.

From a Data Vault modeling perspective, the mined FK structure classifies XTR_HOLIDAYS as standalone. The heuristic recommendation is therefore to treat it as an independent reference or lookup object rather than as a hub, link, or satellite in a Data Vault model, since no foreign key relationships were detected in the documented schema. It functions as a self-contained reference table keyed by currency and date, and it is referenced logically (rather than through declared foreign keys) by treasury processing logic that needs to validate settlement dates.

Key Information Stored

The documented physical schema for XTR_HOLIDAYS in ETRM 12.2.2 shows an owner of XTR and five columns. The most important of these are:

• CURRENCY — The currency code for which the holiday is defined. This is the primary partitioning/grouping attribute and the first component of the primary key.
• HOLIDAY_DATE — The specific date on which the given currency is treated as a non-business day. This is the second component of the primary key and drives all date-validation logic.
• DAY_DESC — Descriptive text identifying the holiday, such as a public holiday name or a bank holiday label, useful for reporting and calendar display.
• COMMENTS — Free-form remarks providing additional context about the holiday entry, such as regional applicability or source.
• HOL_SEQ — A sequence or ordering column associated with the holiday entry, likely used for internal ordering or grouping of holiday records.

The primary key is documented as XTR_HOLIDAYS_PK (CURRENCY, HOLIDAY_DATE). The unique index XTR_HOLIDAYS_U1 (HOLIDAY_DATE, CURRENCY) is a documented business-key candidate; note that it reverses the column order of the primary key, so both the PK and the unique index enforce that no two rows exist for the same currency and date, while providing alternate access paths depending on whether queries filter first by currency or by date.

Common Use Cases and Queries

The primary use case is determining whether a proposed settlement or value date is a valid business day for a specific currency. Treasury deal entry, FX rate fixing, and payment scheduling routines consult this table to roll or adjust dates whenever a nominated date falls on a currency holiday. Reporting scenarios include producing holiday calendars per currency, auditing calendar maintenance, and identifying upcoming holidays that may affect cash positioning.

Typical query patterns include filtering by currency and a date range to retrieve all holidays within a period:

• SELECT currency, holiday_date, day_desc FROM xtr_holidays WHERE currency = :p_currency AND holiday_date BETWEEN :p_start AND :p_end ORDER BY holiday_date;
• To validate a single date as a business day: SELECT COUNT(*) FROM xtr_holidays WHERE currency = :p_currency AND holiday_date = :p_date; — a zero count indicates the date is not a holiday.
• To confirm uniqueness and support the U1 index access path: SELECT * FROM xtr_holidays WHERE holiday_date = :p_date ORDER BY currency;

Because the metadata describes XTR_HOLIDAYS as standalone, no join keys are documented; application logic performs lookups by currency and date rather than by foreign key.

Related Objects

The documented FK/PK relationship data classifies XTR_HOLIDAYS as standalone, meaning no declared foreign keys are mined. Its relationships to other objects are therefore logical rather than enforced. The most significant related objects in the Treasury and wider EBS context are:

• XTR_HOLIDAYS_PK — the primary key constraint (CURRENCY, HOLIDAY_DATE) that governs row uniqueness.
• XTR_HOLIDAYS_U1 — the unique index (HOLIDAY_DATE, CURRENCY) providing the alternate business-key access path.
• FND_CURRENCIES — the standard EBS currency definitions table, joined on CURRENCY = FND_CURRENCIES.CURRENCY_CODE, providing currency names and attributes for holiday reporting.
• XTR currency and deal tables — treasury instrument tables (such as FX and money market deal tables in the XTR schema) that logically reference holiday calendars via their currency codes when deriving value and settlement dates.
• GL_DAILY_CONVERSION_TYPES / GL daily rates interfaces — treasury rate and conversion processes that depend on valid business days for a currency.

Because the FK classification is standalone, consumers should rely on application-level validation and the documented unique index rather than expecting database-enforced referential integrity to other Treasury objects.