Results for “xtr_limit_utilization_fee_v”

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

Overview

The view APPS.XTR_LIMIT_UTILIZATION_FEE_V is a reporting and integration object within the Oracle E-Business Suite Treasury (XTR) module. Its purpose is to expose the fee and interest-rate structure applied to limit utilization arrangements, allowing external reports, concurrent programs, and integration layers to retrieve fee definitions without querying the base transaction table directly. The view is owned by the APPS schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2.

From a design standpoint, the view is intentionally thin. It projects a defined subset of columns from a single base object and includes no joins, filters, or aggregations. This makes it a stable, low-overhead access point for consumers that require the fee/rate definition per company, counterparty, and limit, keyed by an effective date. Because the projection is explicit, applications referencing the view are insulated from column additions made to the underlying table.

Underlying Base Objects

The view is defined directly over the base table XTR_LIMIT_UTILIZATION_FEE, which is exposed within the APPS schema as a synonym. The documented view text is:

• SELECT COMPANY_CODE, CPARTY_CODE, LIMIT_CODE, MIN_AMT, MAX_AMT, INTEREST_RATE, EFFECTIVE_FROM_DATE FROM XTR_LIMIT_UTILIZATION_FEE

The relationship is therefore strictly one-to-one: every row returned by the view corresponds to exactly one row in XTR_LIMIT_UTILIZATION_FEE. No filtering predicate narrows the result set, and no other XTR table participates in the definition. All business logic governing when a given fee band is valid must be applied by the consuming query or report, typically through the effective-date and amount-band columns described below.

Key Columns

The view publishes seven columns, each of which supports the tiered fee definition for limit utilization:

• COMPANY_CODE — Identifies the legal entity or company for which the fee schedule is defined.
• CPARTY_CODE — Identifies the counterparty associated with the limit arrangement.
• LIMIT_CODE — The limit identifier to which the fee and interest-rate band applies.
• MIN_AMT — The lower bound of the utilization amount band covered by this fee definition.
• MAX_AMT — The upper bound of the utilization amount band covered by this fee definition.
• INTEREST_RATE — The rate applied to utilization falling within the MIN_AMT/MAX_AMT band. This is the column most frequently targeted when users search for interest_rate, since it holds the pricing value used in cost and exposure calculations.
• EFFECTIVE_FROM_DATE — The date from which the fee/rate definition becomes effective, enabling versioned or time-phased rate schedules.

Together these columns form a tiered rate table: for a given company, counterparty, and limit, multiple rows may exist, each covering a distinct amount band and effective period, with INTEREST_RATE providing the applicable rate for that band.

Common Use Cases and Queries

Typical uses include retrieving the current applicable rate for a limit, reconstructing rate history for audit or accrual purposes, and feeding downstream interest/fee calculations. A simple query to list all published rate bands is:

• SELECT company_code, cparty_code, limit_code, min_amt, max_amt, interest_rate, effective_from_date
• FROM apps.xtr_limit_utilization_fee_v
• WHERE limit_code = :p_limit_code
• ORDER BY effective_from_date DESC, min_amt;

To resolve the rate effective on a specific date, a predicate such as effective_from_date <= :as_of_date combined with a descending order and row limit returns the most recent applicable band. Because the view does not enforce uniqueness or effective-date precedence, consuming logic must apply this restriction. The view is best treated as a reporting projection of the underlying fee table rather than as a source of business rules, and any change to rate maintenance should be validated against XTR_LIMIT_UTILIZATION_FEE directly.