Search Results cumulative_scrap_quantity

Overview

APPS.WIP_CUMULATIVE_SCRAP_V is a Work in Process (WIP) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes cumulative scrap information at the work order operation level, computing the running total of quantities scrapped across the sequential operations of a discrete job or repetitive schedule. The view is commonly reached when searching for the term cumulative_scrap_quantity, since that column originates on WIP_OPERATIONS and is surfaced here for consumption by forms, reports, and integration logic.

Its principal design characteristic is that it is a fallback view. The driving filter is WO.CUMULATIVE_SCRAP_QUANTITY IS NULL, meaning the view only returns rows for which the stored cumulative scrap value on the operation has not yet been populated. Where the base column is null, the view derives the running total analytically using a window function. This makes the view useful during data-repair, migration, or interface scenarios in which the maintained cumulative value is absent and must be reconstructed from the individual operation-level scrap quantities.

Underlying Base Objects

The view is defined in the APPS schema over three synonyms, each resolving to the corresponding WIP base table:

• WIP_OPERATIONS (WO) — the primary driving object, supplying ROWID, WIP_ENTITY_ID, CUMULATIVE_SCRAP_QUANTITY, QUANTITY_SCRAPPED, OPERATION_SEQ_NUM, ORGANIZATION_ID, and REPETITIVE_SCHEDULE_ID.
• WIP_DISCRETE_JOBS (WDJ) — joined via an EXISTS subquery to confirm the work order is an open discrete job, and referenced by WIP_ENTITY_ID.
• WIP_REPETITIVE_SCHEDULES (WRS) — joined via a UNION ALL EXISTS branch to confirm the work order is an open repetitive schedule, also keyed on WIP_ENTITY_ID.

The EXISTS predicate enforces that only active work orders are considered: both subqueries exclude STATUS_TYPE values 12, 5, and 7, which correspond to closed, cancelled, and complete statuses in WIP. The UNION ALL allows a single WIP_ENTITY_ID to be matched against either discrete jobs or repetitive schedules, so the view serves both manufacturing execution models without duplicating rows.

Key Columns

• ROW_ID — the ROWID of the underlying WIP_OPERATIONS row, aliased for use in update/correction processes.
• WIP_ENTITY_ID — the work order identifier, common to discrete jobs and repetitive schedules.
• CUMULATIVE_SCRAP_QUANTITY — the persisted cumulative scrap quantity on the operation; because of the driving filter, this is null for every returned row.
• SUM_OF_QTY_SCRAPPED — the computed running total of QUANTITY_SCRAPPED, partitioned by WIP_ENTITY_ID, ORGANIZATION_ID, and NVL(REPETITIVE_SCHEDULE_ID,-9999), ordered by OPERATION_SEQ_NUM, summing all rows strictly preceding the current operation (ROWS BETWEEN UNBOUNDED PRECEDING AND 1 PRECEDING).

Common Use Cases and Queries

The view supports scrap reconciliation, backfill of null cumulative values, and validation of operation sequencing. A typical query lists derived running totals per work order:

• SELECT WIP_ENTITY_ID, ROW_ID, SUM_OF_QTY_SCRAPPED FROM APPS.WIP_CUMULATIVE_SCRAP_V ORDER BY WIP_ENTITY_ID, ROW_ID;
• SELECT WIP_ENTITY_ID, SUM(NVL(SUM_OF_QTY_SCRAPPED,0)) TOTAL_SCRAP FROM APPS.WIP_CUMULATIVE_SCRAP_V GROUP BY WIP_ENTITY_ID;

Because only operations with a null CUMULATIVE_SCRAP_QUANTITY are returned, the view is idiomatically used as the source for corrective updates: the derived SUM_OF_QTY_SCRAPPED can be written back to WIP_OPERATIONS.CUMULATIVE_SCRAP_QUANTITY using ROW_ID as the correlation key, after which the view naturally returns no further rows for that operation.