Search Results period_code




Overview
Explore in AI Chat

Overview

The view APPS.XTR_R_INTEREST_PERIOD_RATES_V is a Treasury (XTR) reporting and integration object shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. It presents interest rate data organized by currency and by an internally keyed interest period, exposing benchmark (bid), spread, and offer rate values together with the date on which those rates were captured. The view is registered in the ETRM metadata repository with a status of VALID and is owned by the APPS schema, which is the standard convention for shared, read-oriented dictionary objects in EBS.

Because it projects a defined subset of columns from a single base object, the view functions as a stable read interface. Technical consultants, report developers, and integration specialists use it to retrieve period-based interest rate data without depending on the full column list or internal indexing conventions of the underlying table. The PERIOD_CODE column is the primary business-facing identifier exposed by the view and is the attribute most frequently referenced when mapping Treasury rate data to external systems or custom reports.

Underlying Base Objects

The view is defined over a single referenced object, XTR_R_INTEREST_PERIOD_RATES, which is documented as a synonym. The view text is a straightforward projection:

No joins, filters, or aggregation are applied. Every column exposed by the view corresponds one-to-one with a column in the base table. This means row cardinality, uniqueness behavior, and any data restrictions are inherited directly from XTR_R_INTEREST_PERIOD_RATES. The synonym indirection means the physical table resides under a schema that APPS references through the synonym convention, and any DML performed through the view would affect the base rows, though the object is intended for query access.

Key Columns

  • PERIOD_CODE — The business identifier for the interest period; the principal search and grouping attribute for this view.
  • UNIQUE_PERIOD_ID — The internal surrogate key that uniquely identifies the period record.
  • CURRENCY — The currency to which the rate applies.
  • RATE_DATE — The effective date of the rate observation.
  • BID_RATE — The bid-side interest rate for the period.
  • SPREAD — The spread component applied to the benchmark rate.
  • OFFER_RATE — The offer-side interest rate for the period.
  • TERM_TYPE — Classifies the term structure associated with the rate.
  • CONTRA_OPTION_CCY — The contra (counterparty) option currency for the rate line.
  • DOWNLOAD_DATE_TIME — Timestamp indicating when the rate record was downloaded or loaded from its source.
  • ARCHIVE_DATE and ARCHIVE_BY — Audit columns recording when and by whom the record was archived.

Common Use Cases and Queries

The view supports period-based rate reporting, treasury integrations, and reconciliation checks. Typical uses include verifying loaded rates by currency and date, extracting bid/offer pairs for curve construction, and validating that PERIOD_CODE values and spread components match downstream systems. A standard query filtering by period and currency is shown below.

  • Retrieve rates for a specific period_code and currency: 
    SELECT period_code, currency, rate_date, bid_rate, spread, offer_rate
FROM   xtr_r_interest_period_rates_v
WHERE  period_code = :p_period_code
AND    currency    = :p_currency
ORDER BY rate_date DESC;
  • List distinct period codes available for a currency, which is the common discovery step after searching for "period_code": 
    SELECT DISTINCT period_code, term_type
FROM   xtr_r_interest_period_rates_v
WHERE  currency = :p_currency
ORDER BY period_code;
  • Audit recently downloaded or archived records: 
    SELECT period_code, currency, download_date_time, archive_date, archive_by
FROM   xtr_r_interest_period_rates_v
WHERE  download_date_time >= SYSDATE - 7;

Because the view performs no filtering, callers should apply predicates on PERIOD_CODE, CURRENCY, or RATE_DATE to limit result sets, and should account for archived rows unless ARCHIVE_DATE IS NULL is used to restrict output to active records.