Results for “representative_flag”

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

Overview

The WSM_STARTING_JOBS_INTERFACE table is a Shop Floor Management (WSM) interface table within the Oracle E-Business Suite WSM product family. It serves as the staging area for importing WIP lot transaction starting lots, acting as the child table to WSM_SPLIT_MERGE_TXN_INTERFACE. During lot transaction imports — typically from external manufacturing execution systems, shop floor data collection devices, or legacy MES feeds — starting job records are first written into this interface table, validated and processed, and then applied to the production work-in-process tables. The table resides in the WSM schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a link table. It connects a parent split/merge transaction (via HEADER_ID) to a WIP entity (via WIP_ENTITY_ID), resolving a many-to-many style relationship between the transaction interface and discrete production jobs. Modelers should treat it as a transactional link rather than a pure hub or satellite, since its rows represent associations between two business entities plus descriptive attributes.

Key Information Stored

The documented physical schema contains 39 columns. The primary key is WSM_STARTING_JOBS_INTERFAC_PK, defined on HEADER_ID, which is itself a foreign key to WSM_SPLIT_MERGE_TXN_INTERFACE, establishing the parent-child association. The most significant columns include:

• HEADER_ID — primary key and link to the parent split/merge interface header.
• WIP_ENTITY_ID — foreign key to WIP_ENTITIES, identifying the production job being started.
• WIP_ENTITY_NAME — denormalized job name for reference and validation.
• OPERATION_SEQ_NUM and INTRAOPERATION_STEP — identify the routing operation and step context for the starting lot.
• ROUTING_SEQ_ID — links to the routing sequence definition.
• PRIMARY_ITEM_ID — the item associated with the starting job.
• ORGANIZATION_ID — the inventory organization context.
• PROCESS_STATUS and ERROR_MESSAGE — track import processing outcome and validation failures.
• REPRESENTATIVE_FLAG — indicates whether the row represents the representative starting lot.
• GROUP_ID and INTERNAL_GROUP_ID — support grouping and internal processing correlation.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit context.
• XML_DOCUMENT_ID — references the source XML payload for the import.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield and extensibility columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

HEADER_ID functions as the surrogate primary key, while business-key candidates derive from the combination of WIP_ENTITY_ID, OPERATION_SEQ_NUM, and INTRAOPERATION_STEP, though no unique index beyond the PK is documented.

Common Use Cases and Queries

Typical scenarios include monitoring import success rates, diagnosing failed starting lot imports, and reconciling interface rows against posted WIP transactions. A common diagnostic query lists failed rows for a concurrent request:

• SELECT header_id, wip_entity_name, organization_id, process_status, error_message FROM wsm_starting_jobs_interface WHERE process_status = 'ERROR' AND request_id = :req_id;
• Join to WIP_ENTITIES on wip_entity_id to confirm the target job exists.
• Join to WSM_SPLIT_MERGE_TXN_INTERFACE on header_id to retrieve parent transaction context.
• Aggregate by organization_id and process_status for throughput reporting.

Reporting use cases include post-import audit trails and root-cause analysis of rejected starting lots before corrective resubmission.

Related Objects

• WSM_SPLIT_MERGE_TXN_INTERFACE — parent table; joined via HEADER_ID.
• WIP_ENTITIES — referenced through WIP_ENTITY_ID; supplies production job details.
• WIP_DISCRETE_JOBS — extended attributes of the referenced WIP entity.
• MTL_SYSTEM_ITEMS_B — resolves PRIMARY_ITEM_ID for item descriptions.
• WIP_OPERATIONS and WIP_OPERATION_SEQUENCES — operation and routing context.
• FND_CONCURRENT_REQUESTS — ties REQUEST_ID to the import program run.
• WSM_SPLIT_MERGE_TXN_PUB — the public API layer that consumes these interface rows during import processing.