Search Results wip_operations_v




Overview
Explore in AI Chat

Overview

WIP_OPERATIONS_V is a foreign-key descriptive view owned by the APPS schema in Oracle E-Business Suite, belonging to the Work in Process (WIP) product family. Its stated purpose is to supply foreign-key data for WIP_OPERATIONS, the base table that stores the individual routing operations defined against discrete jobs and repetitive schedules. The view joins the transactional operation rows to the appropriate standard operation and department definitions so that reports and integrations can resolve coded identifiers into human-readable values in a single query.

Because WIP_OPERATIONS itself carries only numeric foreign keys for the standard operation and the department, consumers must otherwise perform multiple lookups. WIP_OPERATIONS_V collapses those lookups into one row per operation, exposing OPERATION_CODE from BOM_STANDARD_OPERATIONS and DEPARTMENT_CODE plus LOCATION_ID from BOM_DEPARTMENTS. It also exposes lookup meanings resolved through MFG_LOOKUPS and returns the COUNT_POINT_TYPE column translated into COUNT_POINT_FLAG and AUTOCHARGE_FLAG, which is convenient for shop-floor reporting where the raw type code is not meaningful.

The view is read-only and derived entirely from base tables; it defines no independent data. This makes it suitable for ad hoc reporting, Oracle Discoverer worksheets, and interface extracts that need operation context without writing the join logic repeatedly.

Underlying Base Objects

The view is defined over five referenced objects as documented for release 12.2.2: WIP_OPERATIONS (synonym), BOM_STANDARD_OPERATIONS (synonym), BOM_DEPARTMENTS (synonym), MFG_LOOKUPS (view), and PER_ALL_PEOPLE_F (synonym). The driving table is WIP_OPERATIONS, aliased WO, which supplies WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID, REPETITIVE_SCHEDULE_ID, and all quantity and date columns.

BOM_STANDARD_OPERATIONS, aliased BSO, is joined to provide OPERATION_CODE, while BOM_DEPARTMENTS, aliased BD, supplies DEPARTMENT_CODE and LOCATION_ID. MFG_LOOKUPS, aliased LU1, resolves the shutdown type code into a MEANING value. PER_ALL_PEOPLE_F is referenced to support creation and update audit columns such as CREATED_BY and LAST_UPDATED_BY, consistent with standard EBS audit patterns.

All APPS synonyms point to the corresponding base tables in their owning schemas. Because the view depends on PER_ALL_PEOPLE_F and other base objects that change with patches, recompilation status should be verified after upgrades; the ETRM record lists the view as VALID.

Key Columns

Identification columns include WIP_ENTITY_ID, OPERATION_SEQUENCE_ID, OPERATION_SEQ_NUM, STANDARD_OPERATION_ID, ORGANIZATION_ID, and REPETITIVE_SCHEDULE_ID. Descriptive columns include OPERATION_CODE, DEPARTMENT_CODE, LOCATION_ID, DESCRIPTION, and LONG_DESCRIPTION. Quantity columns cover SCHEDULED_QUANTITY and the stage buckets QUANTITY_IN_QUEUE, QUANTITY_RUNNING, QUANTITY_WAITING_TO_MOVE, QUANTITY_REJECTED, QUANTITY_SCRAPPED, and QUANTITY_COMPLETED.

Notably, the view wraps each quantity column in DECODE against zero, returning NULL when the value is zero. Consumers should therefore treat a NULL result as a zero quantity and apply NVL in arithmetic expressions. Scheduling columns include FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE, DATE_LAST_MOVED, and the derived PROGRESS_PERCENTAGE. Routing control columns include PREVIOUS_OPERATION_SEQ_NUM, NEXT_OPERATION_SEQ_NUM, MINIMUM_TRANSFER_QUANTITY, BACKFLUSH_FLAG, OPERATION_YIELD, OPERATION_YIELD_ENABLED, CUMULATIVE_SCRAP_QUANTITY, and OPERATION_COMPLETED. Fifteen ATTRIBUTE columns and a ROW_ID column are also exposed.

Common Use Cases and Queries

Typical scenarios include listing open operations for a discrete job, monitoring queue and running quantities by department, and extracting operation detail for interfaces. A representative query follows.

  • Operations for a job:

    SELECT operation_seq_num, operation_code, department_code, scheduled_quantity, NVL(quantity_running,0) qty_running, NVL(quantity_completed,0) qty_completed FROM wip_operations_v WHERE wip_entity_id = :p_wip_entity_id ORDER BY operation_seq_num;

  • Department load:

    SELECT department_code, COUNT(*) ops, SUM(NVL(quantity_in_queue,0) + NVL(quantity_running,0)) wip_qty FROM wip_operations_v WHERE organization_id = :p_org_id GROUP BY department_code;

  • Yield and scrap analysis:

    SELECT operation_code, operation_yield, NVL(cumulative_scrap_quantity,0) scrap FROM wip_operations_v WHERE wip_entity_id = :p_wip_entity_id AND operation_yield_enabled = 'Y';

Always join back to WIP_DISCRETE_JOBS or WIP_ENTITIES for job-level context, and filter by ORGANIZATION_ID to control the operating unit scope.