Results for “next_operation_code”

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

Overview

The WSM_COPY_ALL_OPERATIONS_V view is a reporting object owned by the APPS schema within the WSM (Shop Floor Management) product of Oracle E-Business Suite. In both release 12.1.1 and 12.2.2 the object carries a VALID status and is documented in the ETRM repository. Its stated purpose is to retrieve all standard operations that exist within an OSFM (Oracle Shop Floor Management) organization, consolidating operation-level attributes together with the operation network relationships that connect them.

Because the view joins operation records to the network definitions that link a source operation to a target operation, it is primarily consumed by integration and reporting logic that needs to enumerate operation sequences in the context of a work order or job flow. Practitioners searching for the to_op_seq_id term typically encounter this view while examining how the "to" (destination) side of an operation network relationship is exposed, a pattern that resembles the row-replication logic used by the related copy operations view.

Underlying Base Objects

The view is defined over two base objects, both referenced as APPS synonyms:

• WSM_COPY_OPERATIONS — supplies the operation master data, including the WIP entity, operation sequence, standard operation code and description, department, and recommended flag.
• WSM_COPY_OP_NETWORKS — supplies the network connectivity, providing the FROM_OP_SEQ_NUM and TO_OP_SEQ_NUM columns that define predecessor/successor links between operations.

The two objects are joined on WIP_ENTITY_ID, and the qualifying condition keeps a row when the operation's sequence number matches either the FROM_OP_SEQ_NUM or the TO_OP_SEQ_NUM of the network record. This produces a union-like expansion in which a single operation can surface through both its inbound and outbound network links.

Key Columns

• WIP_ENTITY_ID — identifies the work order or job to which the operations belong; the common join key across both base objects.
• TO_OP_SEQ_NUM — a constant value of 10 in the documented view text, representing the target operation sequence number placeholder.
• TO_WCO_OP_SEQ_NUM — the operation sequence number of the associated WSM_COPY_OPERATIONS record, presented as the "to" sequence.
• TO_OP_SEQ_ID — the OPERATION_SEQUENCE_ID of the WSM_COPY_OPERATIONS row, exposed under the "to_op_seq_id" alias that matches the user's search term.
• NEXT_OPERATION_CODE — sourced from STANDARD_OPERATION_CODE, identifying the following standard operation.
• OPERATION_DESCRIPTION, STANDARD_OPERATION_ID — descriptive and surrogate identifiers for the standard operation.
• DEPARTMENT_CODE, DEPARTMENT_ID — the department owning the operation.
• RECOMMENDED — flag indicating whether the operation is recommended in the network context.

Common Use Cases and Queries

Typical usage involves enumerating standard operations for an OSFM organization, resolving operation-to-operation links, and extracting the destination operation sequence identifier. A representative query filtering on the sequence identifier is:

• SELECT wip_entity_id, to_op_seq_num, to_op_seq_id, next_operation_code FROM apps.wsm_copy_all_operations_v WHERE wip_entity_id = :p_wip_entity_id;
• SELECT to_op_seq_id, department_code, recommended FROM apps.wsm_copy_all_operations_v WHERE to_op_seq_id = :p_to_op_seq_id;

Integration developers use these results when populating copy or routing logic, verifying that each operation sequence carries the correct destination identifier, and validating network completeness before flows are released to the shop floor.