Search Results xtr_a_exposure_transactions_v

Overview

XTR_A_EXPOSURE_TRANSACTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR (Treasury) product family. It presents exposure transaction data used by Treasury for tracking foreign exchange and financial exposure items across the enterprise. The view is defined as a straightforward projection over the XTR_A_EXPOSURE_TRANSACTIONS synonym, exposing a fixed column list rather than applying joins, filters, or aggregation logic. Its status is VALID in the reference environment, confirming it compiles cleanly against the underlying object.

Because exposure transactions feed downstream treasury settlement, hedging, and risk monitoring processes, this view functions primarily as a read-oriented interface for reports, concurrent programs, and integrations that must retrieve exposure data without depending directly on the base table name. Its inclusion of PURCHASING_MODULE is directly relevant to users searching on that term, as it identifies the originating purchasing context of an exposure record.

Underlying Base Objects

The documented referenced base object is the synonym XTR_A_EXPOSURE_TRANSACTIONS. The view text is a simple SELECT over that synonym, returning all listed columns without WHERE predicates or joins. The "A" prefix indicates the object belongs to the Treasury application's core table family, while the "_V" suffix designates it as a view rather than a table. In practice, the synonym typically resolves to the physical Treasury exposure transactions table under the XTR schema, so the view inherits the storage, indexing, and partitioning characteristics of that base object. No additional base tables are documented for this view, meaning row counts and column values map one-to-one with the underlying exposure records.

Key Columns

• TRANSACTION_NUMBER — primary business identifier for the exposure transaction.
• COMPANY_CODE and PORTFOLIO_CODE — organizational and portfolio attribution.
• DEAL_TYPE and DEAL_SUBTYPE — classification of the underlying treasury deal.
• EXPOSURE_TYPE — the category of exposure being tracked.
• CURRENCY, AMOUNT, and AMOUNT_HCE — transaction currency, transaction amount, and home-currency equivalent.
• VALUE_DATE and ESTIMATE_DATE — accounting value date and estimated settlement date.
• PURCHASING_MODULE — indicates the purchasing module associated with the exposure, directly supporting queries filtered on this attribute.
• SETTLE_ACTION_REQD, SELECT_ACTION, and ACTION_CODE — settlement and action workflow indicators.
• PAYMENT_AMOUNT, PAYMENT_STATUS, and BALANCE — payment and outstanding balance information.
• CPARTY_CODE, CPARTY_REF, THIRDPARTY_CODE, and BENEFICIARY_CODE — counterparty and beneficiary identifiers.
• AVG_RATE, NZD_AMOUNT, CONTRA_NZD_AMOUNT, and PROFIT_LOSS — rate, currency-specific, and valuation amounts.
• COVERED_BY_FX_CONTRACT — flags whether the exposure is hedged by an FX contract.
• DEAL_STATUS, STATUS_CODE, ARCHIVE_DATE, and ARCHIVE_BY — lifecycle and archival state.
• AUDIT_INDICATOR and AUDIT_DATE_STORED — audit tracking.
• CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include Treasury exposure reporting, reconciliation of purchasing-driven exposures, FX hedging analysis, and settlement tracking. A common query filters by the purchasing module:

• SELECT transaction_number, company_code, deal_type, exposure_type, currency, amount, value_date FROM xtr_a_exposure_transactions_v WHERE purchasing_module = :p_module;
• SELECT transaction_number, cparty_code, payment_amount, payment_status, balance FROM xtr_a_exposure_transactions_v WHERE payment_status <> 'PAID' ORDER BY value_date;
• SELECT portfolio_code, currency, SUM(amount_hce) total_exposure FROM xtr_a_exposure_transactions_v WHERE covered_by_fx_contract = 'N' GROUP BY portfolio_code, currency;

Because the view performs no filtering or aggregation, all business logic must be supplied in the query predicate. Direct DML should be avoided; exposure records are maintained through the Treasury application or its associated APIs.