Results for “ce_fc_rx_v”

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

Overview

CE_FC_RX_V is an APPS-owned database view in the Oracle E-Business Suite Cash Management (CE) module. It belongs to the Cash Forecasting reporting layer and is documented as a retrofitted object, meaning it was regenerated or recreated during an upgrade cycle to preserve compatibility with the existing forecast reporting architecture. The view presents cash forecast data in a pivoted, denormalized layout: each row represents a single forecast row (a labelled line of the forecast grid) combined with its period-by-period amount columns, its title hierarchy, and its descriptive meaning. The naming convention reflects its structural role — FC for forecast, RX for the title/row expansion family, and the _V suffix confirming it is a view rather than a table.

In Oracle EBS 12.1.1 and 12.2.2 the object remains valid under the APPS schema. Its purpose is to expose the cash forecast matrix to Oracle Reports, BI Publisher layouts, and custom SQL used by treasury analysts, allowing a forecast to be read as a flat result set without first resolving the underlying forecast line and amount tables.

Underlying Base Objects

The documented base objects fall into three functional groups:

• Title hierarchy views — CE_FC_RX_TITLE1_V through CE_FC_RX_TITLE7_V. These supply the seven title levels of the forecast structure and are joined on FORECAST_NAME. Each contributes a contiguous block of COLUMN0 through COLUMN80 output slots.
• Data views and synonyms — CE_FC_RX_SUMMARY_V, CE_FORECAST_LINES_AMT_V, the CE_FORECASTS synonym, and the CE_FORECAST_ROWS synonym. These provide the forecast definition header, the row definitions, and the period amounts.
• Lookup view — CE_LOOKUPS, which resolves the MEANING column used for the display label of each forecast row.

The view text is constructed as a UNION of two query blocks. The first block joins the seven title views to produce the header/summary band, emitting literal placeholders (0, NULL, NULL) for the row number, meaning, and description positions. The second block draws the detail rows from the forecast and forecast-line sources and emits the numeric values through TO_CHAR(FL.COLUMN0) … TO_CHAR(FL.COLUMNn) conversions, aligning them against the same eighty-column grid produced by the title branch.

Key Columns

• FORECAST_NAME (aliased from F1.FORECAST_NAME / F.NAME) — the identifier of the cash forecast; the join key across all seven title views.
• Row number — emitted as literal 0 in the header branch and as FR.ROW_NUMBER in the detail branch, allowing consumers to order and distinguish summary rows from data rows.
• MEANING — the lookup-derived display label for a forecast row; NULL in the header branch.
• DESCRIPTION — the forecast row description text; NULL in the header branch.
• COLUMN0 through COLUMN80 — the pivoted forecast values. In the header branch these carry the title-level text; in the detail branch they are the TO_CHAR-converted period amounts drawn from the forecast line amount source.

Common Use Cases and Queries

The view is typically consumed to render a complete forecast grid. Because all amount columns are character-typed by the TO_CHAR conversion, queries usually apply explicit ordering and filter on a single forecast name:

• Extracting a full forecast matrix for a report layout: SELECT * FROM apps.ce_fc_rx_v WHERE forecast_name = :p_forecast ORDER BY 2;
• Listing available forecasts referenced by the view: SELECT DISTINCT forecast_name FROM apps.ce_fc_rx_v ORDER BY 1;
• Retrieving only detail rows (excluding the header band) by filtering on the row-number position or non-null MEANING: SELECT forecast_name, column0, column1, column2 FROM apps.ce_fc_rx_v WHERE forecast_name = :p_forecast AND meaning IS NOT NULL;
• Numeric conversion for downstream aggregation, since the view exposes character data: SELECT forecast_name, TO_NUMBER(column0) amt FROM apps.ce_fc_rx_v WHERE meaning IS NOT NULL;

Because the object is a view rather than a table, no DML is permitted against it; all access is read-only, and performance depends on the efficiency of the underlying title views and forecast line amount view. When tuning queries, the FORECAST_NAME predicate should always be supplied to constrain the seven-way join.