Results for “ce_projected_balances”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_PROJECTED_BALANCES is a Cash Management (CE) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the projected balances of internal bank accounts. It belongs to the CE schema and is classified as VALID in the ETRM repository. The table supports the Cash Management forecasting and reconciliation functionality by persisting the anticipated balance positions of internal bank accounts over time, enabling treasury users and cash managers to review expected cash positions derived from open transactions, payments, receipts, and other cash-affecting activities.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a surrogate primary key (CE_PROJECTED_BALANCES_PK, defined on PROJECTED_BALANCE_ID) and a foreign key to CE_BANK_ACCOUNTS via BANK_ACCOUNT_ID, along with standard audit and version columns. This structure is characteristic of a satellite that records descriptive, time-varying measures (projected balances over a date dimension) attached to a business key represented by the bank account hub. It should not be treated as an independent hub, since it holds no natural business key of its own beyond the surrogate identifier.

Key Information Stored

The table contains ten documented columns. The most significant are:

• PROJECTED_BALANCE_ID — Surrogate primary key, enforced by CE_PROJECTED_BALANCES_PK and reinforced by the unique index CE_PROJECTED_BALANCES_U1. It uniquely identifies each projected balance record.
• BANK_ACCOUNT_ID — Foreign key referencing CE_BANK_ACCOUNTS. Identifies the internal bank account to which the projected balance applies. This is the principal business-key candidate for joining to account master data.
• BALANCE_DATE — The date on which the projected balance is expected to occur, forming the time dimension of the forecast.
• PROJECTED_BALANCE — The anticipated monetary amount for the bank account on the given balance date. This is the core measure of the table.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row, and when.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Object Library to detect concurrent updates.

The surrogate PROJECTED_BALANCE_ID should be distinguished from the business-meaningful combination of BANK_ACCOUNT_ID and BALANCE_DATE, which together identify a projected position for a specific account on a specific day. Reporting logic should generally resolve the surrogate key through joins rather than exposing it directly to end users.

Common Use Cases and Queries

Typical use cases include cash position forecasting, treasury dashboards, and reconciliation of projected versus actual balances. A common query pattern retrieves projected balances for a given bank account over a date range:

• SELECT pb.balance_date, pb.projected_balance FROM ce_projected_balances pb WHERE pb.bank_account_id = :bank_account_id AND pb.balance_date BETWEEN :start_date AND :end_date ORDER BY pb.balance_date;
• Joining to CE_BANK_ACCOUNTS to obtain the account name and number: SELECT ba.bank_account_name, pb.balance_date, pb.projected_balance FROM ce_projected_balances pb, ce_bank_accounts ba WHERE pb.bank_account_id = ba.bank_account_id;
• Aggregating projected balances by date across all internal accounts for a consolidated cash position report.

Because the table stores only projected figures, reconciliation reports typically compare these rows against actual statement balances held in related Cash Management tables. Filters on BALANCE_DATE are essential to constrain the result set, since forecast horizons can extend across many periods.

Related Objects

The most significant related objects, grounded in the documented foreign-key relationships, are:

• CE_BANK_ACCOUNTS — Referenced by CE_PROJECTED_BALANCES.BANK_ACCOUNT_ID; the primary parent of this table, providing internal bank account definitions.
• CE_BANK_ACCT_USES_ALL — Provides the operating unit context and usage settings for the bank account referenced above.
• CE_STATEMENT_HEADERS and CE_STATEMENT_LINES — Source of actual bank statement balances used to reconcile against projected figures.
• CE_CASHFORECAST_* — Cash forecast definition and result tables that can complement projected balance reporting.
• CE_PROJECTED_BALANCES_PK and CE_PROJECTED_BALANCES_U1 — The primary key constraint and unique index enforcing row uniqueness on PROJECTED_BALANCE_ID.

These relationships position CE_PROJECTED_BALANCES as a dependent satellite of bank account master data within the Cash Management schema.