Search Results signed_amount




Overview

APPS.XTR_INTRADAY_STATEMENTS_V is a supplementary view owned by the APPS schema within the Oracle Treasury (ETRM) module of Oracle E-Business Suite. It is classified as a VALID database object in both 12.1.1 and 12.2.2, and its FND Design Data registration is XTR.XTR_INTRADAY_STATEMENTS_V. The view exposes bank intraday statement information — header-level control totals combined with line-level transaction detail — in a single denormalized structure. Its documented purpose is to simplify forms coding within Oracle Applications, presenting joined statement header and line attributes so that Treasury bank statement entry and reconciliation forms can retrieve header control information alongside individual statement lines without issuing multiple queries.

The metadata carries the standard Oracle restriction applicable to internal Treasury objects: Oracle Corporation does not support access to Oracle applications data using this object except from standard Oracle Applications programs, and the view may change dramatically in subsequent minor or major releases. It should therefore be treated strictly as a read-only reporting and diagnostics object.

Underlying Base Objects

The documented referenced base objects are CE_INTRA_STMT_HDRS_LINES_V (a view), FND_GLOBAL (a package), and the synonyms XTR_BANK_ACCOUNTS, XTR_COMPANY_AUTHORITIES, and XTR_DEALER_CODES. The central dependency is CE_INTRA_STMT_HDRS_LINES_V, which supplies the intraday statement header and line records sourced from the Cash Management (CE) intraday statement tables. XTR_BANK_ACCOUNTS provides the bank account definition, enabling resolution of BANK_ACCOUNT_ID to a Treasury bank account. XTR_COMPANY_AUTHORITIES and XTR_DEALER_CODES supply organizational and dealer-level authorization context. FND_GLOBAL is invoked to apply the runtime security context — notably the current user, login, and responsibility-based access filtering — so that rows returned respect the Treasury company and bank account authorities of the session.

Key Columns

Common Use Cases and Queries

Typical usage includes intraday cash position reporting, reconciliation of statement lines to control totals, and diagnostics of auto-loaded statements. A sample query returning signed line amounts for a bank account is:

SELECT statement_number, line_number, trx_date, trx_type, amount, signed_amount FROM apps.xtr_intraday_statements_v WHERE bank_account_id = :p_bank_account_id ORDER BY statement_number, line_number;

Because Oracle does not support direct querying, such SQL should be confined to controlled reporting environments, and consumers should expect column changes across releases.