Results for “quantity_scrapped”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.WIP_REP_QUANTITY_SCRAPPED_V view is a Work in Process (WIP) reporting object that exposes the aggregate quantity scrapped against repetitive schedules. It presents a pre-summarized result set grouped by repetitive schedule and organization, allowing reports, concurrent programs, and integrations to obtain scrapped quantities without repeatedly scanning and aggregating the transaction-level WIP_OPERATIONS table.

In Oracle EBS 12.1.1 and 12.2.2, repetitive manufacturing uses schedules (rather than discrete jobs) to drive production. Scrap attributable to those schedules is recorded at the operation level in WIP_OPERATIONS. Because a single repetitive schedule typically spans many operations and many scrapped transactions, the raw data is not directly useful for schedule-level reporting. This view resolves that problem by collapsing the detail into one row per REPETITIVE_SCHEDULE_ID and ORGANIZATION_ID, with the summed QUANTITY_SCRAPPED value.

The object is a simple, non-materialized view owned by the APPS schema and is reported as VALID. Its role is purely read-oriented: it feeds scrap analysis, yield/efficiency reporting, cost roll-up review, and any integration that needs a schedule-level scrap figure. It exposes no DML surface of its own; data originates entirely from the underlying operation records. Typical consumers include custom reports, Discoverer workbooks, OBIEE/BIP extracts, and interface programs that reconcile repetitive manufacturing scrap.

Underlying Base Objects

The view is defined over a single referenced base object, WIP_OPERATIONS, accessed through a synonym. The documented view text is:

• SELECT REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID, SUM(QUANTITY_SCRAPPED) QUANTITY_SCRAPPED FROM WIP_OPERATIONS WHERE REPETITIVE_SCHEDULE_ID IS NOT NULL GROUP BY REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID

Three structural facts follow from this definition. First, the view is a pure aggregation: it contains no joins to repetitive schedule headers, job definitions, or item masters, so it returns only identifiers and a summed quantity. Second, WIP_OPERATIONS is a synonym resolving to the APPS-owned operations table that stores per-operation transaction activity, including the QUANTITY_SCRAPPED column. Third, the WHERE REPETITIVE_SCHEDULE_ID IS NOT NULL predicate is the filter that restricts output to repetitive schedule activity, excluding discrete job operations whose repetitive schedule identifier is null. The GROUP BY on REPETITIVE_SCHEDULE_ID and ORGANIZATION_ID establishes the grain of the result.

Because the view depends directly on WIP_OPERATIONS, its results change as operations are completed, scrap is recorded, or records are purged or archived. There is no caching layer, and no additional base objects are documented for this view.

Key Columns

• REPETITIVE_SCHEDULE_ID — Identifier of the repetitive schedule whose operations contributed scrap. This is the primary grouping key and the column most frequently used in joins to repetitive schedule header objects.
• ORGANIZATION_ID — The inventory organization in which the schedule and its operations reside. It is the second grouping key, ensuring that the same schedule identifier is not conflated across organizations.
• QUANTITY_SCRAPPED — The summed scrapped quantity for the schedule/organization combination, produced by SUM(QUANTITY_SCRAPPED) over the qualifying WIP_OPERATIONS rows.

Common Use Cases and Queries

The most common requirement is retrieving the total scrapped quantity for a specific repetitive schedule, which is the exact scenario implied by the search term repetitive_schedule_id. A representative query:

• SELECT repetitive_schedule_id, organization_id, quantity_scrapped FROM apps.wip_rep_quantity_scrapped_v WHERE repetitive_schedule_id = :p_schedule_id AND organization_id = :p_org_id;

For organization-wide scrap analysis across all repetitive schedules:

• SELECT organization_id, SUM(quantity_scrapped) total_scrapped FROM apps.wip_rep_quantity_scrapped_v GROUP BY organization_id;

For a ranked view of the highest-scrap schedules:

• SELECT repetitive_schedule_id, organization_id, quantity_scrapped FROM apps.wip_rep_quantity_scrapped_v ORDER BY quantity_scrapped DESC;

Because only identifiers and a summed quantity are exposed, users should expect to join this view to repetitive schedule header data to obtain item, line, or date context. Its simplicity makes it a reliable, low-overhead building block for repetitive manufacturing scrap reporting in Oracle EBS 12.1.1 and 12.2.2.