Search Results wsm_wip_operations_v

Overview

WSM_WIP_OPERATIONS_V is an Oracle E-Business Suite view owned by the APPS schema and categorized under the WSM (Shop Floor Management) product family. It exposes work-in-process operation-level detail, one row per routing operation attached to a discrete job or repetitive schedule. The view is the operational layer between the WIP execution engine and the shop floor user interfaces, reports, and integration programs that consume operation status and quantity information.

Because the view carries a dedicated QUANTITY_SCRAPPED column alongside the other quantity buckets, it is the canonical source for scrap reporting and yield analysis at the operation level. It serves as a read-oriented projection over the WIP_OPERATIONS base table, allowing Oracle's own forms, concurrent programs, and customer-built reports to query operation data through a stable, named interface rather than joining directly to the WIP entity tables. This indirection means the view can be described as a simplified access path: it avoids the more elaborate multi-table joins used by the Oracle Work in Process operational views, while retaining the fields most frequently referenced by shop floor transactions and reporting.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: the synonym WIP_OPERATIONS. The view text confirms this relationship directly — the SELECT list and FROM clause draw every column from WIP_OPERATIONS with no joins, unions, aggregations, or filters. WIP_OPERATIONS is the transactional table that stores the routing steps of a work order; it is a child of the WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES entities and a sibling of the WIP_OPERATIONS table's related instruction and resource tables. Because WSM_WIP_OPERATIONS_V performs no filtering itself, consumers must supply their own predicates, typically on WIP_ENTITY_ID, ORGANIZATION_ID, or OPERATION_SEQ_NUM, to isolate the rows they need.

Key Columns

• WIP_ENTITY_ID — Identifier of the parent discrete job or repetitive schedule; the primary join key back to the work order header.
• ORGANIZATION_ID — Owning inventory organization; required for multi-org and security-constrained queries.
• OPERATION_SEQ_NUM / OPERATION_SEQUENCE_ID — The routing step number and its surrogate primary key; OPERATION_SEQ_NUM drives the user-visible sequence.
• REPETITIVE_SCHEDULE_ID — Populated when the operation belongs to a repetitive schedule rather than a discrete job.
• DEPARTMENT_ID / STANDARD_OPERATION_ID / DESCRIPTION — Where the work is performed and the standard operation the step is based on.
• SCHEDULED_QUANTITY — Quantity planned for the operation.
• QUANTITY_IN_QUEUE, QUANTITY_RUNNING, QUANTITY_WAITING_TO_MOVE, QUANTITY_REJECTED, QUANTITY_SCRAPPED, QUANTITY_COMPLETED — The operation quantity buckets; QUANTITY_SCRAPPED records units lost to scrap at this step and is the primary reason users search this view.
• FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE — Actual execution timestamps used for lead-time and performance measurement.
• PREVIOUS_OPERATION_SEQ_NUM, NEXT_OPERATION_SEQ_NUM, COUNT_POINT_TYPE, BACKFLUSH_FLAG, MINIMUM_TRANSFER_QUANTITY — Routing control attributes governing flow and lot movement.
• PRE_SPLIT_QUANTITY, OPERATION_YIELD_ENABLED, OPERATION_YIELD — Split and yield-tracking columns used in yield analysis.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield storage, available for customer-defined reporting.

Common Use Cases and Queries

Typical consumers include scrap and yield dashboards, shop floor workbench extensions, MES integrations, and period-end operations reviews. Because the view is defined over WIP_OPERATIONS only, queries must supply organization and work order context.

Scrap by operation for a given job:

• SELECT operation_seq_num, description, quantity_scrapped, quantity_completed FROM apps.wsm_wip_operations_v WHERE organization_id = :org_id AND wip_entity_id = :wip_entity_id ORDER BY operation_seq_num;

Largest scrap contributors in an organization:

• SELECT wip_entity_id, operation_seq_num, quantity_scrapped FROM apps.wsm_wip_operations_v WHERE organization_id = :org_id AND quantity_scrapped > 0 ORDER BY quantity_scrapped DESC;

Operation status for in-process work:

• SELECT wip_entity_id, operation_seq_num, quantity_in_queue, quantity_running, quantity_waiting_to_move, quantity_completed FROM apps.wsm_wip_operations_v WHERE organization_id = :org_id AND quantity_running > 0;

Repetitive schedule yield review:

• SELECT operation_seq_num, quantity_completed, quantity_scrapped, operation_yield FROM apps.wsm_wip_operations_v WHERE repetitive_schedule_id = :schedule_id ORDER BY operation_seq_num;

Joining to WIP_ENTITIES or WIP_DISCRETE_JOBS through WIP_ENTITY_ID provides work order numbers, assembly items, and status, enabling consolidated scrap-rate reporting. Queries should always include ORGANIZATION_ID to satisfy multi-org access and to leverage the organization leading index on WIP_OPERATIONS.