Search Results ar_customer_profile_classes

Overview

The CE_FORECAST_ROWS table is a core data object within Oracle E-Business Suite Cash Management (CE) module, specifically for versions 12.1.1 and 12.2.2. It functions as the detailed repository for individual forecast sources or lines that constitute a cash forecast template. Each row in this table defines a specific source of cash inflow or outflow, such as a particular bank account, receipt method, or budget, that is to be included in a forecast model. The table's primary role is to store the configuration and parameters for these forecast sources, which are then used by the Cash Management engine to generate projected cash flow data over a defined forecast period. It acts as the child entity to the forecast template header (CE_FORECAST_HEADERS) and the parent entity to the generated forecast data cells (CE_FORECAST_CELLS).

Key Information Stored

The table's structure is designed to capture the identity, type, and parameters of a forecast source. The primary identifier is the FORECAST_ROW_ID. Each row is logically linked to its parent template via the FORECAST_HEADER_ID and maintains a sequence within that template using ROW_NUMBER. Key descriptive columns include ROW_NAME and DESCRIPTION. The table's critical functional columns are the foreign keys that define the actual source of the forecast data. These include BANK_ACCOUNT_ID (linking to AP_BANK_ACCOUNTS_ALL), RECEIPT_METHOD_ID (linking to AR_RECEIPT_METHODS), SET_OF_BOOKS_ID, BUDGET_VERSION_ID, ENCUMBRANCE_TYPE_ID, and CUSTOMER_PROFILE_CLASS_ID. The specific foreign key populated determines the type of forecast row (e.g., bank account balance, receipts from a specific method, budget encumbrances). Additional columns control data selection, such as INCLUDE_FLAG and various amount type flags.

Common Use Cases and Queries

This table is central to technical analysis, troubleshooting, and custom reporting for cash forecasts. A common use case is auditing the configuration of a specific forecast template to verify all included sources. For example, to list all forecast rows for a template named 'Monthly Operating Forecast', a developer might execute:

• SELECT cfr.row_number, cfr.row_name, cfr.description FROM ce_forecast_rows cfr, ce_forecast_headers cfh WHERE cfr.forecast_header_id = cfh.forecast_header_id AND cfh.forecast_name = 'Monthly Operating Forecast' ORDER BY cfr.row_number;

Another critical scenario involves identifying the source of data errors in forecast generation by joining to the CE_FORECAST_ERRORS table on FORECAST_ROW_ID. For performance analysis or data reconciliation, queries often join CE_FORECAST_ROWS to CE_FORECAST_CELLS to analyze the projected amounts generated for each source row over time.

Related Objects

CE_FORECAST_ROWS maintains integral relationships with numerous key EBS tables, primarily through foreign key constraints as documented in the ETRM. Its principal relationships are:

• Parent: CE_FORECAST_HEADERS (via CE_FORECAST_ROWS.FORECAST_HEADER_ID)
• Children:
  • CE_FORECAST_CELLS (via CE_FORECAST_CELLS.FORECAST_ROW_ID)
  • CE_FORECAST_ERRORS (via CE_FORECAST_ERRORS.FORECAST_ROW_ID)
  • CE_FORECAST_TRX_CELLS (via CE_FORECAST_TRX_CELLS.FORECAST_ROW_ID)
• Source Definition Tables:
  • AP_BANK_ACCOUNTS_ALL (via BANK_ACCOUNT_ID)
  • AR_RECEIPT_METHODS (via RECEIPT_METHOD_ID)
  • GL_SETS_OF_BOOKS_11I (via SET_OF_BOOKS_ID)
  • GL_BUDGET_VERSIONS (via BUDGET_VERSION_ID)
  • GL_ENCUMBRANCE_TYPES (via ENCUMBRANCE_TYPE_ID)
  • AR_CUSTOMER_PROFILE_CLASSES (via CUSTOMER_PROFILE_CLASS_ID)