Search Results external_source_view

Overview

CE_FORECAST_EXT_VIEWS_V is a reporting view owned by the APPS schema within the Cash Management (CE) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The object is documented as "Retrofitted," a classification indicating it was introduced or reconciled to maintain backward compatibility with earlier EBS releases while preserving the surrounding Cash Management architecture. Its purpose is to expose configuration definitions that map external data sources to internal forecast logic used by the Cash Forecasting engine.

Rather than storing transactional cash forecast data, the view presents metadata about where forecast-relevant information originates. Each row describes an external source type, the database view that supplies the data, and an optional database link name for cross-instance access. This makes CE_FORECAST_EXT_VIEWS_V a control-plane object: it governs how Cash Management locates and consumes external cash positions, not the position values themselves. Because the view is defined over a synonym and exposes ROWID as ROW_ID, it is typically consumed by Oracle Forms-based setup screens, concurrent programs, and integration routines rather than by end-user ad hoc reporting.

Underlying Base Objects

The view is defined over a single documented base object: the synonym CE_FORECAST_EXT_VIEWS, which resolves to the underlying APPS table of the same name. The definition selects all rows from that source with no WHERE clause, filter, or join:

• CE_FORECAST_EXT_VIEWS (SYNONYM) — the sole referenced base object, resolving to the physical external-source configuration table in the APPS schema.

Because the mapping is a straight projection with an implicit ROWID alias, the view is effectively a thin, read-only presentation layer. It performs no aggregation and applies no row-level security beyond the standard APPS schema grants. Consequently, any change to the base table is immediately visible through the view, and the view cannot be used to persist updates unless an INSTEAD-OF trigger exists on the base object. The one-to-one column correspondence means the view carries essentially the same cardinality as the base table.

Key Columns

The columns exposed by CE_FORECAST_EXT_VIEWS_V fall into two groups: functional configuration attributes and standard EBS audit columns.

• ROW_ID — The ROWID of the underlying base row, used by Oracle Forms for row identification, optimistic locking, and navigational operations.
• EXTERNAL_SOURCE_TYPE — Classifies the external data source, allowing the forecast engine to distinguish among source categories (for example, differing source systems or integration patterns).
• EXTERNAL_SOURCE_VIEW — Names the database view that supplies the external cash data. This is the operative column for the "external_source_view" lookup, since it identifies precisely which object the forecasting process should query.
• DB_LINK_NAME — Specifies an optional database link used when the external source view resides in a remote database, enabling distributed forecast sourcing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking record creation and the most recent modification, including the login of the updating user.

Common Use Cases and Queries

Typical use cases include auditing external forecast source configuration, diagnosing forecast generation failures caused by an invalid or missing source view, and validating cross-database integration setups prior to running forecast concurrent programs.

List all configured external forecast sources:

• SELECT external_source_type, external_source_view, db_link_name FROM apps.ce_forecast_ext_views_v;

Identify remote sources requiring database link validation:

• SELECT external_source_view, db_link_name FROM apps.ce_forecast_ext_views_v WHERE db_link_name IS NOT NULL;

Retrieve audit history for recently modified configurations:

• SELECT row_id, external_source_type, last_updated_by, last_update_date FROM apps.ce_forecast_ext_views_v ORDER BY last_update_date DESC;

Because the view exposes ROW_ID, it also supports Forms-driven maintenance and row-level troubleshooting within the Cash Management setup responsibilities.