Results for “lot_suffix”

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

Overview

IC_ITEM_MST_B is the master item definition table within the Oracle Process Manufacturing Inventory module (GMI), and it operates as the foundational reference object for material identity across Oracle EBS 12.1.1 and 12.2.2. Every item that is transacted, costed, planned, purchased, sold, or quality-tested in a process manufacturing environment is registered here first. The table stores the complete attribute set that governs how an item behaves: its lot and sublot control rules, its unit of measure definitions, its class and type designations, and the numerous category and accounting classifications that downstream applications consume. Because items permeate nearly every process manufacturing sub-module — inventory, costing, quality, forecasting, order management, production, and purchasing — IC_ITEM_MST_B functions as a central hub from which a very large number of dependent transactions and detail records radiate.

From a data-modeling perspective, the structure of IC_ITEM_MST_B is best described heuristically as a Data Vault hub. Its identity is anchored by a single surrogate primary key, ITEM_ID, and the surrounding tables reference that key rather than replicating descriptive item attributes. In practice, this table is treated as the system of record for item master data, and any change to an item's control flags or classifications can ripple across the entire inventory and costing chain.

Key Information Stored

IC_ITEM_MST_B contains 119 documented columns. The most operationally significant are summarized below.

• ITEM_ID — the surrogate primary key defined by IC_ITEM_MST_B_PK. This is the value referenced by all foreign keys that point back to the item master.
• ITEM_NO — the user-facing item number and the business-key candidate, enforced by the unique index IC_ITEM_MST_B_UNQ1.
• ITEM_DESC1 / ITEM_DESC2 — the primary and secondary item descriptions used in reporting and screens.
• ITEM_UM, ITEM_UM2, DUALUM_IND, FILL_QTY, FILL_UM — unit of measure definitions, dual-UOM handling, and fill quantity parameters.
• LOT_CTL, SUBLOT_CTL, LOCT_CTL, LOT_INDIVISIBLE, AUTOLOT_ACTIVE_INDICATOR, LOT_PREFIX, LOT_SUFFIX, SUBLOT_PREFIX, SUBLOT_SUFFIX — the lot and sublot control configuration that determines traceability behavior.
• INV_TYPE, INACTIVE_IND, ITEMCOST_CLASS, COST_MTHD_CODE — inventory type, active/inactive status, and costing classification.
• INV_CLASS, GL_CLASS, SALES_CLASS, PURCH_CLASS, STORAGE_CLASS, TAX_CLASS, SHIP_CLASS, FRT_CLASS, PRICE_CLASS, PLANNING_CLASS, ALLOC_CLASS, CUSTOMS_CLASS — the extensive class hierarchy used for categorization and defaulting.
• SHELF_LIFE, RETEST_INTERVAL, EXPACTION_CODE, EXPACTION_INTERVAL — shelf-life and expiration action settings, particularly relevant for regulated products.
• QC_GRADE, GRADE_CTL, STATUS_CTL, LOT_STATUS, QCITEM_ID, QCHOLD_RES_CODE — quality control grade, status control, and QC item linkage.
• WHSE_ITEM_ID, BULK_ID — self-referencing warehouse item and bulk item relationships.

Common Use Cases and Queries

Typical usage centers on item lookups, inventory reporting, and downstream joins. A common pattern joins the item master to its foreign-key lookup tables to resolve coded values into descriptions:

• Retrieve active items by inventory type: SELECT ITEM_NO, ITEM_DESC1, INV_TYPE FROM GMI.IC_ITEM_MST_B WHERE INACTIVE_IND = 0.
• Identify lot-controlled items: SELECT ITEM_NO, LOT_CTL, SUBLOT_CTL FROM GMI.IC_ITEM_MST_B WHERE LOT_CTL = 1.
• Join to inventory balances for stock reporting via IC_WHSE_INV.ITEM_ID = IC_ITEM_MST_B.ITEM_ID.
• Resolve classification lookups by joining category IDs (for example GL_CATEGORY_ID, INV_CATEGORY_ID) to their respective category tables.

Because IC_ITEM_MST_B carries extensive ATTRIBUTE1 through ATTRIBUTE30 columns plus ATTRIBUTE_CATEGORY, implementations frequently store client-specific extension data there. Reports should account for that flexibility when producing item master extracts.

Related Objects

The referential footprint of IC_ITEM_MST_B is exceptionally large. The following are among the most significant related objects, with their actual join columns:

• IC_WHSE_INV — warehouse inventory balances, joined on ITEM_ID; the primary on-hand reporting companion.
• IC_LOTS_MST — lot master, joined on ITEM_ID; essential for lot and sublot traceability.
• IC_TRAN_CMP / IC_TRAN_PND — completed and pending inventory transactions, joined on ITEM_ID.
• GL_ITEM_CST — item cost records, joined on ITEM_ID.
• QC_SPEC_MST / QC_SMPL_MST / QC_RSLT_MST — quality specifications, samples, and results, joined on ITEM_ID.
• PO_RECV_DTL / PO_ORDR_DTL — purchasing receipt and order lines, joined on ITEM_ID.
• OP_ORDR_DTL / OP_PRCE_ITM — order detail and pricing, joined on ITEM_ID.
• IC_COMD_CDS, IC_INVN_TYP, IC_PKGS_MST, IC_LOTS_STS — lookup tables referenced by the item master's foreign keys (COMMODITY_CODE, INV_TYPE, PKG_ID, LOT_STATUS respectively).
• IC_ITEM_MST_B itself — self-references via WHSE_ITEM_ID, BULK_ID, and QCITEM_ID.

Collectively, these relationships confirm that IC_ITEM_MST_B is the principal hub of process manufacturing item data, and that any data extraction or interface design must treat ITEM_ID as the stable integration key.