Results for “variable_leadtime”

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

Overview

IC_WHSE_INV is a Process Manufacturing Inventory table owned by the GMI schema in Oracle EBS 12.1.1 and 12.2.2. It stores warehouse-level inventory planning and control rules that govern how each item behaves within a specific warehouse. Each row represents the rules assigned to a unique combination of item and warehouse, covering replenishment parameters, lead times, sourcing indicators, cycle-count scheduling, and classification groupings used for costing, shipping, and freight processing.

Because the table is keyed by an item-warehouse combination and holds descriptive planning attributes rather than transactional movements, the heuristic Data Vault classification is satellite-leaning. It can reasonably be modeled as a satellite attached to an item/warehouse hub-and-link structure, where the business key (ITEM_ID plus WHSE_CODE) identifies the parent relationship and the remaining columns provide the changing descriptive context. This classification is a modeling suggestion only; in native EBS terms the object is a standard, non-partitioned inventory rules table.

Key Information Stored

• WHSEINV_ID — the surrogate primary key defined by index IC_WHSE_INV_PK.
• ITEM_ID and WHSE_CODE — the composite business-key candidates defined by unique index IC_WHSE_INV_U1; together they identify one rule row per item per warehouse.
• SAFETY_STOCK, REORDER_POINT, MIN_QTY, MAX_QTY, STD_QTY — replenishment and stocking-level thresholds.
• FIXED_LEADTIME and VARIABLE_LEADTIME — planning lead-time components.
• INNER_TIMEFENCE, OUTER_TIMEFENCE, RESCHEDULE_PERIOD, DAYS_SUPPLY — scheduling and time-fence controls used by the planning engine.
• PURCHASE_IND, TRANSFER_IND, PRODUCTION_IND — sourcing/order-generation indicators.
• RULE_TYPE, SCRAP_FACTOR, WHSE_ABCCODE — rule classification and scrap allowance.
• CYCLECOUNT_DAYS and LASTCOUNT_DATE — cycle-count frequency and last-count tracking.
• COUNT_CLASS, GL_CLASS, SHIP_CLASS, FRT_CLASS, and the corresponding ATTRIBUTE descriptor and ATTRIBUTE_CATEGORY columns — classification codes reused for counting, costing, shipping, and freight.
• TEXT_CODE — reference to descriptive text held in IC_TEXT_HDR.
• DELETE_MARK and TRANS_CNT — logical delete flag and transaction counter.
• Audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Typical reporting and integration scenarios include extracting item-warehouse replenishment rules for planning tuning, cycle-count scheduling reports, and classification-code validation. A representative query joining the parent item and warehouse masters is:

• SELECT w.WHSE_CODE, w.ITEM_ID, w.SAFETY_STOCK, w.REORDER_POINT, w.MIN_QTY, w.MAX_QTY FROM GMI.IC_WHSE_INV w WHERE w.DELETE_MARK = 0 AND w.WHSE_CODE = :warehouse;
• Join to GMI.IC_ITEM_MST on ITEM_ID to resolve item descriptions for a rule exception report.
• Join to GMI.IC_WHSE_MST on WHSE_CODE to list all rules for a given warehouse.
• Filter on CYCLECOUNT_DAYS and LASTCOUNT_DATE to identify items overdue for a physical count.
• Aggregate by RULE_TYPE or WHSE_ABCCODE to summarize planning policy coverage across the organization.

Always exclude rows with DELETE_MARK set to eliminate logically deleted records from reporting output.

Related Objects

• IC_ITEM_MST and IC_ITEM_MST_B — referenced via IC_WHSE_INV.ITEM_ID; supply item master attributes.
• IC_WHSE_MST — referenced via IC_WHSE_INV.WHSE_CODE; provides warehouse definitions.
• IC_RANK_MST — referenced via WHSE_CODE and WHSE_ABCCODE for ABC ranking.
• IC_CRUL_CLS, IC_GLED_CLS, IC_SHIP_CLS, IC_FRGT_CLS — classification masters referenced through COUNT_CLASS, GL_CLASS, SHIP_CLASS, and FRT_CLASS.
• IC_TEXT_HDR — referenced via TEXT_CODE for narrative text.
• IC_ITEM_CDT — references back to IC_WHSE_INV via ITEM_ID and WHSE_CODE, forming a child relationship used for item-warehouse detail data.