Search Results ddr_sv_inv_mv




Overview
Explore in AI Chat

Overview

DDR_SV_INV_MV is a materialized view object registered in the APPS schema and catalogued under the FND – Application Object Library product within Oracle E-Business Suite 12.1.1 and 12.2.2. The name follows the DDR_SV_INV_MV convention, indicating a demand-driven or scheduled refresh snapshot (SV) that consolidates inventory (INV) measures for downstream reporting rather than supporting transactional entry. The object exposes 81 columns and is classified as a standalone object; it does not serve as the parent of any documented foreign key relationship and does not participate in a normalized operational hierarchy. From a Data Vault modeling perspective, the ETRM metadata yields a standalone classification rather than a hub, link, or satellite designation. This suggests the object functions as a reporting aggregate — effectively a snapshot store — and would typically be modeled as a point-in-time satellite or a derived fact structure rather than as an integration hub.

Key Information Stored

The table is organized around a conformed dimensional grain composed of business calendar, organization, and item attributes, with an extensive set of calculated quantity and valuation measures layered on top.

No hidden surrogate primary key is documented; the unique snapshot index is the closest structural analog and should be treated as the logical key for de-duplication and incremental loads.

Common Use Cases and Queries

Because the object is a pre-aggregated inventory snapshot, it is best consumed for trend, coverage, and valuation reporting rather than real-time inquiry. Typical usage includes week-over-week on-hand and in-transit valuation, backorder exposure by item class and organization chain, and inventory-days-of-supply analysis.

  • Trend reporting: group by BSNS_WK_ID and summarize ON_HAND_NET_COST_AMT compared against prior periods.
  • Hierarchy roll-up: filter on BSNS_CLNDR_DIM_LVL and ORG_DIM_LVL to control aggregation depth.
  • Exception analysis: compare UNDR_STCK_BU_ITM_DAYS against IN_STCK_BU_ITM_DAYS per ORGANIZATION and item class.
  • Grouping-scoped queries: join or filter on GROUPING_ID to retrieve a defined HR_DM_TABLE_GROUPINGS cohort.

A representative pattern selects BSNS_MNTH_ID, ORG_CHAIN_ID, MFG_ITEM_CLASS_ID, SUM(ON_HAND_QTY_PRMRY), and SUM(ON_HAND_RTL_AMT) from APPS.DDR_SV_INV_MV, filtered by BSNS_WK_ID and GROUPING_ID, grouped by the dimensional columns above.

Related Objects

The documented dependency set is narrow, reflecting the standalone classification.

  • HR_DM_TABLE_GROUPINGS — referenced through DDR_SV_INV_MV.GROUPING_ID, providing the grouping definition that scopes each snapshot cohort.
  • FND product tables — the object is catalogued under FND – Application Object Library, so metadata and concurrent-program refresh definitions for the underlying materialized view reside in FND objects.
  • Inventory valuation and item/organization dimensions — the measure and dimension columns imply logical joins to on-hand, receiving, and item-class sources; these are populated at refresh time rather than enforced by foreign keys.
  • Business calendar and organization hierarchies — referenced indirectly through BSNS_CLNDR_DIM_ID, ORG_DIM_ID, MFG_ITEM_DIM_ID, and RTL_ITEM_DIM_ID in downstream reporting views.

Administrators should confirm the refresh schedule and staleness tolerance for this snapshot before using it for period-close reporting, since values are only as current as the last materialized view refresh.