Search Results wsm_subinventory_extensions




Overview
Explore in AI Chat

Overview

The WSM_SUBINVENTORY_EXTENSIONS table is a core data object within the Oracle E-Business Suite (EBS) Shop Floor Management (WSM) module, specifically for organizations operating in a Flow Manufacturing (OSFM) environment. Its primary role is to establish and manage the association between a subinventory, a fundamental inventory storage location, and a sector extension. A sector extension defines a specific physical or logical area on the shop floor, such as a production line or a kanban supermarket. This linkage is critical for enabling precise material tracking, replenishment signaling, and work execution within a flow manufacturing cell, thereby supporting lean manufacturing principles integral to OSFM.

Key Information Stored

The table acts as a junction, storing the foreign key relationships that define the subinventory-to-sector extension mapping. Its structure is defined by a composite primary key and two critical foreign keys. The primary key consists of ORGANIZATION_ID and SECONDARY_INVENTORY_NAME, ensuring a unique assignment per subinventory within an inventory organization. The key columns stored are:

This minimalistic design ensures data integrity and enforces the business rule that a subinventory in an OSFM context can be associated with one specific sector extension.

Common Use Cases and Queries

The primary use case is configuring and querying the shop floor layout for material flow. During implementation, records are inserted into this table via the Oracle Flow Manufacturing user interface to define where materials for a specific production line are staged. Common reporting and validation queries involve joining to related master tables. For instance, to list all subinventories and their associated sector extensions for a given organization, a query would be:

SELECT msi.secondary_inventory_name,
      wse.sector_extension_name
FROM wsm_subinventory_extensions wsext,
     mtl_secondary_inventories msi,
     wsm_sector_extensions wse
WHERE wsext.organization_id = :p_org_id
AND wsext.secondary_inventory_name = msi.secondary_inventory_name
AND wsext.organization_id = msi.organization_id
AND wsext.sector_extension_id = wse.sector_extension_id;

Another critical scenario is data validation, ensuring that subinventories referenced in WIP or inventory transactions within an OSFM organization have a valid sector extension defined, which is essential for proper kanban and pull-based replenishment processes.

Related Objects

This table sits at the intersection of inventory structures and shop floor configuration, with documented foreign key relationships to two key master tables:

  • MTL_SECONDARY_INVENTORIES: The table is joined via ORGANIZATION_ID and SECONDARY_INVENTORY_NAME to validate and retrieve descriptive information about the subinventory, such as its description and material status.
  • WSM_SECTOR_EXTENSIONS: The table is joined via SECTOR_EXTENSION_ID to retrieve details about the associated shop floor sector, including its name, type, and the specific flow manufacturing line or cell it services.

As a configuration table, it is primarily referenced by the underlying WSM and OSFM application logic that governs material movement, kanban calculation, and shop floor dispatching. Direct dependencies from other tables are less common, as it serves as a terminal point in the configuration hierarchy linking inventory to the shop floor.