Results for “ce_forecast_trx_cells”

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

Overview

CE_FORECAST_TRX_CELLS is a transaction-level forecast table in the Cash Management (CE) module of Oracle E-Business Suite, owned by the CE schema and valid in both release 12.1.1 and 12.2.2. The table stores forecast data at the individual transaction cell level, meaning each row represents a single intersection of a forecast row and a forecast column, enriched with transactional detail such as amount, currency, transaction date, and bank account. It is the lowest-grain storage unit within the Cash Management forecasting infrastructure, supporting the generation and analysis of projected cash positions.

From a dimensional modeling perspective, the documented foreign key structure suggests this object behaves as a link entity in a Data Vault model. It resolves the many-to-many relationship between forecast rows, forecast columns, and bank accounts, while also carrying descriptive attributes (amount, currency, transaction date) that could alternatively be modeled as a satellite. The surrogate primary key, FORECAST_CELL_ID, uniquely identifies each cell.

Key Information Stored

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

• FORECAST_CELL_ID – The surrogate primary key, enforced by CE_FORECAST_TRX_CELLS_PK and reinforced by unique index CE_FORECAST_TRX_CELLS_U1.
• FORECAST_ID and FORECAST_HEADER_ID – Identify the parent forecast and its header, anchoring the cell to a specific forecast definition.
• FORECAST_ROW_ID – Foreign key to CE_FORECAST_ROWS; defines the row (often a transaction category or template line) in the forecast grid.
• FORECAST_COLUMN_ID – Foreign key to CE_FORECAST_COLUMNS; defines the column (typically a time period such as a day or week).
• BANK_ACCOUNT_ID – Foreign key to AP_BANK_ACCOUNTS_ALL, linking the forecast cell to a specific bank account.
• AMOUNT and TRX_AMOUNT – Monetary values associated with the forecasted transaction.
• CURRENCY_CODE – Currency of the stored amounts.
• TRX_DATE – Date of the underlying transaction or expected cash event.
• REFERENCE_ID – Reference to the originating source transaction.
• CODE_COMBINATION_ID – Accounting flexfield reference for the cell.
• ORG_ID – Operating unit identifier, supporting multi-org reporting.
• INCLUDE_FLAG – Indicates whether the cell is included in forecast calculations.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include cash position forecasting reports, bank account liquidity analysis, and reconciliation of forecasted versus actual cash flows. A common query pattern joins the cell table to its row, column, and header parent tables to reconstruct the forecast grid:

• Retrieve forecast amounts by bank account and date range: SELECT bank_account_id, trx_date, SUM(amount) FROM ce_forecast_trx_cells WHERE forecast_header_id = :id GROUP BY bank_account_id, trx_date.
• Reconstruct grid intersections by joining to CE_FORECAST_ROWS and CE_FORECAST_COLUMNS on FORECAST_ROW_ID and FORECAST_COLUMN_ID.
• Filter included cells using INCLUDE_FLAG for scenario-based forecasting.
• Multi-org reporting filtered by ORG_ID.

Related Objects

The most significant related objects, based on documented foreign keys, are:

• CE_FORECAST_ROWS – joined on FORECAST_ROW_ID.
• CE_FORECAST_COLUMNS – joined on FORECAST_COLUMN_ID.
• CE_FORECAST_HEADERS – joined on FORECAST_HEADER_ID.
• AP_BANK_ACCOUNTS_ALL – joined on BANK_ACCOUNT_ID.
• GL_CODE_COMBINATIONS – commonly joined on CODE_COMBINATION_ID for account analysis.