Results for “msc_sub_inventories”

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

Overview

MSC_SUB_INVENTORIES is a table in the MSC schema belonging to the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite, and is present in both 12.1.1 and 12.2.2 environments. It stores planning-relevant attributes for each subinventory defined in Oracle Inventory, most importantly the netting type that determines whether the on-hand quantity held in a subinventory is considered available supply during a planning run. Every subinventory registered in Oracle Inventory is expected to have a corresponding row in MSC_SUB_INVENTORIES for a given plan, organization, and source instance, with NETTING_TYPE indicating whether that subinventory participates in netting calculations.

The table acts as a planning-side extension of the Inventory subinventory master. The MSC schema is populated through collections rather than direct user entry, so the contents are refreshed on the schedule defined for the source instance and plan. From a Data Vault modeling perspective, the FK structure is satellite-leaning: the table hangs off MSC_PLAN_ORGANIZATIONS and refines the subinventory dimension with descriptive and planning-specific attributes rather than establishing an independent business relationship.

Key Information Stored

• PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, SUB_INVENTORY_CODE — the composite business key and primary key (MSC_SUB_INVENTORIES_PK). PLAN_ID scopes the row to a specific plan, SR_INSTANCE_ID identifies the source instance, ORGANIZATION_ID identifies the inventory organization, and SUB_INVENTORY_CODE identifies the subinventory.
• NETTING_TYPE — the central functional attribute, defining whether quantities in the subinventory are netted as supply.
• INCLUDE_NON_NETTABLE — indicates whether non-nettable subinventory balances should still be considered in planning.
• INVENTORY_ATP_CODE — the ATP code carried from Oracle Inventory, influencing availability calculations during planning.
• DESCRIPTION — descriptive text for the subinventory as held on the planning side.
• CONDITION_TYPE and SR_RESOURCE_NAME — planning classification fields used in constraint and sourcing logic.
• REFRESH_NUMBER, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — collection and concurrent program audit fields.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield columns.

A unique index, MSC_SUB_INVENTORIES_U1 (PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, SUB_INVENTORY_CODE), mirrors the primary key and confirms the business-key candidate set. The table contains 37 documented columns in total.

Common Use Cases and Queries

Planners and implementers query this table to verify how a subinventory will be treated during a planning run, particularly when on-hand balances appear to be excluded from supply. A typical check lists the netting configuration for an organization:

• SELECT sub_inventory_code, netting_type, include_non_nettable, inventory_atp_code FROM msc_sub_inventories WHERE plan_id = :plan_id AND organization_id = :org_id; — audit of netting settings for one organization within a plan.
• SELECT sub_inventory_code FROM msc_sub_inventories WHERE plan_id = :plan_id AND netting_type = 'NON-NETTABLE'; — identification of subinventories excluded from netting.
• Joining to MSC_RESERVATIONS on SR_INSTANCE_ID, PLAN_ID, ORGANIZATION_ID, and SUBINVENTORY to trace how reservations are attributed to specific subinventories in a plan.
• Comparing MSC_SUB_INVENTORIES against MTL_SECONDARY_INVENTORIES to detect subinventories defined in Inventory that lack a corresponding planning row after a collection.

Reporting use cases include netting configuration matrices for new plan implementations, collection reconciliation reports, and diagnostics when supply totals in the planner workbench do not match expected on-hand values.

Related Objects

• MSC_PLAN_ORGANIZATIONS — referenced by MSC_SUB_INVENTORIES.PLAN_ID; the parent planning-organization record.
• MSC_RESERVATIONS — references this table via SR_INSTANCE_ID, PLAN_ID, ORGANIZATION_ID, and SUBINVENTORY.
• MTL_SECONDARY_INVENTORIES — the Inventory-side subinventory master from which planning data is collected.
• MTL_ONHAND_QUANTITIES_DETAIL / MTL_MATERIAL_TRANSACTIONS — source of on-hand and transaction data used with netting decisions.
• MSC_PLANS — defines the plan referenced by PLAN_ID.
• FND_DESCR_FLEX_COLUMN_USAGES and FND_FLEX_VALUES — support interpretation of the ATTRIBUTE columns.
• MSC_APPLY_SUB_INV_PUB / collection concurrent programs — the standard mechanisms that populate and refresh this table.