Results for “default_acct_class_code”

32 results




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

Overview

WSM_SECTOR_EXTENSIONS is a table owned by the WSM schema in Oracle E-Business Suite, belonging to the WSM – Shop Floor Management product family (Oracle Shop Floor Management, or OSFM). In OSFM, a sector extension represents the segment of a manufacturing process for which a lot-based job is defined. The table therefore stores the master definitions of these sector extensions, one row per sector extension per organization, establishing the granularity at which lot-based production is tracked on the shop floor.

In Oracle EBS 12.1.1 and 12.2.2 the table carries ten documented columns and is classified in ETRM as VALID. The relationship data mined from its foreign key structure suggests a satellite-leaning Data Vault classification. Modeled in Data Vault terms, the sector extension identifier would typically serve as a hub or business key anchor, while the descriptive and organizational attributes documented here behave like satellite attributes. This classification is a heuristic modeling suggestion rather than a functional property of the table itself.

Key Information Stored

WSM_SECTOR_EXTENSIONS holds both surrogate identity and descriptive attributes for sector extensions. The most significant columns documented are:

The surrogate key (SECTOR_EXTENSION_ID) should be distinguished from the business-key candidates exposed by the unique indexes: SECTOR_EXTENSION_ID alone (U1) and the composite (ORGANIZATION_ID, SECTOR_EXTENSION_CODE) (U2). Application logic and reporting should generally resolve records through the organization and code pair rather than through the surrogate identifier.

Common Use Cases and Queries

Typical use cases include validating the set of active sector extensions for a given organization, joining sector extensions to their dependent subinventory extensions, and reporting on the default accounting class associated with each extension. A representative query listing sector extensions by organization is:

  • SELECT sector_extension_id, sector_extension_code, sector_extension_description, default_acct_class_code FROM wsm_sector_extensions WHERE organization_id = :org_id ORDER BY sector_extension_code;
  • Resolving a business key to the surrogate key: SELECT sector_extension_id FROM wsm_sector_extensions WHERE organization_id = :org_id AND sector_extension_code = :code;
  • Reporting sector extensions and their child subinventory extensions: SELECT s.sector_extension_code, si.subinventory_extension_id FROM wsm_sector_extensions s, wsm_subinventory_extensions si WHERE s.sector_extension_id = si.sector_extension_id AND s.organization_id = :org_id;

Because the table is a definition-level object rather than a transactional table, it is frequently used as a lookup in shop-floor and lot-based job reporting, and as a validation source in data-conversion or interface programs that establish manufacturing sectors.

Related Objects

The following documented relationships are the most significant for working with WSM_SECTOR_EXTENSIONS:

  • WSM_SUBINVENTORY_EXTENSIONS – References WSM_SECTOR_EXTENSIONS through SECTOR_EXTENSION_ID. This is the principal child table, linking subinventory extensions to their parent sector extension.
  • WIP_ACCOUNTING_CLASSES – Referenced by WSM_SECTOR_EXTENSIONS.DEFAULT_ACCT_CLASS_CODE, supplying the valid accounting class values.
  • WSM_PARAMETERS – Referenced by WSM_SECTOR_EXTENSIONS.ORGANIZATION_ID, providing the organization-level OSFM parameter context.
  • WSM_SECTOR_EXTENSIONS_PK, WSM_SECTOR_EXTENSIONS_UK, WSM_SECTOR_EXTENSIONS_U1, WSM_SECTOR_EXTENSIONS_U2 – The primary, unique, and unique-index constraints that enforce identity and business-key uniqueness on the table.