Results for “edw_items_m”

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

Overview

ISC_EDW_BACKLOG_S is an APPS-owned, VALID database view within the ISC – Supply Chain Intelligence product module of Oracle E-Business Suite. It is designed to serve as the semantic-layer source for Backlog reports, exposing pre-aggregated backlog metrics joined to conformed dimensional keys from the Supply Chain Intelligence (EDW) star schema. The view presents a denormalized, report-ready projection of the ISC_EDW_BACKLOGS_F fact table, enriched with foreign key surrogates drawn from the geography, item, organization, and time dimension tables. Because it is a view rather than a materialized object, consumers always see a current representation of the underlying EDW fact and dimension data at query time.

The object is available in both Oracle EBS 12.1.1 and 12.2.2 environments, though the online documentation referenced for 12.2.2 does not list any base objects explicitly, meaning the definitive source of truth remains the view text itself as recorded in ETRM.

Underlying Base Objects

The view is defined over five EDW objects: the fact table ISC_EDW_BACKLOGS_F (aliased BACKLOG) and four dimension tables — EDW_GEOGRAPHY_M (GEO), EDW_ITEMS_M (ITEM), EDW_ORGANIZATION_M (ORG), and EDW_TIME_M (TIME). Joins are performed on surrogate primary key columns: ITEM.IREV_ITEM_REVISION_PK_KEY to BACKLOG.TOP_MODEL_ITEM_FK_KEY, ORG.ORGA_ORGANIZATION_PK_KEY to BACKLOG.INV_ORG_FK_KEY, GEO.GLOC_LOCATION_PK_KEY to BACKLOG.SHIP_TO_LOCATION_FK_KEY, and TIME.CDAY_CAL_DAY_PK_KEY to BACKLOG.DATE_BALANCE_FK_KEY. The resulting row set combines dimensional context with backlog monetary measures.

Key Columns

• AREA_FK, COUNTRY_FK, REGION_FK — Geography surrogates from EDW_GEOGRAPHY_M, enabling geographic slicing of backlog.
• BUS_GRP_FK, LEGAL_ENT_FK, OPER_UNIT_FK, INT_ORGA_FK — Organizational surrogates from EDW_ORGANIZATION_M; INT_ORGA_FK resolves to the inventory organization.
• CATG_FK — Item category surrogate from EDW_ITEMS_M.
• DAY_FK — Calendar day surrogate from EDW_TIME_M.
• ORDER_SOURCE_FK, ORDER_TYPE_FK, SALES_CHANNEL_FK — Descriptive keys carried directly from the fact table (BACKLOG.SALES_CHANNEL_FK_KEY SALES_CHANNEL_FK); this is the column matched by the user search term "sales_channel_fk".
• BILLING_COST, BILLING_MARGIN, BILLING_REVENUE — Billed backlog amounts.
• DELINQUENT_COST, DELINQUENT_MARGIN, DELINQUENT_REVENUE — Delinquent backlog amounts.
• SHIPPING_COST, SHIPPING_MARGIN, SHIPPING_REVENUE — Shipped backlog amounts.
• UNBILL_COST, UNBILL_MARGIN, UNBILL_REVENUE — Unbilled shipment amounts.

Common Use Cases and Queries

Typical usage involves joining SALES_CHANNEL_FK to a sales channel dimension through a higher-level EDW view, or filtering directly for channel-based backlog analysis. A minimal projection follows:

• SELECT SALES_CHANNEL_FK, SUM(BILLING_REVENUE), SUM(UNBILL_REVENUE) FROM APPS.ISC_EDW_BACKLOG_S GROUP BY SALES_CHANNEL_FK;
• SELECT DAY_FK, OPER_UNIT_FK, SALES_CHANNEL_FK, DELINQUENT_REVENUE FROM APPS.ISC_EDW_BACKLOG_S WHERE DAY_FK = :p_day;

These patterns support channel profitability, backlog aging, and revenue-recognition reporting aligned to the ISC EDW dimensional model.