Results for “to_op_seq_id”

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

Overview

WSM_ALL_OPERATIONS_V is a validity-verified view owned by the APPS schema within the WSM (Shop Floor Management) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to retrieve all standard operations defined for an organization that is enabled for Oracle Shop Floor Management (OSFM). The view is an operational reporting and integration construct rather than a base table, exposing the resolved relationship between discrete jobs, their routing sequences, and the individual operations within those routings.

The view is of particular relevance to developers and analysts searching for the "bom_operation_sequences" object, because BOM_OPERATION_SEQUENCES is the central table in its definition. The view joins this table to routing, network, standard operation, department, and discrete job data to present a flattened, job-contextualized operation list. The embedded comment "/* ALL THE OPERATIONS IN BON */" confirms its intent to enumerate every operation participating in the BOM operation network.

Underlying Base Objects

ETRM documents the following referenced base objects, all exposed through APPS synonyms:

• BOM_OPERATION_SEQUENCES — the primary driver table, supplying operation sequence numbers, sequence identifiers, descriptions, and department and standard operation references.
• BOM_STANDARD_OPERATIONS — joined with an outer join on STANDARD_OPERATION_ID to resolve operation codes.
• BOM_OPERATIONAL_ROUTINGS — provides the routing sequence context, joined via NVL(COMMON_ROUTING_SEQUENCE_ID, ROUTING_SEQUENCE_ID).
• BOM_OPERATION_NETWORKS — defines the from/to operation links used to constrain which sequences qualify.
• BOM_DEPARTMENTS — supplies DEPARTMENT_CODE for each operation.
• WIP_DISCRETE_JOBS — supplies the job context (WIP_ENTITY_ID, item, job type, routing revision date) that anchors the operation list to a specific discrete job.

The view correlates routing sequences to discrete jobs through COMMON_ROUTING_SEQUENCE_ID, and matches assembly items using a DECODE on WIP_DISCRETE_JOBS.JOB_TYPE. Effectivity is enforced by comparing ROUTING_REVISION_DATE against the operation sequence's EFFECTIVITY_DATE and disable dates.

Key Columns

• WIP_ENTITY_ID — the discrete job identifier from WIP_DISCRETE_JOBS.
• OPERATION_SEQ_NUM — the operation sequence number, the field most commonly referenced when searching on "bom_operation_sequences" terminology.
• OPERATION_SEQUENCE_ID — the unique surrogate key of the operation sequence row.
• STANDARD_OPERATION_ID and OPERATION_CODE — the standard operation reference and its code.
• OPERATION_DESCRIPTION — descriptive text for the operation.
• DEPARTMENT_ID and DEPARTMENT_CODE — the department owning the operation.

Common Use Cases and Queries

Typical scenarios include listing every operation for a given discrete job, validating routing-versus-network consistency, and feeding shop floor integration extracts. A representative query:

• SELECT operation_seq_num, operation_code, department_code, operation_description FROM wsm_all_operations_v WHERE wip_entity_id = :job_id ORDER BY operation_seq_num;
• SELECT wip_entity_id, COUNT(*) FROM wsm_all_operations_v GROUP BY wip_entity_id;
• SELECT a.operation_seq_num, a.operation_code, a.department_code FROM wsm_all_operations_v a WHERE a.department_code = :dept;

Because the view enforces effectivity and network membership, results reflect only operations valid for the job's routing revision date, which makes it suitable for point-in-time shop floor reporting.