Search Results total_quantity




Overview
Explore in AI Chat

Overview

WIP_OPEN_SCHEDULES_VAL_V is a validation view owned by the APPS schema in Oracle E-Business Suite (WIP — Work in Process module). It exposes open repetitive schedules, providing a denormalized, read-only projection of repetitive manufacturing schedule data that joins repetitive schedule header information with the associated repetitive item definition. The view is validated and active on both 12.1.1 and 12.2.2.

The view derives its name from its intended usage as a validation/oracle-driven source for open repetitive schedules. Rather than defining a distinct physical entity, it consolidates scheduling quantities, dates, status, and item context so that reports, concurrent programs, and integrations can query open repetitive work without navigating the underlying normalized WIP_REPETITIVE_SCHEDULES and WIP_REPETITIVE_ITEMS tables separately. The user keyword total_quantity is directly material: the view computes TOTAL_QUANTITY at runtime as the product of the daily production rate and the number of processing work days, so it is not a stored column in a base table but a derived expression available only through this view.

Underlying Base Objects

The documented base objects referenced by the view are:

  • WIP_REPETITIVE_ITEMS (SYNONYM) — repetitive item definition key
  • WIP_REPETITIVE_SCHEDULES (SYNONYM) — repetitive schedule header and quantity data

These are accessed in the ETRM metadata as synonyms within APPS. The view text joins the two on three keys — ORGANIZATION_ID, WIP_ENTITY_ID, and LINE_ID — ensuring that the repetitive item row corresponds to the correct schedule row. Crucially, the WHERE clause restricts rows to STATUS_TYPE IN (1, 3, 4, 6), which are the schedule statuses considered open (and related) in WIP repetitive manufacturing. Because the join is an inner join, only schedules with a matching repetitive item are returned.

Key Columns

  • ORGANIZATION_ID — operating unit / inventory organization owning the schedule.
  • REPETITIVE_SCHEDULE_ID — unique identifier of the repetitive schedule.
  • WIP_ENTITY_ID — work-in-process entity key linking the schedule to the WIP entity.
  • PRIMARY_ITEM_ID — inventory item being built (from WIP_REPETITIVE_ITEMS).
  • LINE_ID — production line on which the schedule runs.
  • FIRST_UNIT_START_DATE / FIRST_UNIT_COMPLETION_DATE — start and completion dates of the first unit.
  • LAST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE — start and completion dates of the last unit.
  • TOTAL_QUANTITY — derived as DAILY_PRODUCTION_RATE * PROCESSING_WORK_DAYS; the total planned quantity for the schedule. This is the column most relevant to the user's search.
  • BOM_REVISION — bill of materials revision used by the schedule.
  • STATUS_TYPE — schedule status code (restricted to 1, 3, 4, 6).
  • PROCESSING_WORK_DAYS — count of working days over which production is scheduled.
  • DAILY_PRODUCTION_RATE — units produced per working day.

Common Use Cases and Queries

Typical scenarios include reporting on open repetitive schedule load by organization or line, validating available capacity, and feeding planning extracts. A representative query returning total quantity per line is:

  • SELECT organization_id, line_id, repetitive_schedule_id, total_quantity, status_type FROM apps.wip_open_schedules_val_v WHERE organization_id = :org_id AND status_type = 3;

Because TOTAL_QUANTITY is computed, consumers requiring the raw drivers can select DAILY_PRODUCTION_RATE and PROCESSING_WORK_DAYS alongside it for reconciliation. The view is best treated as a reporting and validation source; it carries no DML capability and should not be used for transactional updates. For date-sensitive analysis, filter on the FIRST_UNIT and LAST_UNIT date columns to isolate schedules active within a given window.