Results for “drawn_order”

2 results




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

Overview

XTR_MOST_EFFICIENT_LIMIT_USE_V is a Treasury (XTR) reporting view that ranks counterparty credit limits according to the cost of drawing against them. It exposes the outstanding limit position of each counterparty together with the fee percentages and utilisation basis flags needed to determine which limit line should be consumed first. The view filters out settlement-type limits (LIMIT_CODE = 'SETTLE') and returns only those limit records where available headroom remains, that is, where LIMIT_AMOUNT less UTILISED_AMOUNT is greater than zero.

Within Oracle EBS 12.1.1 and 12.2.2, this object is a database view rather than a concurrent program or form. As documented in ETRM, it is catalogued in the Treasury module but is not implemented in every database; availability depends on which Treasury licensing and patch levels have been applied. Its principal role is analytical: it supplies a query-ready result set for determining which credit line carries the lowest aggregate fee, thereby supporting "most efficient" limit selection logic in treasury dealing and exposure analysis.

Underlying Base Objects

The view is defined exclusively over XTR_COUNTERPARTY_LIMITS. No additional base tables, synonyms or functions are documented as referenced objects. This single-table dependency means the view inherits the security, partitioning and indexing characteristics of XTR_COUNTERPARTY_LIMITS and cannot return a limit that does not exist as a counterparty limit record.

The filter predicate restricts the result set in two ways. First, LIMIT_CODE != 'SETTLE' removes the settlement limit maintained for operational cash management purposes, ensuring only trading and credit facilities are considered. Second, NVL(LIMIT_AMOUNT, 0) - NVL(UTILISED_AMOUNT, 0) > 0 excludes fully consumed limits and rows where LIMIT_AMOUNT is null. The NVL wrappers are significant because they prevent null limit or utilisation values from suppressing otherwise valid rows or from producing unpredictable ordering.

Key Columns

  • COMPANY_CODE — the legal entity or company owning the limit line.
  • CPARTY_CODE — the counterparty to which the limit is granted.
  • LIMIT_CODE — the identifier of the specific limit facility; never 'SETTLE' in this view.
  • LIMIT_AMOUNT — the authorised limit ceiling, the primary value users search for when querying by limit_amount.
  • UTILISED_AMOUNT — the amount already consumed against the limit.
  • COMMITMENT_FEE_PERCENT and UTILISATION_FEE_PERCENT — the fee rates applied to undrawn and drawn balances respectively.
  • BENCHMARK_REF — the reference rate or index associated with the facility.
  • UTILISATION_CALC_BASIS — determines whether the facility is fee-optimal when drawn ('U') or when undrawn.
  • UTILIZATION_STRUCTURE_BASIS — the structural basis governing how utilisation is aggregated.
  • UNDRAWN_ORDER and DRAWN_ORDER — derived fee-total columns that drive the efficiency ranking; a value is populated in one and zeroed in the other depending on the calculation basis.

Common Use Cases and Queries

The most frequent query pattern selects limits for a counterparty and orders them by the derived fee orders to identify the cheapest facility to draw upon:

  • Listing remaining headroom: SELECT company_code, cparty_code, limit_code, limit_amount - utilised_amount FROM xtr_most_efficient_limit_use_v WHERE cparty_code = :cp
  • Locating facilities by size: SELECT * FROM xtr_most_efficient_limit_use_v WHERE limit_amount >= :amount ORDER BY limit_amount
  • Efficiency ranking: SELECT limit_code, drawn_order, undrawn_order FROM xtr_most_efficient_limit_use_v WHERE cparty_code = :cp ORDER BY drawn_order, undrawn_order

Because the view already excludes exhausted limits and settlement lines, downstream reports and integrations can use it directly without repeating the exclusion logic. Users searching on "limit_amount" should note that the column reflects the authorised ceiling, not the available balance; the residual capacity is obtained by subtracting UTILISED_AMOUNT.