Search Results ce_payment_transactions




Overview

CE_PAYMENT_TRANSACTIONS is a Cash Management (CE) base table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores bank account transfer information. It records transactions initiated by a treasury user to move funds between internal bank accounts, including the source and destination bank accounts, legal entities, parties, currency, and payment amounts. The table also captures the lifecycle of each transfer, from submission through authorization, settlement, and reconciliation against bank statement lines. The row is owned by the CE schema and is classified as VALID in the ETRM repository, with 60 documented columns.

From a data modeling perspective, the FK evidence suggests CE_PAYMENT_TRANSACTIONS is best treated as a standalone entity rather than a dependent child. The heuristic Data Vault classification is standalone, meaning it does not behave as a hub, link, or satellite within a strictly normalized vault model according to the mined relationships; it is an independent transactional record with selective outbound references.

Key Information Stored

The unique index CE_PAYMENT_TRANSACTIONS_U1 combines TRXN_REFERENCE_NUMBER and TRXN_STATUS_CODE, positioning these as the business-key candidate. TRXN_REFERENCE_NUMBER carries the transaction's externally meaningful identifier, while TRXN_STATUS_CODE tracks its workflow state (for example, entered, authorized, or settled).

Common Use Cases and Queries

Treasury reporting frequently aggregates transfers by currency, legal entity, or counterparty. A typical reconciliation query joins bank statement lines through CREATE_FROM_STMTLINE_ID to confirm that recorded transfers cleared the bank:

SELECT p.trxn_reference_number, p.payment_amount, p.transaction_date, p.bank_trxn_number FROM ce_payment_transactions p WHERE p.trxn_status_code = 'SETTLED' AND p.transaction_date BETWEEN :from_date AND :to_date;

Analysts also use this table to identify unmatched or pending transfers, verify authorization status, and trace document sequence values for audit. Because source and destination bank accounts are both stored, the table supports net cash position reporting across internal accounts, and the EXT_BANK_ACCOUNT_ID reference enables integration with external or third-party bank account information.

Related Objects

The documented foreign keys anchor this table to two principal references, and additional Cash Management objects integrate at the transaction level:

Collectively these relationships make CE_PAYMENT_TRANSACTIONS the transactional center of internal bank-to-bank fund movement within Oracle Cash Management.