Results for “xtr_a_rate_sets_v”

16 results




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

Overview

XTR_A_RATE_SETS_V is an APPS-owned database view within the Oracle E-Business Suite Treasury (XTR) module. It is catalogued as VALID in both the 12.1.1 and 12.2.2 releases and serves as a reporting and integration layer over the Treasury interest rate setup data stored in the XTR_A_RATE_SETS base object. In the ETRM (Enterprise Treasury Reference Model) documentation, the view is classified as a read-only presentation object: it exposes the full column set of the underlying rate-set definition so that concurrent programs, reports, and external interfaces can query rate configuration without direct dependency on the base table's physical layout.

The view is defined with a simple projection — SELECT of the named columns FROM XTR_A_RATE_SETS — without joins, aggregations, or filters. This makes it a thin, deterministic wrapper whose primary value is schema abstraction, security consistency, and standardized naming for downstream consumers such as interest rate calculation, deal processing, and audit reporting.

Underlying Base Objects

The documented base object is XTR_A_RATE_SETS, referenced through a SYNONYM. The view returns every column of that table unchanged, meaning row-level and column-level semantics are identical to the parent rate-set definition. Because the view is a direct projection, it inherits any grants held on XTR_A_RATE_SETS and is subject to the same Oracle EBS multi-org and security model applied elsewhere in the Treasury schema. No other base tables or views are documented as participating in its definition.

Key Columns

Common Use Cases and Queries

Typical usage includes reviewing active rate configurations for a currency or deal type, auditing changes to rates and margins, and supplying input to interest accrual or deal revaluation processes. Because RATE_SETS are effective-dated, queries commonly filter by EFFECTIVE_FROM to reconstruct the rate in force on a given date.

Example: list rate sets for a client grouping by currency.

  • SELECT unique_ref_num, currency, deal_type, rate, margin, effective_from
    FROM apps.xtr_a_rate_sets_v
    WHERE client_grouping = :p_client_grouping
    AND currency = :p_currency
    ORDER BY effective_from DESC;

Example: identify floating-rate configurations currently posted.

  • SELECT unique_ref_num, deal_type, reset_basis, no_of_days, term
    FROM apps.xtr_a_rate_sets_v
    WHERE fixed_floating = 'FLOATING'
    AND posted = 'Y';

Example: trace records created by a specific concurrent request for audit purposes.

  • SELECT unique_ref_num, created_by, created_on, concurrent_request
    FROM apps.xtr_a_rate_sets_v
    WHERE concurrent_request = :p_request_id;

In integration scenarios the view is frequently accessed read-only by external rate engines or reconciliation scripts, since it presents the canonical, documented Treasury rate-set structure without requiring knowledge of underlying table constraints.