Search Results inventory




Overview
Explore in AI Chat

Overview

The IC_SUMM_INV table is a core data repository within the GMI (Process Manufacturing Inventory) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the inventory summary table, designed to store aggregated on-hand inventory balances. Its primary role is to maintain summarized quantities by the key dimensions of item, warehouse, and quality control (QC) grade. This summary-level data is critical for performance in inventory inquiries, reporting, and availability checks, providing a consolidated view of stock levels without needing to query granular transaction-level tables. The metadata indicates it is a standard table within the GMI product's data model, though the provided excerpt notes it was "Not implemented in this database" for the specific instance from which the documentation was extracted.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which dictate the granularity and integrity of the data it holds. The primary inventory balance is uniquely identified by the combination of ITEM_ID, WHSE_CODE, and QC_GRADE, as enforced by the IC_SUMM_INV_U1 unique key. A surrogate primary key, SUMM_INV_ID, is also present. The table's critical foreign key relationships reveal the specific data it stores: ITEM_ID references IC_ITEM_MST (the item master), WHSE_CODE references IC_WHSE_MST (the warehouse master), and QC_GRADE references QC_GRAD_MST (the quality grade master). While the metadata excerpt does not list the specific quantity columns, tables of this nature typically contain columns for on-hand, available, reserved, and in-transit quantities for the given item-warehouse-grade combination.

Common Use Cases and Queries

This table is central to inventory summary reporting and availability analysis. Common operational use cases include generating high-level stock status reports, checking material availability for production or sales orders, and reconciling summary balances with detailed transaction history. A typical query pattern would join IC_SUMM_INV to its referenced master tables to retrieve meaningful descriptions. For example:

  • Retrieving total on-hand quantity by item and warehouse: SELECT i.ITEM_NO, w.WHSE_CODE, s.QC_GRADE, s.ON_HAND FROM IC_SUMM_INV s JOIN IC_ITEM_MST i ON s.ITEM_ID = i.ITEM_ID JOIN IC_WHSE_MST w ON s.WHSE_CODE = w.WHSE_CODE WHERE i.ITEM_NO = '&ITEM';
  • Identifying inventory held under a specific quality grade for quality management purposes.
  • Serving as the primary data source for custom inventory dashboards or summary screens that require aggregated performance.

Related Objects

IC_SUMM_INV sits at the center of a network of related GMI tables, primarily defined by its foreign key constraints. The master tables it directly depends on are IC_ITEM_MST (items), IC_WHSE_MST (warehouses), and QC_GRAD_MST (quality grades). It is also referenced by the table itself through a self-referencing foreign key on ITEM_ID, the purpose of which would be detailed in a full data model. While not listed in the excerpt, this summary table is typically populated and maintained by inventory transaction processing logic (potentially in packages or from tables like IC_TRAN_PND) that post aggregated changes to the summary balances. Reports and forms displaying inventory summaries will directly query this table or related views built upon it.