Results for “fc_misc”

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

Overview

CE_FC_AMTS_DISC_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Cash Management (CE). Its name denotes a Forecast Amounts (Discovered/Detailed) view, and it exposes the transactional cell-level data that underpins the Cash Management cash forecasting feature. The view flattens the multi-table structure of forecasts — headers, forecasts, rows, columns, and transaction cells — into a single denormalized result set suitable for reporting, inquiry, and downstream integration. By joining forecast cell amounts to bank account details, legal entity information, trading partners, and lookup translations, the view presents forecast amounts in a business-readable form without requiring consumers to understand the underlying normalized forecast model.

The view is defined in the APPS schema and carries a VALID status, indicating it is a supported, compiled object in both 12.1.1 and 12.2.2 environments. It is not a base table; it is a convenience layer over the CE_FORECAST_* family of tables plus cross-module reference views.

Underlying Base Objects

The documented base objects referenced by CE_FC_AMTS_DISC_V are:

• CE_FORECAST_TRX_CELLS — the fact table holding individual forecast cell amounts by row, column, and transaction.
• CE_FORECAST_ROWS — defines each forecast row (transaction type, row number, description).
• CE_FORECAST_COLUMNS — defines each forecast column (dates, developer column numbers, day offsets).
• CE_FORECASTS and CE_FORECAST_HEADERS — the forecast definition and its header, supplying name, currency, start date, factor, and header identifier.
• CE_BANK_ACCOUNTS — supplies bank account name, number, and currency.
• CE_LOOKUPS — the Cash Management lookup view, joined multiple times (aliases L through L7) to translate transaction types, column meanings, and the “OTHERS” account placeholder.
• HZ_PARTIES and XLE_FIRSTPARTY_INFORMATION_V — resolve party names and legal entity names for org/party identification.
• GL_PERIODS and GL_PERIOD_TYPES — documented references used for period-based column derivation.

The joins are largely outer joins (noted by the (+) operator) against bank accounts, org/legal entity, and party, so forecast cells without a matching bank account or party still appear, with “OTHERS” substituted for missing account information. This design ensures that consolidated or unassigned forecasts are not dropped from reporting.

Key Columns

• FORECAST_ROW_ID, ROW_NUMBER, TRX_TYPE, DESCRIPTION — identify the forecast row and its transaction type (for example API, APX, PAY, POP, POR).
• FORECAST_ID, FORECAST_HEADER_ID, NAME (header), FORECAST_CURRENCY, FACTOR — tie the cell to its parent forecast and header.
• BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, CURRENCY_CODE — account context; an “OTHERS” indicator column flags cells with no specific account.
• AMOUNT, TRX_AMOUNT, TRX_DATE, REFERENCE_ID, ORG_ID — the quantitative and transactional detail of each forecast cell.
• MEANING columns (from repeated CE_LOOKUPS joins) — decoded, user-facing labels for lookup-coded values such as transaction type.
• DEVELOPER_COLUMN_NUM and derived date labels — render the forecast column as a single date or an aggregated date range using START_DATE plus DAYS_FROM/DAYS_TO offsets.
• LEGAL_ENTITY / PARTY_NAME (from XLE and HZ_PARTIES) — organizational ownership of the forecast amount.

Common Use Cases and Queries

Typical uses include cash forecast reporting, liquidity analysis, and reconciliation of forecast amounts by bank account, legal entity, or transaction type. Analysts frequently filter by forecast header or currency and aggregate amounts across dated columns.

Sample query aggregating forecast amounts by bank account within a header:

• SELECT bank_account_name, currency_code, SUM(amount) amt FROM apps.ce_fc_amts_disc_v WHERE forecast_header_id = :p_header AND trx_date BETWEEN :p_from AND :p_to GROUP BY bank_account_name, currency_code ORDER BY amt DESC;

A second common pattern lists row-level detail for a single forecast, decoded to business meanings:

• SELECT row_number, description, bank_account_num, party_name, trx_amount FROM apps.ce_fc_amts_disc_v WHERE forecast_id = :p_forecast ORDER BY row_number, trx_date;

Because the view applies outer joins and “OTHERS” placeholders, queries should account for rows where bank_account_id is null when reconciling totals.