Search Results ce_ce_cashflows_v




Overview
Explore in AI Chat

Overview

The APPS.CE_CE_CASHFLOWS_V view is a reporting and integration construct within the Oracle Cash Management (CE) module. It presents a consolidated, query-ready projection of cashflow records maintained in the CE_CASHFLOWS table, enriched with transaction subtype descriptions and system-level parameters. In Oracle EBS 12.1.1 and 12.2.2, the view carries a status of VALID and is owned by the APPS schema, making it accessible to standard report definitions, concurrent programs, and downstream integrations that require cashflow visibility without directly querying the base transaction table.

The view's principal role is to expose normalized cashflow data — including base (ledger) currency amounts, status information, and bank account identifiers — while restricting the row set to cashflows in a meaningful lifecycle state. Specifically, only records whose CASHFLOW_STATUS_CODE is CREATED, CLEARED, or RECONCILED are returned, ensuring that draft or otherwise incomplete cashflows do not pollute reporting output.

Underlying Base Objects

Per the documented ETRM metadata, CE_CE_CASHFLOWS_V is defined over the following referenced objects:

The join to CE_SYSTEM_PARAMETERS is an equi-join (not outer), meaning cashflows tied to a legal entity without a matching system parameter row are excluded. The subtype join is outer, so cashflows lacking a mapped subtype code still appear, with null subtype name and code ID.

Key Columns

The view exposes the following notable columns, several of which are computed rather than passed through directly:

  • CASHFLOW_ID — surrogate identifier of the underlying cashflow row.
  • CASHFLOW_DIRECTION — indicates inflow versus outflow.
  • CASHFLOW_AMOUNT and BASE_AMOUNT — the transaction amount and its ledger-currency equivalent. When BASE_AMOUNT is null, the view derives it using CEP_STANDARD.GET_CONVERSION_RATE with the cashflow ledger, currency, date, and the system exchange rate type.
  • TRXN_SUBTYPE / TRXN_SUBTYPE_CODE_ID — the subtype name and identifier sourced from CE_TRXNS_SUBTYPE_CODES.
  • CURRENCY_CODE, CASHFLOW_DATE, ACTUAL_VALUE_DATE, CLEARED_DATE — dates are truncated via TRUNC for consistent day-level reporting.
  • CASHFLOW_STATUS — one of the three lifecycle codes noted above.
  • CASHFLOW_BANK_ACCOUNT_ID — the user's searched term; this identifies the bank account associated with the cashflow, enabling bank-account-level cash positioning and reconciliation reporting.
  • COUNTERPARTY_PARTY_ID and COUNTERPARTY_BANK_ACCOUNT_ID — counterparty identifiers for the opposing side of the transaction.
  • CASH_ACTIVITY_DATE — computed as TRUNC(NVL(ACTUAL_VALUE_DATE, CASHFLOW_DATE)).

Common Use Cases and Queries

The view is typically used for cash positioning, bank account analysis, and reconciliation reporting. A frequent pattern filters by bank account, the searched column cashflow_bank_account_id:

  • SELECT cashflow_id, cashflow_bank_account_id, cashflow_amount, base_amount, cash_activity_date FROM ce_ce_cashflows_v WHERE cashflow_bank_account_id = :p_bank_account_id ORDER BY cash_activity_date;
  • Aggregating net flow by direction: SELECT cashflow_direction, SUM(base_amount) FROM ce_ce_cashflows_v GROUP BY cashflow_direction;
  • Reconciliation review: SELECT cashflow_id, cashflow_status, cleared_date FROM ce_ce_cashflows_v WHERE cashflow_status = 'CLEARED';

Because the view filters by status and joins system parameters, consumers should be aware that unresolved legal-entity parameters and non-standard statuses will suppress rows. No database links or external dependencies are documented; the view operates entirely within APPS.