Results for “xtr_a_futures_v”

4 results




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

Overview

XTR_A_FUTURES_V is a reporting view within the Oracle E-Business Suite Treasury (XTR) module. It exposes the full set of attribute columns required to describe, price, and administer futures and exchange-traded derivative contracts maintained in the Treasury contract repository. The view captures the descriptive identity of each instrument (contract code and description), its classification, pricing conventions, settlement behaviour, coupon characteristics, termination rules, and month-level deliverability flags.

In Oracle EBS 12.1.1 and 12.2.2, XTR_A_FUTURES_V functions as a read-only presentation layer over the futures contract definition data. It is intended for inquiry, reporting, and downstream extraction rather than for transactional maintenance. Because it carries audit columns (CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON, AUDIT_INDICATOR, AUDIT_DATE_STORED) alongside the business attributes, the view is equally suited to reconciliation and audit reporting as it is to operational inquiry.

The metadata records that the view is not implemented in the reference database, and that no owner or referenced base objects were documented in the ETRM 12.2.2 extract. Consumers should therefore validate object availability in their own instance before building dependent reports.

Underlying Base Objects

The view definition is a straight projection with no joins, aggregation, or filtering predicates:

Every column listed in the view text maps one-to-one to a column of the base table XTR_A_FUTURES. No additional tables, synonyms, or lookup objects are referenced. The absence of a WHERE clause means the view does not, by itself, restrict rows to authorised contracts, active contracts, or any date range; filtering must be supplied by the calling query. The AUTHORISED column is exposed as data, not applied as a predicate.

Since the view is a non-transforming projection, it is inherently updatable in Oracle terms, but the EBS convention remains that contract maintenance is performed through the Treasury application forms and APIs rather than through the view.

Key Columns

Common Use Cases and Queries

Typical scenarios include contract master listings, pricing-convention audits, authorisation status reviews, and extracts feeding risk or valuation engines.

Listing contracts with description and pricing detail:

  • SELECT CONTRACT_CODE, CONTRACT_DESCRIPTION, PRICING_BASIS, TICK_VALUE, CURRENCY FROM XTR_A_FUTURES_V WHERE AUTHORISED = 'Y';

Searching by description fragment, which mirrors the common "contract_description" lookup:

  • SELECT CONTRACT_CODE, CONTRACT_DESCRIPTION FROM XTR_A_FUTURES_V WHERE UPPER(CONTRACT_DESCRIPTION) LIKE '%TREASURY BOND%';

Auditing recently modified definitions:

  • SELECT CONTRACT_CODE, UPDATED_BY, UPDATED_ON FROM XTR_A_FUTURES_V WHERE UPDATED_ON >= TRUNC(SYSDATE) - 30;

Reviewing coupon and termination conventions:

  • SELECT CONTRACT_CODE, YEAR_BASIS, COUPONS_PER_YEAR, COUPON_RATE, TERMINATION_DATE FROM XTR_A_FUTURES_V;

Because no row-level filtering is built into the view, all business restrictions should be applied explicitly in the consuming query.