Search Results xtr_holiday_rules_v

Overview

XTR_HOLIDAY_RULES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the XTR (Treasury) product family. Its status is VALID in both the 12.1.1 and 12.2.2 releases. The view exposes the holiday rule definitions maintained within Oracle Treasury, presenting the calendar logic that drives value date, maturity date, and settlement date calculations for treasury instruments, foreign exchange deals, loans, and money market transactions.

Holiday rules in Treasury determine whether a calculated date falls on a non-business day and, if so, how that date should be adjusted. This view is the reporting and integration surface for that configuration, allowing users, concurrent programs, and external systems to query the rules without accessing the base table directly. Because the view is a thin projection over a single base object, it inherits all row-level values and applies no filtering or transformation of its own.

Underlying Base Objects

The view is defined over the base object XTR_HOLIDAY_RULES, which is referenced as a SYNONYM within the APPS schema. The view text selects twelve columns directly from this table with no joins, aggregations, or WHERE clause:

• SELECT HOL_SEQ, CURRENCY, HOLIDAY_DESC, HOLIDAY_TYPE, HOLIDAY_MONTH,
• CALCULATED_OUT_TO, HOLIDAY_DAY, HOLIDAY_YEAR, HOLIDAY_RULE, DAY_RULE,
• WEEKEND_ADJ, EXTRA_HOLIDAY_DAYS FROM XTR_HOLIDAY_RULES

Consequently, the view carries one row per holiday rule record, keyed indirectly by the combination of currency and holiday sequence. Any maintenance performed through the Treasury holiday calendar setup forms updates XTR_HOLIDAY_RULES, and the view reflects those changes immediately upon commit.

Key Columns

The exposed columns describe the identity, timing, and adjustment behaviour of each holiday entry:

• HOL_SEQ — the sequence identifier that uniquely orders holiday records within the rules set.
• CURRENCY — the currency or country calendar to which the holiday rule applies.
• HOLIDAY_DESC — the descriptive name of the holiday (for example, a national or bank holiday).
• HOLIDAY_TYPE — classifies the holiday as fixed-date, floating, or rule-driven.
• HOLIDAY_MONTH / HOLIDAY_DAY / HOLIDAY_YEAR — the calendar attributes used to resolve the holiday date, including recurrence year where applicable.
• CALCULATED_OUT_TO — the horizon out to which the holiday occurrence has been generated or calculated.
• HOLIDAY_RULE — the rule governing how the holiday date is derived for the given calendar.
• DAY_RULE — the business-day convention applied when a calculated date lands on the holiday.
• WEEKEND_ADJ — the weekend adjustment convention (for example, following, preceding, or modified following).
• EXTRA_HOLIDAY_DAYS — additional non-business days to include alongside the defined holiday.

Common Use Cases and Queries

The view is typically used to validate holiday configuration, support date-roll logic in reporting, and feed downstream integrations that must replicate Treasury business-day conventions. A common check is to list all holiday rules for a given currency:

• SELECT HOL_SEQ, HOLIDAY_DESC, HOLIDAY_TYPE, HOLIDAY_MONTH, HOLIDAY_DAY, WEEKEND_ADJ FROM XTR_HOLIDAY_RULES_V WHERE CURRENCY = 'USD' ORDER BY HOL_SEQ;

Analysts also review adjustment conventions across calendars to confirm consistency:

• SELECT CURRENCY, HOLIDAY_DESC, DAY_RULE, WEEKEND_ADJ, EXTRA_HOLIDAY_DAYS FROM XTR_HOLIDAY_RULES_V ORDER BY CURRENCY, HOL_SEQ;

Because the view is unfiltered, all query predicates must be supplied by the caller. Performance is therefore equivalent to querying XTR_HOLIDAY_RULES directly, and appropriate indexing on CURRENCY and HOL_SEQ is assumed at the base table level. No DML is permitted against the view; changes must be applied to the underlying table through the standard Treasury setup interface.