Search Results processing_work_days




Overview
Explore in AI Chat

Overview

WIP_JOBS_AND_SCHEDULES_V is a documented Oracle E-Business Suite view owned by the APPS schema and classified as VALID in the Work in Process (WIP) product. As its description states, the view provides summary data for jobs and schedules, consolidating discrete job and repetitive schedule information into a single, uniformly shaped result set. The view is built on a UNION-style DECODE pattern over WIP_ENTITIES, which is the master table for all work orders, and it uses ENTITY_TYPE to discriminate between discrete jobs (ENTITY_TYPE = 1), repetitive schedules (ENTITY_TYPE = 2), and what is treated as an additional discrete-style job category (ENTITY_TYPE = 3). The result is a normalized projection in which each row represents a single job or schedule with consistent column semantics regardless of entity type. This makes the view a convenient reporting and integration object: rather than joining the discrete job and repetitive schedule tables separately with conditional logic, consumers can query one view and filter by ENTITY_TYPE. The view also exposes repetitive-specific attributes such as PROCESSING_WORK_DAYS and DAILY_PRODUCTION_RATE, which are NULL for discrete jobs, and discrete-specific attributes such as JOB_TYPE, which is likewise NULL for repetitive schedules.

Underlying Base Objects

The documented ETRM metadata lists four referenced base objects, each exposed through a synonym in the APPS schema: WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_LINES, and WIP_REPETITIVE_SCHEDULES. The view is defined with outer joins (denoted by the (+) operator) so that WIP_ENTITIES drives the result set and the type-specific tables are attached only when a matching row exists. WIP_DISCRETE_JOBS is joined on WIP_ENTITY_ID and ORGANIZATION_ID, WIP_REPETITIVE_SCHEDULES is joined on WIP_ENTITY_ID, and WIP_LINES is joined to WIP_REPETITIVE_SCHEDULES on LINE_ID. Because WIP_LINES is joined only through the repetitive schedule path, LINE_ID and LINE_CODE are populated for repetitive entities and are NULL for discrete jobs.

Key Columns

  • WIP_ENTITY_ID / ORGANIZATION_ID — Primary identifiers linking the row to the WIP entity and the inventory organization.
  • WIP_ENTITY_NAME / DESCRIPTION — Suppressed (set to NULL via DECODE) for repetitive schedules, where ENTITY_TYPE = 2; populated for discrete jobs.
  • ENTITY_TYPE — Discriminator column: 1 and 3 behave as discrete jobs, 2 indicates a repetitive schedule.
  • STATUS_TYPE — Sourced from WIP_DISCRETE_JOBS for discrete entities and from WIP_REPETITIVE_SCHEDULES for repetitive entities.
  • TOTAL_QUANTITY — For discrete jobs, the START_QUANTITY from WIP_DISCRETE_JOBS. For repetitive schedules, it is calculated as DAILY_PRODUCTION_RATE multiplied by PROCESSING_WORK_DAYS.
  • DAILY_PRODUCTION_RATE — Repetitive-only attribute defining units produced per working day.
  • PROCESSING_WORK_DAYS — Repetitive-only attribute representing the number of processing work days in the schedule; central to the TOTAL_QUANTITY computation and a frequent search term for this object.
  • JOB_TYPE — Discrete-only classification of the job.
  • SCHEDULED_START_DATE — From WIP_DISCRETE_JOBS for discrete entities and from FIRST_UNIT_START_DATE for repetitive schedules.
  • REPETITIVE_SCHEDULE_ID / LINE_ID / LINE_CODE — Repetitive scheduling identifiers and production line references.

Common Use Cases and Queries

The view is typically used for shop-floor reporting, capacity analysis, and interface extracts that must treat jobs and schedules uniformly. A representative query returning all open work with quantities and dates is:

SELECT wip_entity_id, organization_id, wip_entity_name, entity_type, status_type, total_quantity, daily_production_rate, processing_work_days, scheduled_start_date, line_code FROM apps.wip_jobs_and_schedules_v WHERE organization_id = :org_id ORDER BY scheduled_start_date;

To isolate repetitive schedules and compute derived quantities by processing work days, filter on ENTITY_TYPE = 2 and inspect PROCESSING_WORK_DAYS alongside DAILY_PRODUCTION_RATE. To isolate discrete jobs, filter on ENTITY_TYPE IN (1,3) and use JOB_TYPE. Because the view is a read-only projection over the WIP base tables, it is safe for reporting joins to WIP_ENTITIES and inventory item master data, but it should not be treated as an update target.