Results for “item_um2”

50+ results




Overview
Explore in AI Chat

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

Overview

IC_LOCT_INV_RPTVW1 is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMI (Process Manufacturing Inventory) product family. The view is documented in ETRM as the "Lot inventory report view," and its purpose is to consolidate lot-level on-hand inventory into a single, query-friendly projection that combines item, lot, warehouse, and location attributes. In both 12.1.1 and 12.2.2 the object is reported as VALID, indicating the definition compiles cleanly against the base synonyms in the instance.

The view serves as a denormalized read layer over the core inventory master and transaction tables. Rather than requiring report developers or integration endpoints to join four base tables manually, IC_LOCT_INV_RPTVW1 exposes item number, description, primary and secondary unit of measure, lot and sublot identifiers, warehouse details, expiry information, and aggregated on-hand quantities. Because it aggregates quantities and applies a HAVING filter, it is intended strictly for read-only reporting and inquiry, not for transactional processing.

Underlying Base Objects

The view is defined over four documented base objects referenced through synonyms in the APPS schema:

Joins are established on ITEM_ID between IC_ITEM_MST, IC_LOTS_MST, and IC_LOCT_INV; on LOT_ID between IC_LOTS_MST and IC_LOCT_INV; and on WHSE_CODE between IC_LOCT_INV and IC_WHSE_MST. The result set is grouped by warehouse code, item number, lot number, sublot number, warehouse name, item description, both unit-of-measure columns, lot creation date, expiry date, location, and the item delete flag.

Key Columns

  • WHSE_CODE / WHSE_NAME — warehouse identifier and its descriptive name.
  • ITEM_NO / ITEM_DESC1 — item identifier and description.
  • ITEM_UM — primary unit of measure for the item, used to interpret LOCT_QTY1.
  • ITEM_UM2 — secondary unit of measure, the column referenced in the user's search. It is the UOM corresponding to LOCT_QTY2 and is essential when dual UOM tracking is enabled in GMI.
  • LOT_NO / SUBLOT_NO — lot and sublot identifiers for the balance.
  • LOT_CREATED / EXPIRE_DATE — lot creation and expiry dates, supporting shelf-life analysis.
  • LOCATION — the storage location within the warehouse.
  • LOCT_QTY1 / LOCT_QTY2 — aggregated on-hand quantity in the primary and secondary UOM respectively, produced by SUM(INV.LOCT_ONHAND) and SUM(INV.LOCT_ONHAND2).
  • DELETE_MARK — item deletion indicator, useful for filtering obsolete items.

Common Use Cases and Queries

Typical usage includes lot on-hand reporting, expiry and shelf-life review, and reconciliation of dual-UOM balances. Because ITEM_UM2 is exposed directly, reports that present secondary quantities alongside primary quantities can source both the value and its UOM from the same view.

Sample query listing positive on-hand lot balances with their primary and secondary UOMs:

  • SELECT WHSE_CODE, WHSE_NAME, ITEM_NO, ITEM_DESC1, ITEM_UM, ITEM_UM2, LOT_NO, SUBLOT_NO, LOCATION, LOCT_QTY1, LOCT_QTY2 FROM APPS.IC_LOCT_INV_RPTVW1 WHERE DELETE_MARK = 0 AND LOCT_QTY2 > 0;

Sample query identifying lots nearing expiry for a given warehouse:

  • SELECT ITEM_NO, LOT_NO, EXPIRE_DATE, LOCT_QTY1, ITEM_UM FROM APPS.IC_LOCT_INV_RPTVW1 WHERE WHSE_CODE = :p_whse AND EXPIRE_DATE BETWEEN SYSDATE AND SYSDATE + 30 ORDER BY EXPIRE_DATE;

Because the view already aggregates and filters out zero-balance rows, queries against it are efficient for balance-driven reporting; however, heavy analytical workloads should account for the GROUP BY and HAVING processing performed internally.