Search Results quantity_running




Overview
Explore in AI Chat

Overview

APPS.WIP_OPERATIONS_INQ_V is a reporting and inquiry view within the Oracle E-Business Suite Work in Process (WIP) module. It presents a consolidated, denormalized picture of discrete job and repetitive schedule operations, exposing both header-level job context and operation-level quantity states in a single row per operation. The view is defined over the WIP_OPERATIONS table as its primary driver, joined outward to WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_LINES, BOM_DEPARTMENTS, BOM_STANDARD_OPERATIONS, and MFG_LOOKUPS to resolve descriptive attributes such as job name, status meaning, department code, operation code, and line code.

Because it joins both discrete jobs (ENTITY_TYPE = 1) and repetitive schedules (ENTITY_TYPE = 2), the view supports unified inquiry across both manufacturing execution models. Job-specific columns are decoded to NULL for repetitive records, and status is resolved from whichever source applies. This makes the view a convenient, read-only source for operational reporting, shop-floor inquiry screens, and integration extracts that need "where is the work right now" visibility across departments and resources.

Underlying Base Objects

The view references the following documented base objects:

  • WIP_OPERATIONS — the driving table; supplies operation sequence, quantities, and operation identity.
  • WIP_ENTITIES — provides the job or schedule header, entity type, name, and description.
  • WIP_DISCRETE_JOBS — supplies discrete job status and scheduled dates when the entity is a discrete job.
  • WIP_REPETITIVE_SCHEDULES — supplies repetitive schedule status, line, and start dates.
  • WIP_LINES — resolves the repetitive line code.
  • BOM_DEPARTMENTS — resolves the department code and location.
  • BOM_STANDARD_OPERATIONS — resolves the standard operation code.
  • MFG_LOOKUPS — translates status type into a user-facing meaning (status code).

These are accessed via synonyms in the APPS schema. The join design lets the view present a single logical operation record regardless of whether the parent entity is a discrete job or a repetitive schedule.

Key Columns

Common Use Cases and Queries

Typical uses include shop-floor status dashboards, WIP quantity reconciliation, and extracts feeding MES or planning systems. To locate operations with work actively running:

SELECT job_name, operation_seq_num, department_code, quantity_running
FROM   apps.wip_operations_inq_v
WHERE  organization_id = :org_id
AND    quantity_running IS NOT NULL
ORDER BY job_name, operation_seq_num;

Because zero quantities are decoded to NULL, filtering on IS NOT NULL is the correct idiom to find operations with running quantity. A broader remaining-work query sums or lists QUANTITY_REMAINING by department to identify bottlenecks. Joining the view back to WIP_ENTITIES or WIP_DISCRETE_JOBS by WIP_ENTITY_ID supports cross-checks against the operational tables.