Search Results top_model_item_fk




Overview
Explore in AI Chat

Overview

APPS.ISCBV_BACKLOGS_FCV is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment that presents an aggregated, fact-style ("_FCV" denoting a fact collection view) picture of order backlog information. The view consolidates backlog metrics across multiple summary grains — bill backlog, ship backlog, and delivery/quote (DLQT) backlog — by grouping on a common set of foreign keys and reference identifiers. Each row returned by the view represents a unique combination of those grouping keys, with monetary and quantity measures aggregated through SUM() and the latest update timestamp captured through MAX().

This object is principally used for analytical and reporting purposes, feeding business intelligence extracts, Discoverer worksheets, OBIEE/DAC-based ETL, or custom concurrent programs that need a denormalized, pre-aggregated backlog dataset rather than querying transactional On-Hand/Shipping/Order Management tables directly. Because the view exposes both transactional and reporting-side identifiers (SEQ_ID, BACKLOGS_PK, INSTance), it serves as a bridge between the raw backlog data model and reporting layers.

Underlying Base Objects

The ETRM metadata for this object does not enumerate any explicitly documented base tables or referenced objects ("Referenced base objects: none documented"). The SELECT list, however, strongly indicates that the view is defined over one or more backlog fact tables (likely partitioned or aggregated tables containing columns such as BILL_BKLG_MRG_T, SHIP_BKLG_COST_G, QTY_UNBILL_SHIP_B, and similar measures). These are joined or grouped together with reference/master data representing customers, locations, items, currencies, operating units, and other dimensions exposed through the various _FK columns.

The presence of a SURROGATE key such as BACKLOGS_PK alongside SEQ_ID, INSTANCE, and USER_ATTRIBUTE1 through USER_ATTRIBUTE23 (a truncated list at USER_ATTRIB) suggests the underlying storage follows a multi-instance, user-extensible fact pattern common in Oracle Business Intelligence Applications (OBIA) and EBS CRM/Order Management analytical schemas. Because the metadata does not document the base objects, technical users should query USER_DEPENDENCIES or ALL_VIEWS to confirm the exact underlying tables in their specific release.

Key Columns

The view's columns fall into three broad categories.

BASE_UOM_FK, the column matching the user's search, is the foreign key to the base unit of measure dimension. It determines the UOM context for the quantity measures and is a critical grouping key when comparing backlog quantities across items with differing primary units.

Common Use Cases and Queries

Typical scenarios include backlog analysis by customer, operating unit, or sales channel; order-book reporting comparing billed versus shipped versus unbilled backlog; and feeds into OBIA/ETL pipelines. A representative query filtered by base UOM might be:

  • SELECT BASE_UOM_FK, OPERATING_UNIT_FK, SUM(BILL_BKLG_REV_G) bill_rev_g, SUM(SHIP_BKLG_REV_G) ship_rev_g, SUM(QTY_BILL_BKLG_B) qty_bill FROM APPS.ISCBV_BACKLOGS_FCV GROUP BY BASE_UOM_FK, OPERATING_UNIT_FK ORDER BY bill_rev_g DESC;
  • SELECT CUSTOMER_FK, TRX_CURRENCY_FK, SUM(BILL_BKLG_MRG_T) mrg_t, SUM(UNBILL_SHIP_MRG_T) unbill_mrg_t FROM APPS.ISCBV_BACKLOGS_FCV GROUP BY CUSTOMER_FK, TRX_CURRENCY_FK;
  • SELECT BASe_UOM_FK, MAX(LAST_UPDATE_DATE) last_upd FROM APPS.ISCBV_BACKLOGS_FCV GROUP BY BASE_UOM_FK;

When performance is a concern, filter on indexed dimensions (OPERATING_UNIT_FK, INV_ORG_FK, ITEM_ORG_FK) and constrain LAST_UPDATE_DATE. Because BASE_UOM_FK participates in the GROUP BY, queries that directly reference it should expect one row per UOM per remaining key combination.