Search Results credit_line_count




Overview
Explore in AI Chat

Overview

APPS.CEFV_BANK_STATEMENTS is a public Oracle E-Business Suite view owned by the APPS schema and registered under the Application Object Library design data as CE.CEFV_BANK_STATEMENTS. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents a consolidated, reporting-oriented projection of bank statement information combined with header-level reconciliation status. The documentation describes it as a public view which may be useful for custom reporting or other data requirements.

Conceptually, the view represents a bank statement received from a bank, along with the detailed banking transactions — debits and credits — and their reconciliation status. It does not itself store transactional detail lines; instead it exposes header-level summary attributes, including debit and credit totals and the corresponding line counts. In the broader Cash Management (CE) schema, CEFV_BANK_STATEMENTS serves as a denormalized read-only layer that joins statement header data to bank account and organization context, which makes it suitable for operational reporting, reconciliation dashboards, and integration extracts without requiring the consumer to navigate multiple base tables.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, CEFV_BANK_STATEMENTS is defined over the following referenced base objects, each exposed through public synonyms:

  • CE_STATEMENT_HEADERS (SYNONYM) — the primary source for statement-level attributes such as statement number, statement date, balances, and currency.
  • CE_BANK_ACCOUNTS (SYNONYM) — supplies bank account number and account name associated with the statement.
  • HR_ALL_ORGANIZATION_UNITS (SYNONYM) — supplies the operating unit or organization name and identifier, enabling multi-org filtering via ORG_ID.

The view therefore acts as a join between the statement header, the bank account definition, and the organization/operating unit model. Because it is a view rather than a table, it performs no independent data storage; every query is resolved against the current state of these base objects at runtime.

Key Columns

The view exposes identifiers, balances, summary totals, counts, and standard WHO audit columns. Principal columns include:

Common Use Cases and Queries

Typical usage includes reconciliation status reporting, statement line-volume analysis, and bank account level balance extracts. A representative query counting receipt transactions per statement is shown below.

  • Identify unreconciled statements: filter on COMPLETION_STATUS and STATEMENT_DATE range.
  • Measure transaction volume: aggregate DEBIT_LINE_COUNT and CREDIT_LINE_COUNT by bank account.
  • Extract balances: select BEGINNING_BALANCE, DEBIT_TOTAL, CREDIT_TOTAL, ENDING_BALANCE by CURRENCY_CODE.
  • Restrict by operating unit: apply ORG_ID predicate consistent with MOAC security.

Sample SQL:

  • SELECT STATEMENT_ID, STATEMENT_NUMBER, BANK_ACCOUNT_NUMBER, CREDIT_LINE_COUNT, CREDIT_TOTAL, CURRENCY_CODE FROM APPS.CEFV_BANK_STATEMENTS WHERE ORG_ID = :p_org_id AND STATEMENT_DATE BETWEEN :p_from AND :p_to ORDER BY STATEMENT_DATE DESC;

Because the object is a public view, custom reports and interfaces may query it directly, subject to standard APPS schema privileges and operating unit access controls.