Search Results upc_code

Overview

The IC_ITEM_MST_VL view is a Multi-Lingual Support (MLS) enabled view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMI (Process Manufacturing Inventory) product family and exposes the master data records that define items used within OPM (Oracle Process Manufacturing). The view presents a denormalized, translation-aware representation of process manufacturing items, combining the operational item attributes stored in the base item master with the translated descriptive text held in the corresponding translations table.

The "_VL" suffix indicates that the view is language-enabled: it joins the base table to its translation table so that a single query returns both the item attributes and the language-appropriate description columns. This makes the view the preferred access point for reporting and integration logic that must present item descriptions in the session or user language, rather than the base table which stores untranslated attributes only. The view carries a VALID status in the data dictionary, confirming that it compiles successfully against its referenced base objects.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through synonyms:

• IC_ITEM_MST_B — the base item master table. It supplies the majority of the columns, aliased as B in the view text. This includes the primary identifier ITEM_ID, the item number ITEM_NO, unit of measure columns, class and category identifiers, lot and status control flags, and the descriptive flexfield (DFF) ATTRIBUTE1 through ATTRIBUTE30 columns plus ATTRIBUTE_CATEGORY.
• IC_ITEM_MST_TL — the translation table, aliased as T. It contributes the language-dependent descriptive columns, specifically ITEM_DESC1 and ITEM_DESC2, which provide the translated item descriptions.

Because the view joins the base and translation tables, it preserves the relationship between a single item's operational attributes and its language-specific description rows, enabling consistent MLS-aware retrieval across the OPM item domain.

Key Columns

The view exposes a broad set of item attributes. Notable columns include:

• ROW_ID, ITEM_ID, ITEM_NO — the row identifier and the item's primary and alternate identifiers (ALT_ITEMA, ALT_ITEMB).
• ITEM_UM, ITEM_UM2, DUALUM_IND — primary and secondary units of measure and the dual-UOM indicator.
• LOT_CTL, SUBLOT_CTL, LOCT_CTL, STATUS_CTL, GRADE_CTL — control flags governing lot, sublot, location, status, and grade handling.
• SEQ_DPND_CLASS — the sequence-dependent class attribute (the term the user searched), which governs sequence-dependent processing behavior for the item.
• INV_TYPE, INACTIVE_IND, PHANTOM_TYPE — item type classification, active/inactive status, and phantom designation.
• SHELF_LIFE, RETEST_INTERVAL, EXPACTION_CODE, EXPACTION_INTERVAL — shelf-life and expiration action attributes.
• CLASS columns — GL_CLASS, INV_CLASS, SALES_CLASS, SHIP_CLASS, FRT_CLASS, PRICE_CLASS, and related class fields, plus their category ID counterparts.
• ITEM_DESC1, ITEM_DESC2 — translated item descriptions sourced from the TL table.
• AUDIT columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and the WHO-context columns.

Common Use Cases and Queries

The view is commonly used to drive OPM item validation, inventory reporting, and integration extracts that require translated descriptions. A typical query retrieves active items with their descriptions and control flags:

SELECT item_id, item_no, item_um, item_desc1,
       lot_ctl, seq_dpnd_class, inactive_ind
FROM   apps.ic_item_mst_vl
WHERE  inactive_ind = 'N'
AND    item_no LIKE 'FG%';

Because SEQ_DPND_CLASS governs sequence-dependent processing, a frequent reconciliation query filters items by that attribute:

SELECT item_no, item_desc1, seq_dpnd_class, planning_class
FROM   apps.ic_item_mst_vl
WHERE  seq_dpnd_class IS NOT NULL;

Integration and interface routines select from the view when populating downstream systems, since the MLS join guarantees description values consistent with the caller's language environment. The view also supports class-based reporting by joining the ITEM_NO and class columns against category and class lookup tables.