Skip to content
EBS Reference

MSC_SYSTEM_ITEMS

Schema: MSCmasterPer inventory org

The planning copy of the item master at plan + instance + org + item grain — collected item attributes frozen per plan run, and the bridge column back to the source EBS item

Identity
Module: PlanningInventory-org partitioned (ORGANIZATION_ID)
Grain note

INVENTORY_ITEM_ID here is the planning-side surrogate — the EBS item id is SR_INVENTORY_ITEM_ID; the single bridge edge uses that item pair plus ORGANIZATION_ID to prevent fan-out and assumes one collected source instance

Notes

Attributes are frozen per plan run — the same item differs across PLAN_IDs. The physical unique key extends the four-part grain with simulation-set columns, so simulation runs can duplicate the working key. The bridge back to EBS is one edge: SR_INVENTORY_ITEM_ID is its item pair, while the organization pair is retained under the catalog's fan-out rule. Because collected organization ids are instance-qualified, that join assumes a single collected source instance; multi-instance estates must resolve the source instance before using it.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

18 fields · 4 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1PLAN_IDThe plan — item attributes are frozen per plan runNUMBER
Primary-key field
2SR_INSTANCE_IDThe collected source instance — part of the keyNUMBER
Primary-key field
3ORGANIZATION_IDPlanning-instance copy of the org id — part of the keyNUMBER
Primary-key field
4INVENTORY_ITEM_IDThe planning-side item surrogate — part of the key; NOT the EBS item idNUMBER
Primary-key field
5SR_INVENTORY_ITEM_IDThe item id in the source EBS instance — the ONLY sound bridge back to the item masterNUMBER
6ITEM_NAMEThe item name as collectedVARCHAR2
7DESCRIPTIONItem description as collectedVARCHAR2
8UOM_CODEPrimary UOM as collectedVARCHAR2
9MRP_PLANNING_CODEHow the item is planned — MRP, MPS, DRP combinations; codes enumerated in the data dictionary's own commentNUMBER
10FIXED_LEAD_TIMEFixed lead time as collectedNUMBER
11VARIABLE_LEAD_TIMEVariable lead timeNUMBER
12PREPROCESSING_LEAD_TIMEPreprocessing lead timeNUMBER
13POSTPROCESSING_LEAD_TIMEPostprocessing lead timeNUMBER
14PLANNING_TIME_FENCE_DATEPlanning time fence as of the plan runDATE
15DEMAND_TIME_FENCE_DATEDemand time fence as of the plan runDATE
16STANDARD_COSTStandard cost as collectedNUMBER
17SAFETY_STOCK_CODESafety stock method as collectedNUMBER
18MINIMUM_ORDER_QUANTITYMinimum order quantity constraintNUMBER

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

Starting point for reading MSC_SYSTEM_ITEMS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <PLAN_ID>, <SR_INSTANCE_ID>, <INVENTORY_ITEM_ID>, <watermark>

-- ============================================================
-- Table  : MSC_SYSTEM_ITEMS — The planning copy of the item master at plan + instance + org + item grain — collected item attributes frozen per plan run, and the bridge column back to the source EBS item
-- Purpose: Column-selected read of MSC_SYSTEM_ITEMS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + PLAN_ID + SR_INSTANCE_ID + INVENTORY_ITEM_ID
-- Caution: INVENTORY_ITEM_ID here is the planning-side surrogate — the EBS item id is SR_INVENTORY_ITEM_ID; the single bridge edge uses that item pair plus ORGANIZATION_ID to prevent fan-out and assumes one collected source instance
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.PLAN_ID AS "The plan — item attributes are frozen per plan run",
  t.SR_INSTANCE_ID AS "The collected source instance — part of the key",
  t.ORGANIZATION_ID AS "Planning-instance copy of the org id — part of the key",
  t.INVENTORY_ITEM_ID AS "The planning-side item surrogate — part of the key; NOT the EBS item id",
  t.SR_INVENTORY_ITEM_ID AS "The item id in the source EBS instance — the ONLY sound bridge back to the item master",
  t.ITEM_NAME AS "The item name as collected",
  t.DESCRIPTION AS "Item description as collected",
  t.UOM_CODE AS "Primary UOM as collected",
  t.MRP_PLANNING_CODE AS "How the item is planned — MRP, MPS, DRP combinations; codes enumerated in the data dictionary's own comment",
  t.FIXED_LEAD_TIME AS "Fixed lead time as collected",
  t.VARIABLE_LEAD_TIME AS "Variable lead time",
  t.PREPROCESSING_LEAD_TIME AS "Preprocessing lead time",
  t.POSTPROCESSING_LEAD_TIME AS "Postprocessing lead time",
  t.PLANNING_TIME_FENCE_DATE AS "Planning time fence as of the plan run",
  t.DEMAND_TIME_FENCE_DATE AS "Demand time fence as of the plan run",
  t.STANDARD_COST AS "Standard cost as collected",
  t.SAFETY_STOCK_CODE AS "Safety stock method as collected",
  t.MINIMUM_ORDER_QUANTITY AS "Minimum order quantity constraint"
FROM <catalog>.<schema>.MSC_SYSTEM_ITEMS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.PLAN_ID = <PLAN_ID>
  -- AND t.SR_INSTANCE_ID = <SR_INSTANCE_ID>
  -- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PLAN_ID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Loading relationship diagram…

Join details

  • MSC_SUPPLIESMSC_SYSTEM_ITEMSforeign key · N:1
    ON MSC_SUPPLIES.INVENTORY_ITEM_ID = MSC_SYSTEM_ITEMS.INVENTORY_ITEM_ID AND MSC_SUPPLIES.PLAN_ID = MSC_SYSTEM_ITEMS.PLAN_ID AND MSC_SUPPLIES.SR_INSTANCE_ID = MSC_SYSTEM_ITEMS.SR_INSTANCE_ID AND MSC_SUPPLIES.ORGANIZATION_ID = MSC_SYSTEM_ITEMS.ORGANIZATION_ID
  • MSC_DEMANDSMSC_SYSTEM_ITEMSforeign key · N:1
    ON MSC_DEMANDS.INVENTORY_ITEM_ID = MSC_SYSTEM_ITEMS.INVENTORY_ITEM_ID AND MSC_DEMANDS.PLAN_ID = MSC_SYSTEM_ITEMS.PLAN_ID AND MSC_DEMANDS.SR_INSTANCE_ID = MSC_SYSTEM_ITEMS.SR_INSTANCE_ID AND MSC_DEMANDS.ORGANIZATION_ID = MSC_SYSTEM_ITEMS.ORGANIZATION_ID
  • MSC_SYSTEM_ITEMSMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON MSC_SYSTEM_ITEMS.SR_INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MSC_SYSTEM_ITEMS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID

Browse more Planning tables

More Planning tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.