Search Results mrp_sub_inventories




Overview
Explore in AI Chat

Overview

The MRP_SUB_INVENTORIES table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the central table for storing subinventory netting information, a critical component of the Material Requirements Planning (MRP) engine's supply planning process. During an MRP or Master Production Schedule (MPS) compilation, the system references this table to determine which subinventories within an organization should be considered as available supply (nettable) for meeting planned demand. Its role is to define the mapping between physical inventory locations and the logical planning entity represented by a specific MRP compile, thereby controlling the scope of on-hand inventory netting.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies a nettable subinventory for a specific planning run. The key columns are SUB_INVENTORY_CODE, ORGANIZATION_ID, and COMPILE_DESIGNATOR. The SUB_INVENTORY_CODE and ORGANIZATION_ID pair establishes a foreign key relationship to MTL_SECONDARY_INVENTORIES, ensuring referential integrity to the Inventory module's definition of subinventories. The COMPILE_DESIGNATOR links the record to a specific MRP or MPS plan name. The presence of a record for a given subinventory, organization, and plan designator indicates that the on-hand quantity in that subinventory is considered available to net against gross requirements during the plan explosion.

Common Use Cases and Queries

The primary use case is the configuration and analysis of inventory netting for MRP plans. Administrators use this data to verify which subinventories are included in a plan, often through queries like:

  • Identifying all nettable subinventories for a specific MRP plan: SELECT sub_inventory_code FROM mrp_sub_inventories WHERE organization_id = :org_id AND compile_designator = :plan_name;
  • Validating the setup by joining to MTL_SECONDARY_INVENTORIES for descriptive information: SELECT msi.secondary_inventory_name, msi.description FROM mrp_sub_inventories msi, mtl_secondary_inventories msi WHERE msi.organization_id = msi.organization_id AND msi.sub_inventory_code = msi.secondary_inventory_name AND msi.compile_designator = :plan_name;

This table is also fundamental for troubleshooting plan output, as excluding a subinventory will cause its on-hand balance to be ignored, potentially creating unexpected planned orders.

Related Objects

MRP_SUB_INVENTORIES has integral relationships with several other MRP execution tables. As per the provided metadata, it is referenced by foreign keys in MRP_INVENTORY_LOTS and MRP_RESERVATIONS, linking lot-level inventory details and reservation data to the specific nettable subinventory-plan combination. Its defining foreign key dependency is on the foundational inventory table MTL_SECONDARY_INVENTORIES. This table is populated and maintained by the MRP planning engine processes; while direct DML is possible, modifications are typically performed through the planning user interface or associated backend APIs to maintain system integrity.