Search Results ce_forecast_opening_bal_pk

Overview

CE_FORECAST_OPENING_BAL is a Cash Management (CE) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the opening bank balance or GL cash account balance for a particular Start Date, tied to a specific set of forecast results. Each row anchors a forecast run to the balance that existed at the period's beginning, which is essential for computing projected closing balances, net cash positions, and cash flow timing across one or more bank accounts and legal entities.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. The table records descriptive, time-stamped balance attributes (opening balance, prior-day cash flow, balance date) that qualify a parent forecast entity through the FORECAST_ID, making it a natural satellite attached to a forecast hub rather than an independent hub or a pure link. Its surrogate primary key, CE_FORECAST_OPENING_BAL_PK on BALANCE_ID, is a system-generated identifier with no business meaning, consistent with satellite design.

Key Information Stored

The most significant columns capture the forecast context, the balance value, and the accounting reference:

• BALANCE_ID — surrogate primary key; uniquely identifies each opening-balance record.
• FORECAST_ID — associates the row with a specific forecast result set; the principal business linkage.
• BALANCE_TYPE — indicates whether the balance represents a bank balance or a GL cash account balance.
• BANK_ACCOUNT_ID — foreign key to AP_BANK_ACCOUNTS_ALL; identifies the bank account when the balance is bank-sourced.
• CODE_COMBINATION_ID — GL accounting flexfield reference used for GL cash account balances.
• OPENING_BALANCE — the monetary opening amount for the forecast period.
• BALANCE_DATE — the Start Date to which the opening balance pertains.
• PRIOR_DAY_CFLOW — carry-forward cash flow from the prior day, used to derive the next opening balance.
• LEGAL_ENTITY_ID — foreign key to FV_LEGAL_ENTITIES; scopes the balance to a legal entity.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

The unique index CE_FORECAST_OPENING_BAL_U1 on BALANCE_ID reinforces the surrogate key as the only documented business-key candidate; no composite natural key is defined, so functional uniqueness derives from the combination of FORECAST_ID, BALANCE_DATE, and the account reference.

Common Use Cases and Queries

The table supports cash positioning and forecasting reports that reconcile projected cash flows against actual opening positions. A typical query retrieves the opening balances for a forecast run:

SELECT o.BALANCE_ID, o.FORECAST_ID, o.BALANCE_TYPE, o.OPENING_BALANCE, o.BALANCE_DATE, o.PRIOR_DAY_CFLOW FROM CE.CE_FORECAST_OPENING_BAL o WHERE o.FORECAST_ID = :forecast_id ORDER BY o.BALANCE_DATE;

To join bank account details, analysts link through AP_BANK_ACCOUNTS_ALL on BANK_ACCOUNT_ID. For GL-based forecasts they join GL_CODE_COMBINATIONS on CODE_COMBINATION_ID. Legal-entity rollups use LEGAL_ENTITY_ID against FV_LEGAL_ENTITIES. PRIOR_DAY_CFLOW supports derived closing-balance calculations (OPENING_BALANCE + PRIOR_DAY_CFLOW).

Related Objects

• AP_BANK_ACCOUNTS_ALL — joined via BANK_ACCOUNT_ID to resolve bank account names and numbers.
• FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID for legal entity attribution.
• GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID for GL cash account detail.
• CE_FORECASTS / forecast result tables — parent of FORECAST_ID linking balance rows to forecast definitions.
• CE_FORECAST_DAILY_BALANCES or equivalent flow tables — consume PRIOR_DAY_CFLOW to build forward projections.
• Cash Management forecast concurrent programs and Cash Position APIs — populate and read this table during forecast generation.