Search Results ship_to_cust_fk




Overview
Explore in AI Chat

Overview

ISCBV_BACKLOGS_FCV is an Oracle E-Business Suite view owned by the APPS schema and classified under the ISC (Supply Chain Intelligence) product family. It is a wrapper view constructed around the base view that supports the Backlog Snapshot fact table within the Supply Chain Intelligence reporting schema. As a wrapper, its primary purpose is to present a denormalized, aggregated, and consistently named projection of the underlying backlog fact data so that downstream Oracle Business Intelligence (OBIEE) repository metadata, Discoverer workbooks, and custom reports can query a stable interface rather than the base fact structure directly.

Because the object is a view and not a table, it stores no data of its own. All values are derived at query time from the base backlog fact table (documented internally as the Backlog Snapshot fact), which is populated during the Supply Chain Intelligence collection and fact-build process. The naming convention — the ISCBV prefix and FCV suffix — indicates an ISC business view intended for fact-level consumption. Its status is documented as VALID, meaning the compiled definition resolves successfully against the referenced objects in the 12.1.1 and 12.2.2 database releases.

Underlying Base Objects

The ETRM metadata identifies this view as a wrapper around the base view for the Backlog Snapshot fact table, but does not enumerate the specific base tables or the base view by name. In practice, the wrapper is defined over an underlying ISC backlog fact view (commonly named with a BASE or F suffix) which in turn reads the physical fact table loaded by the Supply Chain Intelligence fact build, typically stored in a dedicated ISC staging or fact schema.

The view definition performs an explicit GROUP BY over the full set of foreign key and dimension key columns — including BACKLOGS_PK, ITEM_ORG_FK, CUSTOMER_FK, DATE_BALANCE_FK, and the remaining FK columns — while aggregating the measure columns with SUM and retaining the maximum LAST_UPDATE_DATE. This confirms the wrapper is not a simple pass-through; it consolidates records from the base object to a single grain per dimensional key combination before exposing them.

Key Columns

Common Use Cases and Queries

Typical usage centres on backlog aging, order cycle analysis, and revenue/margin reporting where managers need backlog broken out by customer, item, organization, or sales channel. A representative query aggregates shipment backlog by item organization:

SELECT ITEM_ORG_FK, SUM(SHIP_BKLG_REV_G) total_ship_bklg_rev FROM APPS.ISCBV_BACKLOGS_FCV GROUP BY ITEM_ORG_FK;

A second common pattern filters to a specific customer or order category and compares transaction versus global currency measures to reconcile currency conversion results:

SELECT CUSTOMER_FK, SUM(BILL_BKLG_REV_T) bklg_rev_t, SUM(BILL_BKLG_REV_G) bklg_rev_g FROM APPS.ISCBV_BACKLOGS_FCV WHERE ORDER_CATEGORY_FK = :category GROUP BY CUSTOMER_FK;

Because the wrapper is already aggregated at the fact grain, joins to ISC dimension views (typically ISCBV_* dimension views joined on the *_FK columns) are straightforward and do not require additional GROUP BY clauses on the dimensional attributes. Reporting developers should note that data currency depends entirely on the last successful Supply Chain Intelligence fact build, so the MAX(LAST_UPDATE_DATE) column is a useful indicator of data freshness when validating report results.