Search Results select_reference

Overview

XTR_R_EXPOSURE_TRANSACTIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the XTR (Treasury) product module. It is a valid, compiled database object at release levels 12.1.1 and 12.2.2 and functions as the published read interface to the Treasury exposure transactions data set. The view projects the complete set of columns from its underlying base object without any filtering, joining, aggregation, or transformation logic; the view text is a straight SELECT of the base transaction attributes.

Because XTR covers treasury deal capture, exposure tracking, cash forecasting, and risk-related processing, this view is the reference surface used by downstream reporting, reconciliation, and integration routines that need to read exposure transaction records without accessing the base table directly. The notably wide column list—spanning deal identification, counterparty and bank details, currency and settlement amounts, status codes, archival indicators, and estimate fields—reflects the breadth of the underlying treasury exposure record. The presence of a SELECT_REFERENCE column, and the related SELECT_ACTION column, indicates that the view supports the Treasury "select/action" workflow, in which individual exposure lines can be flagged, referenced, and acted upon by users or background processes. This directly answers the requirement behind a "select_reference" search: the column carrying the user- or process-assigned reference for an exposure transaction is exposed here.

Underlying Base Objects

The view is defined over a single base object: the synonym XTR_R_EXPOSURE_TRANSACTIONS. There are no documented joins to other tables, and no WHERE clause, DISTINCT, GROUP BY, or functional expressions are present. Consequently, one row in the view corresponds to exactly one row in the base exposure transactions table, and any predicate, sort, or aggregation must be supplied by the calling query.

The naming convention (_R_) is consistent with Treasury transaction/record entities, and the column set—including ARCHIVE_DATE, ARCHIVE_BY, AUDIT_INDICATOR, and the standard WHO columns CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON—confirms that the base object carries full audit and archiving support. Because the view is a pure projection, any grant or synonym created on the view provides effective read access to the same rows as the base synonym, subject to the security applied at the table level.

Key Columns

• TRANSACTION_NUMBER, DEAL_TYPE, DEAL_SUBTYPE, DEAL_STATUS, STATUS_CODE — core deal identifiers and lifecycle state.
• COMPANY_CODE, PORTFOLIO_CODE, SUBSIDIARY_REF, CPARTY_CODE, CPARTY_REF, THIRDPARTY_CODE, BENEFICIARY_CODE — organisational, portfolio, and counterparty attribution.
• CURRENCY, AMOUNT, AMOUNT_HCE, NZD_AMOUNT, CONTRA_NZD_AMOUNT, PAYMENT_AMOUNT, BALANCE, AVG_RATE, PROFIT_LOSS — monetary and valuation measures, including the reporting-currency (HCE) equivalent.
• VALUE_DATE, ESTIMATE_DATE, ESTIMATE_AMOUNT — dating and forecast information.
• EXPOSURE_TYPE, AMOUNT_TYPE, ACTION_CODE, SELECT_ACTION, SETTLE_ACTION_REQD, COVERED_BY_FX_CONTRACT — exposure classification and the action/selection workflow.
• SELECT_REFERENCE, WHOLESALE_REFERENCE, COMMENTS — the descriptive reference carried on the exposure line; SELECT_REFERENCE is the key column for a "select_reference" lookup.
• ACCOUNT_NO, INTERMEDIARY_BANK_DETAILS, PAYMENT_STATUS, TAX_BROKERAGE_TYPE, FIS_FOB, PURCHASING_MODULE — settlement, banking, tax, and sourcing attributes.
• ARCHIVE_DATE, ARCHIVE_BY, AUDIT_INDICATOR and the WHO columns — audit and archival control.

Common Use Cases and Queries

The view is typically queried to retrieve exposure positions for reporting, to reconcile treasury balances against general ledger or cash management, and to drive Extracts/APIs that consume Treasury exposure data. Because no filtering exists in the view, queries should always include selective predicates and bind variables to avoid full scans of the exposure table.

Retrieving an exposure line by its selection reference:

• SELECT transaction_number, deal_type, currency, amount, amount_hce, value_date, select_action, select_reference FROM xtr_r_exposure_transactions_v WHERE select_reference = :p_select_reference;

Listing outstanding exposure by counterparty and currency:

• SELECT company_code, cparty_code, cparty_ref, currency, SUM(amount) total_amount, SUM(amount_hce) total_hce FROM xtr_r_exposure_transactions_v WHERE status_code = :p_status AND value_date BETWEEN :p_from AND :p_to GROUP BY company_code, cparty_code, cparty_ref, currency ORDER BY company_code, cparty_code, currency;

Identifying unsettled items requiring action:

• SELECT transaction_number, deal_type, deal_subtype, payment_status, settle_action_reqd, action_code, value_date FROM xtr_r_exposure_transactions_v WHERE settle_action_reqd = 'Y' AND payment_status <> 'SETTLED' ORDER BY value_date;

Reviewing archived versus active records for audit purposes:

• SELECT transaction_number, archive_date, archive_by, audit_indicator, created_by, created_on FROM xtr_r_exposure_transactions_v WHERE archive_date IS NULL AND audit_indicator = :p_indicator;

In all cases the view preserves the full column set of the base object, so it can substitute for direct queries against the underlying exposure transactions table while providing a stable, documented interface for custom reports and integrations across both 12.1.1 and 12.2.2.