Search Results msc_sub_inventories




Overview
Explore in AI Chat

Overview

The MSC_SUB_INVENTORIES table is a core data object within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the planning engine's repository for subinventory-level netting control parameters. During the planning data snapshot and plan generation processes, this table is populated to define whether on-hand inventory within each specific subinventory should be considered available for netting against demand. Its configuration directly influences material availability calculations, safety stock planning, and the generation of planned orders, making it a critical table for accurate supply chain planning execution.

Key Information Stored

The table's structure is designed to uniquely identify a subinventory within a specific plan and organization. Its primary key columns are SR_INSTANCE_ID (identifying the source system instance), ORGANIZATION_ID, SUB_INVENTORY_CODE, and PLAN_ID. The most significant data column is NETTING_TYPE, which dictates the subinventory's role in the planning calculation. While the exact values are not detailed in the provided excerpt, typical netting types include indicators for whether the subinventory's quantity is fully nettable, not nettable (e.g., for quarantined stock), or available for specific types of demand. This flag enables planners to exclude certain subinventories, like repair or rejected inventory, from the available-to-promise pool.

Common Use Cases and Queries

A primary use case is the validation and audit of subinventory netting rules prior to running a planning cycle. Planners often query this table to ensure all relevant subinventories are correctly classified. A common diagnostic query involves joining to inventory tables to identify subinventories missing a planning definition. For example:

  • Identifying subinventories with a specific netting type for a given plan: SELECT * FROM msc_sub_inventories WHERE plan_id = :p_plan_id AND netting_type = 'Nettable';
  • Comparing planning subinventory setup against the operational inventory setup: SELECT inv.org_code, inv.subinventory_code, plan.netting_type FROM inv_subinventories inv LEFT JOIN msc_sub_inventories plan ON ... WHERE plan.plan_id = :p_plan_id;

Data in this table is typically maintained via the planning user interface or seeded during the snapshot process, not via direct DML.

Related Objects

MSC_SUB_INVENTORIES maintains defined foreign key relationships with other central planning tables, ensuring referential integrity. As per the provided metadata, the key relationships are:

  • MSC_PLAN_ORGANIZATIONS: The table's PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID columns reference MSC_PLAN_ORGANIZATIONS. This ensures a subinventory netting rule is only defined for an organization included in the plan.
  • MSC_RESERVATIONS: The MSC_RESERVATIONS table references MSC_SUB_INVENTORIES via its SR_INSTANCE_ID, PLAN_ID, ORGANIZATION_ID, and SUBINVENTORY columns. This links specific supply or demand reservations to the netting rule of the subinventory they are associated with.

These relationships position MSC_SUB_INVENTORIES as a pivotal link between high-level plan definitions and detailed inventory reservation transactions within the ASCP data model.