Results for “primary_item_segments”

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

Overview

WSM_LOT_JOB_INTERFACE is the open interface table used by Oracle Shop Floor Management (OSFM) to import lot-based discrete jobs into Oracle E-Business Suite Manufacturing. Residing in the WSM schema, it serves as the staging area through which external systems — typically legacy MES platforms, custom production schedulers, or upstream planning tools — feed configured lot job definitions into OSFM for validation, transformation, and ultimate creation of WIP entities. The table is essential to the Import Lot Based Jobs concurrent program, which reads pending rows, validates them against bills of material, routings, and inventory structures, and then writes the resulting work orders into the WIP execution tables. The object is documented as VALID across both 12.1.1 and 12.2.2, with a physical schema of 108 columns.

From a data modeling perspective, ETRM's heuristic Data Vault classification places WSM_LOT_JOB_INTERFACE as a link. This is a modeling suggestion rather than a physical design assertion: the table's dense foreign-key surface ties it to BOM, routing, inventory, WIP, and kanban reference entities, consistent with an associative structure recording relationships between a job request and its referenced master data.

Key Information Stored

The table's surrogate primary key is HEADER_ID, enforced through WSM_LOT_JOB_INTERFACE_PK and reinforced by the unique index WSM_LOT_JOB_INTERFACE_U1 on the same column. HEADER_ID is therefore the internal identifier for each interface record, while JOB_NAME effectively serves as the business-facing job reference and is itself foreign-keyed to WIP_ENTITIES.

The most operationally significant columns include:

• GROUP_ID, PROCESS_TYPE, MODE_FLAG — control the grouping, import mode (create, update, release), and processing behavior of each batch.
• ORGANIZATION_ID — identifies the manufacturing organization; foreign-keyed to WSM_PARAMETERS.
• PRIMARY_ITEM_ID — the item being built, referenced against BOM_BILL_OF_MATERIALS and BOM_OPERATIONAL_ROUTINGS.
• PRIMARY_ITEM_SEGMENTS — concatenated flexfield representation of the item for reporting and error messaging.
• START_QUANTITY and NET_QUANTITY — planned and net production quantities for the lot job.
• CLASS_CODE — work-in-process accounting class, foreign-keyed to WIP_ACCOUNTING_CLASSES.
• WIP_SUPPLY_TYPE, LOT_NUMBER, LOT_CONTROL_CODE — drive lot identification and supply semantics.
• COMPLETION_SUBINVENTORY and COMPLETION_LOCATOR_ID — completion destination, referencing MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS.
• SCHEDULE_GROUP_ID, REPETITIVE_SCHEDULE_ID, KANBAN_CARD_ID — optional scheduling and pull-signal associations.
• STATUS_TYPE, PROCESS_STATUS, ERROR_CODE, ERROR_MSG — interface processing state and diagnostic output.
• REQUEST_ID, PROGRAM_ID — concurrent request tracking for the import program.

Common Use Cases and Queries

The primary use case is populating the interface table ahead of the Import Lot Based Jobs concurrent request. Integrators insert rows with MODE_FLAG and PROCESS_TYPE set according to the desired action, populate GROUP_ID to batch records, then invoke the import program. Post-import, the table is queried to reconcile successes and failures.

Reconciling failed rows by error state:

SELECT HEADER_ID, JOB_NAME, PRIMARY_ITEM_SEGMENTS, ERROR_CODE, ERROR_MSG FROM WSM.WSM_LOT_JOB_INTERFACE WHERE PROCESS_STATUS = 'ERROR' AND GROUP_ID = :p_group_id;

Confirming successful creation by joining to the WIP entity:

SELECT i.JOB_NAME, i.START_QUANTITY, w.WIP_ENTITY_ID, w.STATUS_TYPE FROM WSM.WSM_LOT_JOB_INTERFACE i, WIP.WIP_ENTITIES w WHERE i.WIP_ENTITY_ID = w.WIP_ENTITY_ID AND i.GROUP_ID = :p_group_id;

Reporting frequently includes staging volume by organization and process phase, and auditing rows still pending processing by REQUEST_ID.

Related Objects

The table's foreign-key graph identifies the objects most tightly coupled to it:

• WIP_ENTITIES — joined via JOB_NAME and WIP_ENTITY_ID; represents the created or updated job.
• BOM_BILL_OF_MATERIALS — joined via PRIMARY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_BOM_DESIGNATOR to resolve the BOM.
• BOM_OPERATIONAL_ROUTINGS — joined via PRIMARY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_ROUTING_DESIGNATOR to resolve the routing.
• MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS — completion subinventory and locator validation.
• WIP_ACCOUNTING_CLASSES — joined on CLASS_CODE and ORGANIZATION_ID.
• WSM_PARAMETERS — organization-level OSFM configuration.
• WIP_REPETITIVE_SCHEDULES, WIP_SCHEDULE_GROUPS, and MTL_KANBAN_CARDS — optional scheduling and kanban associations.

Collectively, these relationships confirm the interface's role as the gateway between external job requests and the OSFM execution model.