Search Results wip_operations_inq_v




Overview
Explore in AI Chat

Overview

WIP_OPERATIONS_INQ_V is a read-only Oracle EBS Work in Process (WIP) inquiry view owned by the APPS schema. It exposes operation-level in-queue quantity information for both discrete jobs and repetitive schedules, simplifying the retrieval of shop floor status information that would otherwise require joining WIP_OPERATIONS against WIP_ENTITIES, BOM_DEPARTMENTS, and other reference tables. The view maintains a status of VALID across Oracle EBS 12.1.1 and 12.2.2 and is documented under the WIP product module. Its description — "In-queue quantities for operations" — reflects its primary purpose: presenting the quantity balances at each routing operation for a job or schedule, alongside contextual information such as department, line, job name, and status code.

The view is designed for inquiry and reporting rather than transactional DML. It provides a denormalized perspective on WIP operation quantities, allowing report developers, form developers, and integration builders to query operation status directly without reproducing the underlying joins.

Underlying Base Objects

The view is defined over eight documented base objects:

  • WIP_OPERATIONS — the driving table (aliased WO1, with self-join WO3) holding scheduled, in-queue, running, waiting-to-move, rejected, scrapped, and completed quantities per operation sequence.
  • WIP_ENTITIES — supplies job name, description, entity type, and primary item.
  • WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES — provide status type, scheduled start dates, repetitive schedule IDs, and line references.
  • BOM_DEPARTMENTS and BOM_STANDARD_OPERATIONS — supply department code, location, and standard operation code.
  • WIP_LINES — provides the repetitive line code.
  • MFG_LOOKUPS — resolves status codes into user-facing meanings.

The view leverages DECODE logic to normalize status between discrete and repetitive entities (entity type 2 signifies repetitive). The QUANTITY_REMAINING calculation aggregates downstream operation quantities via a self-join on WIP_OPERATIONS (WO3), providing a cumulative remaining quantity for the operation.

Key Columns

Common Use Cases and Queries

This view supports shop floor reporting, WIP status dashboards, and integrations requiring operation-level quantity visibility. Typical uses include identifying operations with pending in-queue quantities, reporting job progress against routing, and tracking repetitive line activity.

Representative query retrieving operation quantities for an organization:

  • SELECT job_name, operation_seq_num, department_code, status_code, quantity_in_queue, quantity_running, quantity_remaining FROM wip_operations_inq_v WHERE organization_id = :org_id AND status_type < 4 ORDER BY job_name, operation_seq_num;

Because zero quantities are stored as NULL, consumers should apply NVL in aggregated or arithmetic usage. The view should not be used for DML; updates must target the base WIP_OPERATIONS table.