Results for “fm_operation_seq_num”

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

Overview

WSM_COPY_NEXT_OPERATIONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined under the WSM (Shop Floor Management) product family. Its documented purpose is to return all valid next operations for a job based on the network routing held in the job's copy tables. In practice the view exposes the routing graph for a discrete job so that a downstream operation can be selected from the operations that legally follow the current one. This makes it a foundational object for shop-floor sequencing, operation move transactions, and any reporting that must traverse a job's routing rather than read a single operation in isolation.

The view is especially relevant in the context of Oracle EBS 12.1.1 and 12.2.2, where WSM copy tables store a job-specific snapshot of the routing. Because the routing is materialized per job, "next operation" logic cannot be answered from BOM routing tables alone; it must be answered from the copy tables, which is precisely what this view does.

Underlying Base Objects

The documented referenced base objects are BOM_DEPARTMENTS, BOM_OPERATION_SEQUENCES, BOM_STANDARD_OPERATIONS, WIP_DISCRETE_JOBS, WIP_OPERATIONS, WSM_COPY_OPERATIONS, WSM_COPY_OP_NETWORKS, and WSM_PARAMETERS, all accessed through APPS synonyms. The view text joins WSM_COPY_OPERATIONS (WCO) and WSM_COPY_OP_NETWORKS (WCON) as the job-level routing and network sources, WIP_OPERATIONS twice (WO and WO2) to anchor the "from" operation and the job's maximum sequence, WSM_PARAMETERS (WP) for the sequence increment, and BOM_STANDARD_OPERATIONS (BSO) for operation codes and descriptions. BOM_OPERATION_SEQUENCES, BOM_DEPARTMENTS, and WIP_DISCRETE_JOBS appear in the union branch and supporting joins. The definition is a UNION of the network-based branch and a routing-based branch, allowing the view to present both explicitly networked transitions and standard sequence transitions.

Key Columns

• WIP_ENTITY_ID — Identifies the discrete job; the join key across all branches.
• FM_OPERATION_SEQ_NUM — The "from" (current) operation sequence number, sourced from WIP_OPERATIONS.OPERATION_SEQ_NUM. This is the columnmost commonly searched, appearing as the alias FM_OPERATION_SEQ_NUM.
• TO_WO_OPERATION_SEQ_NUM — The target work-order operation sequence, computed from WO2.OPERATION_SEQ_NUM plus NVL(WP.OP_SEQ_NUM_INCREMENT,10).
• TO_WCO_OPERATION_SEQ_NUM — The target copy-table sequence number, used to locate the corresponding copy operation.
• FM_OPERATION_SEQ_ID / TO_OPERATION_SEQ_ID — Internal operation sequence identifiers for the from and to operations.
• OPERATION_CODE / NEXT_OPERATION_CODE — Standard operation codes for the current and next operations.
• STANDARD_OPERATION_ID, DEPARTMENT_CODE, DEPARTMENT_ID — Standard operation and department context.
• RECOMMENDED_NEXT_OPERATION / RECOMMENDED_OPERATION — Flags from WSM_COPY_OP_NETWORKS and WSM_COPY_OPERATIONS indicating the recommended routing path.
• OPERATION_DESCRIPTION — Descriptive text for the operation, using BOM_STANDARD_OPERATIONS or BOM_OPERATION_SEQUENCES text.

Common Use Cases and Queries

Typical applications include determining valid move targets on the shop floor, validating operator-entered next operations, and building routing-sequence reports. A common query selects the next operations for a given job and current sequence:

• Retrieve valid next operations for a job: SELECT wip_entity_id, fm_operation_seq_num, next_operation_code, to_wco_operation_seq_num FROM wsm_copy_next_operations_v WHERE wip_entity_id = :job_id AND fm_operation_seq_num = :current_seq;
• Identify recommended transitions: add WHERE recommended_next_operation = 'Y' to restrict the result to network-recommended paths.
• Report full routing progression per job by ordering on fm_operation_seq_num and to_wco_operation_seq_num.

Because the search term "fm_operation_seq_num" maps directly to the view's from-operation sequence column, users searching that phrase are typically attempting to locate the current operation within a job and enumerate what may follow it.