Search Results source_trxn_type

Overview

APPS.CE_CE_CASHFLOWS_V is an internal Oracle E-Business Suite view owned by the APPS schema that exposes cashflow records maintained by the Cash Management (CE) module. In the EBS 12.1.1 and 12.2.2 release streams the object carries a status of VALID and is registered in FND Design Data as CE.CE_CE_CASHFLOWS_V. The view presents a denormalized, reporting-friendly projection of treasury cashflows, combining transaction-level attributes such as direction, amount, currency, status, and value dates with contextual references to the owning bank account, legal entity, ledger, and counterparty.

The view is not a supported public interface. Oracle documents it explicitly as Internal Use Only, meaning access is supported only from standard Oracle Applications programs. Consequently, the intended consumers are Oracle's own concurrent programs and internal processing logic rather than customer-written integrations. The dependent object CE_CP_PRIORDAY references the view, which indicates its role in the prior-day cashflow and bank statement processing performed by Cash Management.

Underlying Base Objects

The view is defined over four documented base objects. CE_CASHFLOWS is the principal source of cashflow records and supplies identifiers, amounts, dates, status, and counterparty references. CE_TRXNS_SUBTYPE_CODES provides the transaction subtype lookup, which maps directly to the TRXN_SUBTYPE and TRXN_SUBTYPE_CODE_ID columns. CE_SYSTEM_PARAMETERS contributes environment-level settings used by Cash Management, and CEP_STANDARD is the Cash Management standard package invoked within the view definition to derive or validate certain values.

Within the APPS schema, CE_CASHFLOWS, CE_TRXNS_SUBTYPE_CODES, and CE_SYSTEM_PARAMETERS are exposed as synonyms to their underlying tables, while CEP_STANDARD is a package. The view therefore inherits the security and validation behavior of the CE data model and should be treated as a dependent artifact of those base objects.

Key Columns

• CASHFLOW_ID — Unique cashflow reference number generated by the system; primary identifier for a cashflow record.
• CASHFLOW_DIRECTION — Indicates whether the cashflow is a PAYMENT or a RECEIPT.
• CASHFLOW_AMOUNT — Cashflow amount expressed in the cashflow transaction currency.
• BASE_AMOUNT — Equivalent amount expressed in the ledger or base currency, useful for consolidated reporting.
• TRXN_SUBTYPE — Transaction subtype description; this is the column most relevant to the search term "trxn_subtype."
• TRXN_SUBTYPE_CODE_ID — Foreign key to CE_TRXNS_SUBTYPE_CODES, linking the cashflow to the defined subtype code.
• CURRENCY_CODE — Currency of the cashflow transaction.
• CASHFLOW_DATE, ACTUAL_VALUE_DATE, CLEARED_DATE, CASH_ACTIVITY_DATE — Key dates representing the booked, value, cleared, and cash activity timings of the cashflow.
• CASHFLOW_STATUS — Current processing state of the cashflow.
• CASHFLOW_BANK_ACCOUNT_ID, CASHFLOW_LEGAL_ENTITY_ID, CASHFLOW_LEDGER_ID — Identifiers placing the cashflow within a bank account, legal entity, and ledger context.
• COUNTERPARTY_PARTY_ID, COUNTERPARTY_BANK_ACCOUNT_ID — Counterparty party and bank account references.
• SOURCE_TRXN_TYPE, DESCRIPTION — Origin transaction type and free-text description.

Common Use Cases and Queries

Because the view is internal, typical use cases center on reconciliation reporting, prior-day cash positioning, and treasury analysis. A common pattern is filtering on the transaction subtype exposed by TRXN_SUBTYPE, which is the term matching the user's search. The following query illustrates listing cashflows by subtype and direction:

SELECT cashflow_id, cashflow_direction, trxn_subtype, cashflow_amount, currency_code, cashflow_status FROM apps.ce_ce_cashflows_v WHERE trxn_subtype = :p_subtype AND cashflow_direction = 'RECEIPT';

A second scenario aggregates cashflow values by ledger and date for cash positioning:

SELECT cashflow_ledger_id, TRUNC(cashflow_date) cf_date, SUM(base_amount) total_base FROM apps.ce_ce_cashflows_v WHERE cashflow_direction IN ('PAYMENT','RECEIPT') GROUP BY cashflow_ledger_id, TRUNC(cashflow_date) ORDER BY cf_date;

When joining to subtype definitions for descriptive reporting, analysts may relate TRXN_SUBTYPE_CODE_ID to CE_TRXNS_SUBTYPE_CODES. Given the internal-only designation, any custom use should be reviewed against Oracle support policy, and direct queries should be limited to read-only diagnostic or reporting purposes.