Results for “ce_fc_bank_netflow_v”

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

Overview

CE_FC_BANK_NETFLOW_V is a custom reporting view owned by the APPS schema in Oracle Cash Management (CE). It was created to track cash inflow per forecast period, aggregated by bank account, within the Cash Forecasting module. Unlike the standard forecast tables, which store data at cell granularity, this view pivots the cell-level amounts across the developer-defined forecast columns (column numbers 0 through 17) into discrete, period-oriented numeric columns. Because it collates inflow values for each bank account against each forecast period, the view is well suited for liquidity reporting, treasury dashboards, and bank-level cash positioning analysis.

In EBS 12.1.1 and 12.2.2 the object is registered as VALID, and its dependency list includes several FND and MO security packages, confirming that the view applies Oracle multi-org and data-access security filters at runtime. It is intended for query access rather than as a transactional object.

Underlying Base Objects

The view is defined over the following documented synonyms and objects:

• CE_FORECAST_TRX_CELLS (synonym) — supplies FCELL columns such as FORECAST_ID, BANK_ACCOUNT_ID, INCLUDE_FLAG, and AMOUNT; this is the primary source of forecast amounts.
• CE_FORECAST_COLUMNS (synonym) — supplies FCOL.DEVELOPER_COLUMN_NUM, which is decoded to route each cell amount into the correct period column.
• CE_FORECAST_ROWS (synonym) — joined to associate rows within a forecast with their columns and cells.
• CE_SECURITY_PROFILES_V (view) — applies bank account security so that users see only authorized accounts.
• FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE — resolve the current user, responsibility, and profile options governing access control.
• MO_GLOBAL — enforces multi-org (operating unit) security.
• XTR_USER_ACCESS — applies treasury access restrictions to restrict forecast data by user.

Key Columns

• FORECAST_ID — identifies the forecast to which the netflow values belong.
• Bank account key — NVL(FCELL.BANK_ACCOUNT_ID, -999); the literal -999 denotes cells not tied to a specific bank account. This column is the grouping key that makes the view a per-bank-account aggregation.
• Period columns (18 in total) — one aggregate per DEVELOPER_COLUMN_NUM from 0 to 17. Each is computed as SUM(DECODE(FCOL.DEVELOPER_COLUMN_NUM, n, DECODE(FCELL.INCLUDE_FLAG,'N',0,FCELL.AMOUNT),0)), meaning amounts flagged as excluded (INCLUDE_FLAG = 'N') contribute zero.
• INCLUDE_FLAG — source flag from CE_FORECAST_TRX_CELLS used to suppress excluded cells from the netflow totals.

Common Use Cases and Queries

Typical uses include retrieving projected inflows per bank account for a forecast, comparing periods side by side, and feeding treasury dashboards. The view is also useful for validating that cells excluded from forecasts are not inflating totals.

• Cash positioning by bank account across all periods.
• Period-over-period inflow trend analysis for a single forecast.
• Security-aware reporting embedded in custom OAF or concurrent programs.

Sample query:

SELECT FORECAST_ID, BANK_ACCOUNT_ID, COL0, COL1, COL2, COL3
FROM APPS.CE_FC_BANK_NETFLOW_V
WHERE FORECAST_ID = :p_forecast_id
ORDER BY BANK_ACCOUNT_ID;

Because access-dependent packages participate in the definition, the returned rows are automatically filtered according to the querying user's bank account, treasury, and operating unit privileges, making the view safe for direct use in user-facing reports.