Search Results xtr_interacct_transfers_pk

Overview

XTR_INTERACCT_TRANSFERS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores information related to inter-account transfers. It records the movement of funds or balances between two internal accounts, capturing the source account, destination account, transfer amount, currency, deal classification, and workflow status. This object is central to Treasury's cash management and deal-capture processes, where transfers between company bank accounts or internal portfolios must be tracked, authorised, and reconciled.

From a heuristic Data Vault modelling perspective, the mined foreign-key structure classifies this table as standalone. That classification is a modelling suggestion only: no parent foreign keys were detected in the documented metadata, so the object behaves as an independent transactional record rather than a dependent satellite hanging off a parent hub. In practice, each row is a self-contained transfer event, keyed by its own transaction number.

Key Information Stored

The table contains 43 documented columns. The primary key is XTR_INTERACCT_TRANSFERS_PK, defined on a single column:

• TRANSACTION_NUMBER — surrogate/system-generated primary key uniquely identifying each inter-account transfer. This is also the natural business-key candidate for the record, as no separate unique index is documented.

The most operationally significant descriptive columns include:

• ACCOUNT_NO_FROM and ACCOUNT_NO_TO — the originating and receiving accounts, defining the transfer direction.
• TRANSFER_AMOUNT and CURRENCY — the monetary value and currency of the transfer.
• TRANSFER_DATE and DEAL_DATE — the effective transfer date and the underlying deal date.
• COMPANY_CODE and PORTFOLIO_CODE — the legal entity and treasury portfolio associated with the transfer.
• DEAL_TYPE, DEAL_SUBTYPE, and PRODUCT_TYPE — deal classification attributes used for reporting and categorisation.
• STATUS_CODE — lifecycle state of the transfer (e.g., entered, authorised, cancelled).
• DEALER_CODE — the dealer responsible for the transaction.
• DUAL_AUTHORISATION_BY and DUAL_AUTHORISATION_ON — audit trail for dual authorisation approval.
• EXTERNAL_SOURCE — indicates data originating from an external system or interface.
• COMMENTS — free-text notes attached to the transfer.

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the DESC_FLEX ATTRIBUTE1–15 columns are also present, along with interface tracking columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage includes treasury reporting, reconciliation of inter-company movements, status monitoring of pending transfers, and audit of dual-authorisation compliance. A representative query lists all transfers for a given date range:

• SELECT transaction_number, account_no_from, account_no_to, transfer_amount, currency, status_code FROM xtr_interacct_transfers WHERE transfer_date BETWEEN :p_from AND :p_to;
• Filter by portfolio or company: WHERE company_code = :company AND portfolio_code = :portfolio.
• Identify unapproved transfers: WHERE dual_authorisation_on IS NULL AND status_code = 'ENTERED'.
• Aggregate net movement by currency: SELECT currency, SUM(transfer_amount) FROM xtr_interacct_transfers GROUP BY currency.
• Trace interface-loaded records: WHERE request_id = :request_id OR external_source IS NOT NULL.

Reports commonly join this table to Treasury deal and portfolio references to present transfer activity alongside other treasury instruments.

Related Objects

Because the table is classified as standalone, no foreign keys were mined from the documented metadata. The most significant related objects are therefore functional rather than enforced by constraints:

• XTR_INTERACCT_TRANSFERS_PK — the primary key constraint on TRANSACTION_NUMBER, used as the join key for downstream references.
• Treasury deal and portfolio tables in the XTR schema, joined by PORTFOLIO_CODE, COMPANY_CODE, and DEAL_TYPE to enrich transfers with portfolio and counterparty context.
• Account and bank master tables in Cash Management (CE), joined by ACCOUNT_NO_FROM and ACCOUNT_NO_TO to resolve account names and bank details.
• Treasury deal-capture and authorisation APIs in the XTR module that insert and validate rows in this table.
• Concurrent request and interface tables referenced through REQUEST_ID and EXTERNAL_SOURCE for reconciliation of externally loaded transfers.

Because no database-level foreign keys were documented, joins to related Treasury and Cash Management objects should be validated against business rules rather than relying on enforced referential integrity.