Results for “cebv_cash_forecast_cells”

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

Overview

CEBV_CASH_FORECAST_CELLS is an APPS-owned business view in the Oracle E-Business Suite Cash Management (CE) module. It presents a denormalized, reporting-friendly projection of the forecast cell data held in the Cash Management forecasting engine, joining transaction-level forecast rows and columns with their descriptive lookups, bank account attributes, payment attributes, and accounting flexfield references. The view is valid and available in both Oracle EBS 12.1.1 and 12.2.2.

Its role is primarily analytical and integration-oriented: rather than forcing external reports or interfaces to traverse the normalized CE_FORECAST_HEADERS, CE_FORECASTS, CE_FORECAST_ROWS, CE_FORECAST_COLUMNS, and CE_FORECAST_CELLS hierarchy, the view exposes each populated cell together with human-readable meanings, dates, amounts, and source identifiers. This makes it suitable for cash positioning dashboards, forecast variance reports, treasury extracts, and downstream data warehouse loads that need a single flattened row per forecast cell.

Underlying Base Objects

The view is defined over a large join of Cash Management forecasting tables plus supporting reference objects. The documented base objects include CE_FORECAST_CELLS (the grain-defining table of amounts), CE_FORECAST_HEADERS, CE_FORECASTS, CE_FORECAST_ROWS, CE_FORECAST_COLUMNS, and CE_FORECAST_TRX_CELLS. Descriptive enrichment comes from CE_LOOKUPS and AR_LOOKUPS (lookup meanings), CE_BANK_ACCOUNTS, GL_SETS_OF_BOOKS, GL_PERIODS, GL_PERIOD_TYPES, GL_CODE_COMBINATIONS, and GL_ENCUMBRANCE_TYPES. Payment-side attributes are sourced from PAY_ORG_PAYMENT_METHODS_F, PAY_ALL_PAYROLLS_F, PAY_EXTERNAL_ACCOUNTS, AR_RECEIPT_METHODS, HZ_CUST_PROFILE_CLASSES, PO_LOOKUP_CODES, HR_ALL_ORGANIZATION_UNITS, and HR_ORGANIZATION_INFORMATION. FND_GLOBAL is referenced as a package, typically to derive session context such as the current user or organization.

Relationships are driven by foreign keys: forecast header to cell, forecast to cell, forecast row to cell, and forecast column to cell. Outer joins are used for optional dimensions such as bank account and set of books, allowing rows for forecast lines that have no bank account or ledger assigned.

Key Columns

• FORECAST_CELL_ID, FORECAST_ID: Primary identifiers for the cell and its parent forecast.
• MEANING (L1–L6): Decoded lookup meanings for transaction type, row/column classifications, payment method, and related codes.
• START_DATE, END_DATE: Effective period boundaries for the forecast cell (from GL_PERIODS aliases PS and PE).
• AMOUNT: The forecasted cash amount for the cell.
• DESCRIPTION, LEAD_TIME: Forecast row description and the lead time applied to the transaction.
• BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM: Bank account context for the forecast line.
• PAYMENT_METHOD, PAY_GROUP, VENDOR_TYPE, PAYMENT_PRIORITY: Payment attributes, with PAY_ORG_PAYMENT_METHODS_F used to resolve the organization payment method name.
• CODE_COMBINATION_ID: Accounting flexfield reference tied to the forecast cell.
• ENCUMBRANCE_TYPE, BUDGET_NAME: Budgetary control attributes.
• CRITERIA1–CRITERIA14: Flexible user-defined criteria columns for custom classification and filtering.
• PAYROLL_NAME, ORG_INFORMATION9, NAME: Payroll, organization, and receipt method descriptive attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard audit columns.

Common Use Cases and Queries

Typical scenarios include generating cash forecast reports by transaction type, comparing forecasted amounts against bank balances, and extracting forecast data for treasury or ERP data warehouses. Because the view flattens lookup meanings and account attributes, it eliminates most join work for report developers.

A representative query retrieves forecast cells by date range and transaction type:

• SELECT FORECAST_ID, FORECAST_CELL_ID, MEANING, START_DATE, END_DATE, AMOUNT, BANK_ACCOUNT_NAME, PAYMENT_METHOD FROM APPS.CEBV_CASH_FORECAST_CELLS WHERE START_DATE BETWEEN :p_start AND :p_end AND MEANING = 'Payables';
• Aggregating by bank account: SELECT BANK_ACCOUNT_NAME, SUM(AMOUNT) FROM APPS.CEBV_CASH_FORECAST_CELLS GROUP BY BANK_ACCOUNT_NAME;
• Filtering on custom criteria: SELECT * FROM APPS.CEBV_CASH_FORECAST_CELLS WHERE CRITERIA1 = :p_criteria;

Because the view spans many base objects, queries should filter on indexed identifiers (FORECAST_ID, BANK_ACCOUNT_ID) and dates to maintain performance. Access is typically granted through the Cash Management responsibility or a custom read-only role against the APPS schema.