Search Results forecast_trx_type




Overview
Explore in AI Chat

Overview

APPS.CE_FC_AMTS_DISC_V is a reporting view in the Oracle E-Business Suite Cash Management module that presents cash forecast transaction amounts in a fully decoded, presentation-ready form. The object belongs to the APPS schema and is available in both EBS 12.1.1 and 12.2.2. Its name reflects its purpose: a forecast (FC) amounts view that resolves internal identifiers and lookup codes into discrete, human-readable values.

Cash forecasting in Oracle Cash Management stores amounts across a normalised structure of headers, forecasts, rows, columns, and transaction cells. The base tables are efficient for storage but unsuitable for direct reporting, because many descriptive attributes are held as lookup codes and several dimensions are resolved through joins. CE_FC_AMTS_DISC_V bridges that gap. It flattens the forecast grid into a single row per transaction cell and substitutes lookup meanings for codes, bank account details for account identifiers, party and legal entity names for internal identifiers, and calculated column date ranges for developer column numbers. The view therefore serves as the principal data source for forecast worksheets, ad hoc reporting, and downstream integrations that need a readable forecast spread.

Underlying Base Objects

The view is defined over eleven documented objects. The core forecast objects are CE_FORECASTS, CE_FORECAST_HEADERS, CE_FORECAST_ROWS, CE_FORECAST_COLUMNS, and CE_FORECAST_TRX_CELLS. The transaction cell is the fact record; the row defines the transaction type and description; the column defines the time bucket; the forecast and forecast header provide the name, currency, factor, and start date of the forecast definition.

Supporting objects supply descriptive context. CE_BANK_ACCOUNTS is joined with an outer join on BANK_ACCOUNT_ID to resolve account name, account number, and currency, falling back to an "Others" flag when no account exists. XLE_FIRSTPARTY_INFORMATION_V and HZ_PARTIES are likewise outer-joined on ORG_ID to resolve legal entity and party names. CE_LOOKUPS appears seven times (aliases L through L7), each pinned to a specific lookup type and code such as FC_MISC to decode bank account type, bank, currency, transaction source, and similar attributes. GL_PERIODS and GL_PERIOD_TYPES are referenced for period context.

Key Columns

  • FORECAST_ROW_ID and FORECAST_COLUMN_ID — the intersection keys identifying the row and time bucket of each cell.
  • ROW_NUMBER and TRX_TYPE — the sequence and transaction type of the forecast row; TRX_TYPE is decoded through a nested DECODE that maps codes such as API, APP, APX, OIO, PAY, POP, POR, PAT, PAO, UDO, and XTO to their lookup meanings.
  • BANK_ACCOUNT_NAME and BANK_ACCOUNT_NUM — resolved from CE_BANK_ACCOUNTS, with "Others" and an indicator flag of 1 when no account is linked.
  • AMOUNT, TRX_AMOUNT, and CURRENCY_CODE — the forecast amount, the source transaction amount, and the currency of the cell.
  • TRX_DATE and REFERENCE_ID — the transaction date and the reference to the originating source document.
  • ORG_ID and the derived legal entity and party name columns — the owning organisation context.
  • FORECAST_CURRENCY and FACTOR — the currency and conversion factor of the forecast definition.
  • DEVELOPER_COLUMN_NUM and the calculated date range — a DECODE produces either the translated column meaning (for column zero) or a formatted date range derived from START_DATE plus DAYS_FROM and DAYS_TO.

Common Use Cases and Queries

Typical use is to report forecast amounts by bank account, currency, and period bucket. The view removes the need to write the lookup and account joins manually.

SELECT forecast_row_id, row_number, trx_type,
       bank_account_name, amount, currency_code,
       trx_date, name AS forecast_name
FROM   apps.ce_fc_amts_disc_v
WHERE  forecast_id = :p_forecast_id
ORDER  BY row_number, forecast_column_id;

A second pattern aggregates exposure by bank account for a given forecast:

SELECT bank_account_name, currency_code,
       SUM(NVL(amount,0)) total_amount
FROM   apps.ce_fc_amts_disc_v
WHERE  forecast_id = :p_forecast_id
GROUP  BY bank_account_name, currency_code;

Because the view exposes ORG_ID and legal entity names, it is also used for multi-organisation forecast reporting and for reconciliation against GL_PERIODS when forecast buckets must align to accounting periods. Integrations commonly select from the view to populate external liquidity dashboards, keying on FORECAST_ID plus ROW_NUMBER and FORECAST_COLUMN_ID to reconstruct the forecast grid.