Results for “summ_inv_id”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IC_SUMM_INV_V is a reporting view owned by the APPS schema within the GMI (Process Manufacturing Inventory) product family of Oracle E-Business Suite. As its description states, it is a "GMI summary inventory view" — it consolidates inventory quantities across the GMI inventory staging structures and exposes a single aggregated row per item, warehouse, and quality grade combination. The view is defined in Oracle EBS 12.1.1 and 12.2.2 with a status of VALID.
The view functions as a reporting and integration layer. Because it groups records and applies fixed aggregation rules (including sign inversions on committed quantities), it shields downstream consumers — custom reports, concurrent programs, and interfaces — from the granularity and volatility of the underlying staging table. Its principal role is to present summarized on-hand, on-order, in-transit, and committed inventory positions in a form suitable for inventory dashboards, availability checks, and reconciliation reporting.
Underlying Base Objects
According to the documented view metadata, IC_SUMM_INV_V is defined exclusively over a single referenced base object: IC_SUMM_INV_INT_V, itself a view. The view text performs a GROUP BY over ITEM_ID, WHSE_CODE, and QC_GRADE, applying SUM() to each quantity column. This means IC_SUMM_INV_INT_V is the intermediate or interface view that holds ungrouped inventory lines, and IC_SUMM_INV_V is the summary (aggregated) presentation of that data.
Because the reference is to another view rather than a base table, the true physical source tables sit beneath IC_SUMM_INV_INT_V in the GMI schema. The aggregation pattern indicates the interface view likely unions or consolidates multiple GMI inventory sub-ledger sources. The naming convention ("_INT_" for interface, "_SUMM_" for summary) reinforces that IC_SUMM_INV_INT_V collects and IC_SUMM_INV_V summarizes.
Key Columns
The view exposes the grouping keys ITEM_ID, WHSE_CODE, and QC_GRADE, plus the aggregated quantities below. Each primary quantity is paired with a secondary quantity (the "QTY2" suffix), reflecting dual-unit-of-measure handling in process manufacturing.
- ONHAND_QTY / ONHAND_QTY2 — Total on-hand inventory quantity in primary and secondary UOM. This is the figure most commonly queried when users search for on-hand balances.
- ONHAND_PROD_QTY / ONHAND_PROD_QTY2 — On-hand quantity attributable to production or in-process stock.
- ONHAND_ORDER_QTY / ONHAND_ORDER_QTY2 — On-hand quantity reserved or associated with orders.
- ONHAND_SHIP_QTY / ONHAND_SHIP_QTY2 — On-hand quantity allocated for shipment. This is the column directly relevant to the search term "onhand_ship_qty."
- ONPURCH_QTY / ONPROD_QTY (and QTY2 variants) — Incoming quantity on purchase orders and on production orders respectively.
- COMMITTEDSALES_QTY, COMMITTEDPROD_QTY (and QTY2 variants) — Committed quantities, multiplied by −1 in the view so that commitments are presented as negative values, reducing available balance rather than adding to it.
- INTRANSIT_QTY / INTRANSIT_QTY2 — Stock in transit between locations.
- Audit and system columns including SUMM_INV_ID, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_DATE, CREATION_DATE, PROGRAM_ID, and REQUEST_ID.
Common Use Cases and Queries
The most frequent use case is querying current on-hand and shipment-allocated stock for a given item and warehouse. For example, to retrieve ship-allocated quantity:
SELECT ITEM_ID, WHSE_CODE, QC_GRADE, ONHAND_QTY, ONHAND_SHIP_QTY FROM APPS.IC_SUMM_INV_V WHERE ITEM_ID = :item_id AND WHSE_CODE = :whse_code;
Variations join to inventory item and warehouse master tables to translate ITEM_ID and WHSE_CODE into descriptive names, and to combine on-hand, on-order, and in-transit columns into a projected available-to-promise calculation. Because committed quantities are already sign-inverted in the view definition, reports can sum all columns directly without adjusting for commitments.
Given the presence of QC_GRADE, the view also supports quality-grade-level inventory reporting, useful where material is segregated by grade or status. Developers building GMI interfaces should treat IC_SUMM_INV_V as a read-only aggregation layer over IC_SUMM_INV_INT_V and avoid expecting row-level transaction detail from it.
-
View: IC_SUMM_INV_V 12.1.1
GMI summary inventory view
-
View: IC_SUMM_INV_V 12.2.2
GMI summary inventory view
-
VIEW: GMI.IC_SUMM_INV_BAK# 12.2.2
-
VIEW: GMI.IC_SUMM_INV_BAK# 12.2.2
-
TABLE: GMI.IC_SUMM_INV_BAK 12.1.1
-
Table: IC_SUMM_INV 12.2.2
Inventory summary table. This table contains inventory summary balances by item/warehouse/grade.
Not implemented in this database·Explore GMI module →
-
TABLE: GMI.IC_SUMM_INV_BAK 12.2.2
-
Table: IC_SUMM_INV 12.1.1
Inventory summary table. This table contains inventory summary balances by item/warehouse/grade.
Not implemented in this database·Explore GMI module →
-
VIEW: APPS.IC_SUMM_INV_V 12.1.1
-
VIEW: APPS.IC_SUMM_INV_V 12.2.2
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.