Search Results dlx_item_id

Overview

APPS.IC_ITEM_LOCT_VW is a public view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its FND design data reference is GMF.IC_ITEM_LOCT_VW, which identifies it as an artifact of the Oracle Process Manufacturing (OPM/GMF) product family. The view presents a combined item, location, and lot perspective: it joins item master attributes to location definitions and lot master records, which is the classic Inventory-style construct used by OPM's lot-driven inventory and financials reporting.

The most significant documented fact about this view is that every column listed in the ETRM metadata is flagged OBSOLETE, and the header comment states: "OBSOLETE: Used in Financials for Lots." The object remains VALID in the data dictionary, but it is retained only for backward compatibility, most likely to support internal OPM Financials routines or legacy customizations that still reference it. Oracle does not recommend building new reports or integrations against it. Where equivalent item, location, and lot information is required for new development, the standard Inventory tables and public views (such as MTL_SYSTEM_ITEMS_VL, MTL_ITEM_LOCATIONS, and MTL_LOT_NUMBERS) in the Oracle Inventory schema should be used instead.

Underlying Base Objects

The view is defined over the following documented objects:

• IC_ITEM_MST (SYNONYM) — the OPM item master, supplying item-level attributes such as item number, dual UOM indicator, and primary/secondary units of measure.
• IC_LOCT_MST (SYNONYM) — the OPM location master, supplying location and warehouse codes.
• IC_LOTS_MST (SYNONYM) — the OPM lot master, supplying lot, sublot, grade, and lot status information.
• MTL_SYSTEM_ITEMS (SYNONYM) — the Oracle Inventory item definition table, providing ORA_ITEM_ID (the Oracle Inventory item identifier) alongside the OPM DLX_ITEM_ID.
• FND_PROFILE (PACKAGE) — the standard EBS profile option API, referenced in the view's source, typically to derive the current organization (ORG_ID) or similar context for the query.

The view is not referenced by any other database object, confirming that its role is purely as a query surface for external consumers rather than part of an internal dependency chain.

Key Columns

The view exposes fifteen columns, all documented as obsolete:

• ORA_ITEM_ID (NUMBER) — the Oracle Inventory / MTL item identifier, used to relate the row to standard Inventory item records.
• DLX_ITEM_ID (NUMBER(10)) — the legacy OPM/Process item identifier, the key searched most often when tracing this view. For new work, ORA_ITEM_ID or the OPM IC_ITEM_MST.ITEM_ID should be preferred.
• ITEM_NO and LOC_CODE — the item number and location code, the two most natural join keys for a lot-by-location listing.
• DUALUM_IND, PRIMARY_UOM, SECONDARY_UOM — dual unit of measure indicator and the associated primary and secondary UOMs.
• LOCATION, WHSE_CODE, WHSE_ITEM_ID — location detail and the warehouse-level item identifier.
• LOT_ID, LOT_NO, SUBLOT_NO, QC_GRADE, LOT_STATUS — full lot identification and quality-grade information.

Common Use Cases and Queries

Because the view is obsolete, its practical uses are limited to debugging legacy OPM Financials behavior and supporting pre-existing custom reports. A typical query is:

SELECT ORA_ITEM_ID
     , DLX_ITEM_ID
     , ITEM_NO
     , LOC_CODE
     , LOT_NO
     , SUBLOT_NO
     , QC_GRADE
     , LOT_STATUS
  FROM APPS.IC_ITEM_LOCT_VW
 WHERE ITEM_NO = :p_item
   AND LOC_CODE = :p_location;

A common pattern is a join to MTL_SYSTEM_ITEMS to translate the legacy DLX_ITEM_ID into a modern inventory item:

SELECT v.DLX_ITEM_ID
     , v.ITEM_NO
     , v.LOT_NO
     , msi.SEGMENT1
     , msi.DESCRIPTION
  FROM APPS.IC_ITEM_LOCT_VW v
     , APPS.MTL_SYSTEM_ITEMS  msi
 WHERE msi.ORGANIZATION_ID = :org_id
   AND msi.INVENTORY_ITEM_ID = v.ORA_ITEM_ID;

Relevant use cases include reconciling legacy lot balances against OPM lot records, tracing an obsolete DLX_ITEM_ID reference during a migration or upgrade, and auditing lot status or QC grade at a specific location. Any new development should be directed to the standard Inventory and OPM base tables rather than this view.