Results for “secondary_inventory_name”

50+ results




Overview
Explore in AI Chat

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

Overview

WSM_SUBINVENTORY_EXTENSIONS is a table in the WSM schema (Shop Floor Management) that stores the association between sector extensions and subinventories within an Oracle Shop Floor Management (OSFM) organization. Its documented description is: "Sector Extensions associated with a subinventory in an OSFM organization." In Oracle EBS 12.1.1 and 12.2.2, this table acts as a configuration bridge — it determines which sector extension rules apply to a given subinventory in a specific organization, driving how OSFM validates or routes material through the shop floor.

From a dimensional modeling perspective, the ETRM heuristic Data Vault classification for this object is link. That is a suggested modeling interpretation rather than a documented Oracle fact: the table carries no descriptive attributes beyond standard audit columns and a single foreign key, so it functions as an associative/link table joining two business entities. The linkage is between a subinventory (identified at the organization level) and a sector extension record.

Key Information Stored

The table is physically documented with 8 columns. The most significant are:

The documented surrogate primary key is WSM_SUBINVENTORY_EXTENSION_PK, defined on (ORGANIZATION_ID, SECONDARY_INVENTORY_NAME). The unique index WSM_SUBINVENTORY_EXTENSIONS_U1 is also defined on (ORGANIZATION_ID, SECONDARY_INVENTORY_NAME). Because the business-key candidate and the primary key coincide, there is no separate hidden surrogate; the natural composite of organization and subinventory serves as the identifier. This implies one sector extension record per subinventory per organization, with SECTOR_EXTENSION_ID carrying the associated value.

Common Use Cases and Queries

Typical use cases involve resolving, for a given organization and subinventory, which sector extension governs OSFM behavior, and validating that all active subinventories are correctly mapped. A common join query links the table back to inventory master data:

  • Subinventory-to-extension lookup: SELECT se.SECONDARY_INVENTORY_NAME, se.SECTOR_EXTENSION_ID FROM WSM_SUBINVENTORY_EXTENSIONS se WHERE se.ORGANIZATION_ID = :org_id;
  • Join to inventory subinventories: ... FROM WSM_SUBINVENTORY_EXTENSIONS se JOIN MTL_SECONDARY_INVENTORIES ms ON ms.ORGANIZATION_ID = se.ORGANIZATION_ID AND ms.SECONDARY_INVENTORY_NAME = se.SECONDARY_INVENTORY_NAME;
  • Join to sector extensions: ... JOIN WSM_SECTOR_EXTENSIONS wse ON wse.SECTOR_EXTENSION_ID = se.SECTOR_EXTENSION_ID;

Reporting scenarios include auditing which subinventories have sector extensions configured versus those that do not, and comparing configuration across organizations. Because audit columns are present, it supports change-tracking reports on when a sector extension mapping was last modified.

Related Objects

The following objects are most significant based on documented foreign key relationships:

  • MTL_SECONDARY_INVENTORIES — Referenced by (ORGANIZATION_ID, SECONDARY_INVENTORY_NAME); provides the subinventory definition and description.
  • WSM_SECTOR_EXTENSIONS — Referenced by SECTOR_EXTENSION_ID; supplies the sector extension definition that is applied to the subinventory.
  • WSM_SUBINVENTORY_EXTENSIONS_U1 / WSM_SUBINVENTORY_EXTENSION_PK — Unique index and primary key enforcing the organization/subinventory uniqueness.
  • MTL_PARAMETERS and ORG_ORGANIZATION_DEFINITIONS — Commonly joined to resolve organization context and OSFM enablement.
  • WSM_SECTOR_EXTENSION_* related reference tables — Provide the detailed rules associated with a sector extension.

Together these objects form the configuration chain that enables OSFM to apply sector-specific logic to a subinventory within a plant.