Search Results ce_forecast_rows_pk

Overview

CE_FORECAST_ROWS is a Cash Management (CE) table that defines the individual rows of a cash forecast template. Each row represents a forecast source — a specific stream of expected cash inflows or outflows — configured within a forecast template stored in the parent table CE_FORECAST_HEADERS. Forecast sources may draw from receivables, payables, payroll, purchase orders, sales orders, budgets, and encumbrances, and each row carries the selection criteria and behavioral flags that determine how amounts are computed and displayed across forecast periods.

The table acts as the configuration backbone of the Cash Management forecast engine. Its unique indexes (CE_FORECAST_ROWS_U1 on FORECAST_ROW_ID and CE_FORECAST_ROWS_U2 on FORECAST_HEADER_ID and ROW_NUMBER) establish both a surrogate identity and a business-key candidate that fixes row sequence within a template. The FK relationship set covering sales stages, receipt methods, bank accounts, budget versions, and order types confirms the table's role as a polymorphic configuration record spanning multiple source systems.

From a Data Vault modeling perspective, the heuristic classification suggests a satellite-leaning pattern: the row is keyed by a single surrogate (FORECAST_ROW_ID) and carries a broad set of descriptive and criteria attributes, while its relationships to CE_FORECAST_CELLS and CE_FORECAST_TRX_CELLS represent dependent child data rather than peer entities.

Key Information Stored

• FORECAST_ROW_ID — surrogate primary key (CE_FORECAST_ROWS_PK); the unique identifier for each forecast row.
• FORECAST_HEADER_ID — foreign key to CE_FORECAST_HEADERS, identifying the owning template.
• ROW_NUMBER — sequence position within the template; combined with FORECAST_HEADER_ID it forms the unique business key U2.
• TRX_TYPE / TYPE — the source transaction category that the row aggregates (for example, receipts, payments, payroll, or budgets).
• DESCRIPTION — user-facing label shown on the forecast worksheet.
• FORECAST_METHOD — the computation approach used to spread amounts into forecast periods.
• LEAD_TIME / ROLL_FORWARD_TYPE / ROLL_FORWARD_PERIOD — timing controls governing when amounts enter the forecast and how they roll between periods.
• SET_OF_BOOKS_ID / CHART_OF_ACCOUNTS_ID — ledger context for budget- and encumbrance-sourced rows.
• BUDGET_NAME / BUDGET_VERSION_ID / ENCUMBRANCE_TYPE_ID — budget and commitment parameters for GL-based forecast sources.
• RECEIPT_METHOD_ID / BANK_ACCOUNT_ID / CUSTOMER_PROFILE_CLASS_ID — receivables-side selection criteria.
• PAYMENT_METHOD / PAY_GROUP / VENDOR_TYPE / PAYMENT_PRIORITY — payables-side selection criteria.
• SALES_STAGE_ID / CHANNEL_CODE / WIN_PROBABILITY / ORDER_TYPE_ID — sales-order weighting parameters.
• LEGAL_ENTITY_ID / ORG_ID — organizational scoping for multi-entity deployments.
• CRITERIA_CATEGORY and CRITERIA1–CRITERIA15 — extensible descriptive flexfield-style filter values.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — standard EBS descriptive flexfield columns.

Common Use Cases and Queries

The most frequent requirement is reviewing the configured rows of a given forecast template, ordered by their display sequence. A representative query joins the row to its header to present the template name alongside source configuration:

• SELECT r.row_number, r.description, r.trx_type, r.forecast_method FROM ce_forecast_rows r WHERE r.forecast_header_id = :header_id ORDER BY r.row_number;
• Determining which ledger a budget-sourced row uses: query rows where TYPE or TRX_TYPE indicates a budget source and join SET_OF_BOOKS_ID to GL_SETS_OF_BOOKS_11I.
• Identifying all templates that reference a particular bank account or receipt method, useful before inactivating those AR or AP setup values.
• Auditing flexfield usage by selecting ATTRIBUTE1 through ATTRIBUTE15 and CRITERIA1 through CRITERIA15 for a template.
• Reconciling forecast output by joining CE_FORECAST_ROWS to CE_FORECAST_CELLS on FORECAST_ROW_ID to compare configured criteria against generated period amounts.

Reporting extracts typically pivot rows by ROW_NUMBER to reproduce the worksheet layout, and integration routines read this table when cloning templates between environments.

Related Objects

• CE_FORECAST_HEADERS — parent template; joined via FORECAST_HEADER_ID.
• CE_FORECAST_CELLS — period-level forecast amounts; references CE_FORECAST_ROWS.FORECAST_ROW_ID, joined on that column.
• CE_FORECAST_TRX_CELLS — transaction-level detail supporting each forecast cell; joined via FORECAST_ROW_ID.
• CE_FORECAST_ERRORS — error records raised during forecast generation; joined via FORECAST_ROW_ID.
• AR_RECEIPT_METHODS — referenced through RECEIPT_METHOD_ID for receivables sources.
• AP_BANK_ACCOUNTS_ALL — referenced through BANK_ACCOUNT_ID (and the XTR_BANK_ACCOUNT column).
• GL_BUDGET_VERSIONS — referenced through BUDGET_VERSION_ID for budget-based rows.
• GL_ENCUMBRANCE_TYPES — referenced through ENCUMBRANCE_TYPE_ID for commitment-based rows.
• GL_SETS_OF_BOOKS_11I — referenced through SET_OF_BOOKS_ID for ledger context.
• AR_CUSTOMER_PROFILE_CLASSES — referenced through CUSTOMER_PROFILE_CLASS_ID for receivables segmentation.