Results for “operation_code”

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

Overview

WSM_NEXT_OPERATIONS_V is an APPS-owned database view in Oracle E-Business Suite that exposes all valid next operations for a discrete job, derived from the BOM operation network (routing) rather than from a manually assigned sequence alone. It is a core data access object for the WSM – Shop Floor Management module, and it is used wherever shop floor logic must determine which operation may legitimately follow the current one on a job. Typical consumers include Shop Floor Management "Move" and next-operation inference logic, WIP-related inquiry screens, move transaction validation, and custom reporting or integration interfaces that need to resolve the successor operation on a routing network.

The view is documented as VALID in both 12.1.1 and 12.2.2 and is defined entirely over SYNONYM objects residing in APPS. Its purpose statement is specific: it returns all valid next operations for a job based on the network routing. This distinguishes it from simpler views that merely read WIP_OPERATIONS in sequence order, because the successor is determined by BOM_OPERATION_NETWORKS relationships qualified by effectivity and disable dates.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

• WIP_DISCRETE_JOBS — supplies the job context, including WIP_ENTITY_ID, JOB_TYPE, PRIMARY_ITEM_ID, ROUTING_REFERENCE_ID, COMMON_ROUTING_SEQUENCE_ID, and ROUTING_REVISION_DATE.
• WIP_OPERATIONS — joined twice (aliases WO and WO2) to provide the current operation and the source row used to derive the next sequence number.
• BOM_OPERATION_SEQUENCES — the valid operations on the routing, with effectivity and disable dates and the department assignment.
• BOM_OPERATIONAL_ROUTINGS — links the assembly item to its routing sequence.
• BOM_OPERATION_NETWORKS — defines the network precedence relationships between operations.
• BOM_STANDARD_OPERATIONS — joined twice (BSO1, BSO2) for the current and next operation codes.
• BOM_DEPARTMENTS — supplies the department code for the next operation.
• WSM_PARAMETERS — supplies OP_SEQ_NUM_INCREMENT, used when no explicit next sequence exists.

Effectivity logic is applied using NVL(WDJ.ROUTING_REVISION_DATE, SYSDATE) compared against BOS.EFFECTIVITY_DATE and BOS.DISABLE_DATE, ensuring only operations valid for the job's routing revision are returned. Department and standard operation joins use outer joins where the operation may not be tied to a standard operation.

Key Columns

• WIP_ENTITY_ID — the job identifier, used to scope the query to a single discrete job.
• OPERATION_SEQ_NUM — the current operation sequence number on the job.
• TO_OPERATION_SEQ_NUM — the successor operation sequence number. This is the column most frequently searched and referenced; it is deliberately cast with TO_NUMBER(NULL) so the column returns a NUMBER datatype, then populated from WO2.OPERATION_SEQ_NUM plus NVL(WP.OP_SEQ_NUM_INCREMENT, 10).
• BOS.OPERATION_SEQ_NUM — the sequence number of the next operation as defined on the routing.
• OPERATION_SEQUENCE_ID — the operation sequence identifier for the current and next operations.
• BSO1.OPERATION_CODE / BSO2.OPERATION_CODE — the standard operation codes for the current and next operations.
• OPERATION_DESCRIPTION, STANDARD_OPERATION_ID — description and standard operation reference for the next operation.
• DEPARTMENT_CODE, DEPARTMENT_ID — the department responsible for the next operation.

Common Use Cases and Queries

The primary use case is resolving the next valid operation for a job during shop floor move processing, including situations where the routing network allows branching. A representative query for a specific job is:

• SELECT wip_entity_id, operation_seq_num, to_operation_seq_num, operation_description, department_code FROM apps.wsm_next_operations_v WHERE wip_entity_id = :p_wip_entity_id ORDER BY to_operation_seq_num;
• To list all successors for a particular operation: SELECT to_operation_seq_num FROM apps.wsm_next_operations_v WHERE wip_entity_id = :p_wip_entity_id AND operation_seq_num = :p_operation_seq_num;
• To join the view to WIP_OPERATIONS for validation of the target operation before a move: SELECT n.to_operation_seq_num, o.status_type FROM apps.wsm_next_operations_v n, apps.wip_operations o WHERE n.wip_entity_id = :p_wip_entity_id AND o.wip_entity_id = n.wip_entity_id AND o.operation_seq_num = n.to_operation_seq_num;

Because the view derives its next-operation values from the BOM network rather than from a static increment, integration and reporting code should not assume a fixed sequence gap; OP_SEQ_NUM_INCREMENT from WSM_PARAMETERS provides a fallback when the network does not define an explicit successor. The view should be queried with a WIP_ENTITY_ID predicate for performance, since the underlying joins span the full BOM routing and network tables.