Results for “wsm_sector_extensions_u2”

12 results




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

Overview

WSM.WSM_SECTOR_EXTENSIONS is a transactional configuration table within the Oracle E-Business Suite Warehouse Management (WSM) module, which in EBS 12.1.1 and 12.2.2 is delivered under the Oracle Shop Floor Management (OSFM) and Process Manufacturing umbrella. The table defines Sector Extensions, which per the ETRM documentation represent "the segment of a manufacturing process for which a Lot based Job is defined." In practical OSFM terms, a Sector Extension is the discrete manufacturing stage or operation boundary within a process flow against which a lot-based work-in-process job is created, tracked, and costed.

The object is registered in FND Design Data as WSM.WSM_SECTOR_EXTENSIONS and resides in the APPS_TS_TX_DATA tablespace with a status of VALID. Its indexes are held separately in APPS_TS_TX_IDX. From a dimensional modeling perspective, the mined relationship structure classifies this table as satellite-leaning: SECTOR_EXTENSION_ID is a surrogate primary key generated by the WSM_SECTOR_EXTENSIONS_S sequence, and the descriptive attributes (code, description, default accounting class) are functionally dependent on that key rather than acting as an independent hub or link. Modelers should treat it as a descriptive satellite anchored on the Sector Extension business key.

Key Information Stored

The table stores ten documented columns. The most significant are:

The secondary unique index WSM_SECTOR_EXTENSIONS_U2 — the subject of the user's search term — is defined on the composite business key (ORGANIZATION_ID, SECTOR_EXTENSION_CODE). It guarantees that a Sector Extension code is unique within a given organization, which is the natural business rule used during data loading and validation.

Common Use Cases and Queries

Typical usage covers configuration reporting (listing Sector Extensions per organization), job-setup validation for lot-based OSFM jobs, and reconciliation to confirm a valid default WIP accounting class is assigned before transactions post.

To retrieve Sector Extensions for a specific organization:

  • SELECT SECTOR_EXTENSION_ID, SECTOR_EXTENSION_CODE, SECTOR_EXTENSION_DESCRIPTION, DEFAULT_ACCT_CLASS_CODE FROM WSM.WSM_SECTOR_EXTENSIONS WHERE ORGANIZATION_ID = :org_id ORDER BY SECTOR_EXTENSION_CODE;
  • Joining to the accounting class for validation: SELECT se.SECTOR_EXTENSION_CODE, wac.* FROM WSM.WSM_SECTOR_EXTENSIONS se, WIP_ACCOUNTING_CLASSES wac WHERE se.DEFAULT_ACCT_CLASS_CODE = wac.ACCOUNTING_CLASS_CODE AND se.ORGANIZATION_ID = :org_id;
  • Locating a row by its business key via the U2 index: SELECT * FROM WSM.WSM_SECTOR_EXTENSIONS WHERE ORGANIZATION_ID = :org_id AND SECTOR_EXTENSION_CODE = :code;

Related Objects

The ETRM dependency data identifies the following significant relationships:

  • WSM.WSM_SUBINVENTORY_EXTENSIONS — references this table via SECTOR_EXTENSION_ID, associating subinventory extensions with a Sector Extension.
  • WIP_ACCOUNTING_CLASSES — referenced by DEFAULT_ACCT_CLASS_CODE, supplying the default WIP accounting class.
  • WSM.WSM_PARAMETERS — referenced by ORGANIZATION_ID, tying the row to OSFM parameter setup.
  • WSM_SECTOR_EXTENSIONS_S — the sequence provisioning SECTOR_EXTENSION_ID.
  • FND_USER and FND_LOGINS — standard "Who" column foreign keys for audit columns.