Results for “eni_dbi_inv_base_mv”

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

Overview

ENI_DBI_INV_BASE_MV is a materialized view owned by the APPS schema within the ENI – Product Intelligence product family in Oracle E-Business Suite. In Release 12.1.1 it is documented as a physical table with 37 columns, materialized for the Daily Business Intelligence (DBI) inventory subject area. It consolidates inventory valuation, in-transit, and work-in-process (WIP) balances into a pre-aggregated, time-bucketed fact structure used by Oracle Inventory and Product Intelligence dashboards.

Under a heuristic Data Vault classification mined from the foreign key structure, the object is modeled as standalone. This reflects that the table contains no outbound foreign keys other than the surrogate YEAR_ID reference to JAI_FA_AST_YEARS, and therefore behaves as a self-contained reporting aggregate rather than a strict hub, link, or satellite. The suggested modeling interpretation is that this is a reporting/temporal snapshot aggregate, not a normalized Data Vault construct.

Key Information Stored

The most significant columns fall into three logical groups:

• Inventory dimension keys: ORGANIZATION_ID, INVENTORY_ITEM_ID, ITEM_ORG_ID, ITEM_MASTER_ORG_ID, ITEM_CATEGORY_ID — the item and organization context for each row.
• Time dimension keys: TIME_ID, YEAR_ID, QTR_ID, MONTH_ID, WEEK_ID, DAY_ID, and grouping attribute GRP_ID — provide calendar roll-ups used by DBI dashboards.
• Valuation measures: ONHAND_VALUE_G, INTRANSIT_VALUE_G, WIP_VALUE_G, INV_TOTAL_VALUE_G (with matching _B and _SG variants) and their companion count columns — COUNT_OVG, COUNT_IVG, COUNT_WVG, COUNT_I_T_V_G, and equivalents — representing value and count facts in multiple ledger/currency bases.
• Consolidated total: COUNT_TOTAL aggregates the underlying item/count measure.

Two unique structures are documented. The business-key candidate ENI_DBI_INV_BASE_MV_U1 covers (TIME_ID, ITEM_MASTER_ORG_ID, ITEM_ORG_ID, ITEM_CATEGORY_ID), and I_SNAP$_ENI_DBI_INV_BASE_M covers a larger set of dimensions including ORGANIZATION_ID, INVENTORY_ITEM_ID, YEAR_ID, QTR_ID, MONTH_ID, WEEK_ID, DAY_ID, and GRP_ID. The documented foreign key to JAI_FA_AST_YEARS is via YEAR_ID.

Common Use Cases and Queries

The most frequent use is inventory valuation reporting — on-hand, in-transit, and WIP values trended across time and rolled up by organization, item, or category. Typical SQL patterns join the materialized view to dimensional masters:

• Trend analysis: select MONTH_ID, sum(ONHAND_VALUE_G), sum(INV_TOTAL_VALUE_G) group by MONTH_ID for a given ORGANIZATION_ID.
• Category roll-up: filter by ITEM_CATEGORY_ID and aggregate by ITEM_MASTER_ORG_ID.
• Period comparison: partition by YEAR_ID to compare on-hand versus in-transit valuation.
• Dashboard drill-downs: use GRP_ID to pivot by DBI grouping sets.

Because the object is a materialized view, refreshes are scheduled to keep the DBI subject area current; queries should account for refresh lag in near real-time reporting.

Related Objects

• JAI_FA_AST_YEARS — referenced by ENI_DBI_INV_BASE_MV.YEAR_ID via the documented foreign key.
• MTL_SYSTEM_ITEMS_B — item master joined on INVENTORY_ITEM_ID.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — organization context for ORGANIZATION_ID.
• MTL_ITEM_CATEGORIES / MTL_CATEGORIES_B — category context for ITEM_CATEGORY_ID.
• FND_CALENDAR / time dimension tables — resolve TIME_ID, MONTH_ID, QTR_ID, YEAR_ID.
• ENI_DBI_* sibling materialized views — shared DBI fact/dimension model.

Because ENI-specific source tables are proprietary, integration is generally performed through the DBI subject area rather than direct DML against this object.