Search Results drawer_code




Overview
Explore in AI Chat

Overview

XTR_A_ROLLOVER_TRANSACTIONS_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes rollover transaction records for treasury deals, presenting a horizontally flattened projection of rollover transaction data that includes deal identification, drawer and counterparty attributes, principal and interest accounting, brokerage, tax, and settlement information. The "_A_" segment in the object name denotes the audit-related naming convention used throughout the XTR schema, and the object is documented in the ETRM metadata as "Retrofitted," reflecting that the view was recreated or redeployed under the standard APPS-owned deployment model rather than a legacy custom schema. The view carries a STATUS of VALID, confirming that it compiles successfully against its referenced base object in the supported release.

The view functions as a read-oriented access layer over the rollover transaction table. It does not introduce business logic beyond column projection and naming; its value lies in providing a stable, named interface for concurrent programs, OAF pages, and SQL-based reporting without requiring direct access to the underlying table. This is significant because XTR treasury tables are among the most heavily denormalized structures in the application, and views such as this one shield downstream consumers from physical schema changes.

Underlying Base Objects

The documented base object for XTR_A_ROLLOVER_TRANSACTIONS_V is the synonym XTR_A_ROLLOVER_TRANSACTIONS. In a standard EBS deployment, this synonym resolves to the APPS-owned table of the same name, which stores rollover transaction rows generated when a treasury deal reaches its renegotiation or maturity rollover point. The view is defined directly over this single referenced object; the ETRM metadata lists no additional tables, joins, or inline views. Consequently the cardinality of the view matches the base table one-to-one, and the DRAWER_CODE column requested in the user's search originates from the rollover transaction record itself rather than from a joined party table.

Because the relationship is a direct projection, row-level security is not applied by the view definition. Any access restrictions are enforced at the table or synonym grant level, and responsibility-based data filtering is typically implemented by the calling forms or concurrent programs rather than by the view.

Key Columns

The view exposes a broad column set spanning deal, party, financial, and audit attributes. Notable columns include:

Common Use Cases and Queries

The view is typically used for rollover transaction inquiry, reconciliation of principal and interest rollovers, and downstream extraction into treasury reporting. A representative query retrieving rollover transactions by drawer is:

SELECT transaction_number, deal_number, drawer_code, drawer_name, deal_type, currency, principal_adjust, interest, maturity_date FROM xtr_a_rollover_transactions_v WHERE drawer_code = :p_drawer_code ORDER BY deal_date DESC;

For financial reconciliation, filtering on the home currency equivalent columns supports functional currency reporting:

SELECT deal_number, principal_adjust_hce, accum_interest_hce, brokerage_amount_hce, tax_amount_hce FROM xtr_a_rollover_transactions_v WHERE currency = :p_currency AND status_code = 'ACTIVE';

Because the view performs no joins, queries against it are inexpensive relative to treasury inquiry forms that denormalize party and portfolio data at runtime. Analysts should note, however, that the view returns only transaction rows persisted to XTR_A_ROLLOVER_TRANSACTIONS; rollovers still in a pending or unposted state may reside in related dealer deal tables and will not appear here until the rollover transaction is written.