Search Results scrap_quantity

Overview

WIP_BIS_PROD_ASSY_YIELD_V is an Oracle E-Business Suite view owned by the APPS schema and registered as VALID under the Work in Process (WIP) product. Its purpose, as documented in the ETRM, is to report total and scrapped quantity at a specific organization and date. The view functions as a reporting and analytics layer over the production assembly yield data, aggregating completed and scrapped quantities across a wide set of business dimensions including ledger, legal entity, operating unit, inventory organization, work order, category, item, and geography. Because the object is a view rather than a base table, it exposes no independent storage; it is query-only and is intended for the Business Intelligence System (BIS) and related WIP reporting consumers.

Underlying Base Objects

The view is defined over a single documented base object: the synonym WIP_BIS_PROD_ASSY_YIELD, referenced internally with the alias WBPAY. The defining query filters on WBPAY.EXISTING_FLAG = 1, which restricts output to current (non-obsolete) yield records, and then aggregates using GROUP BY across the full set of dimensional columns preceding the measures. Two measures are produced through SUM(): COMPLETED_QUANTITY and SCRAP_QUANTITY, and TOTAL_QUANTITY is derived as the sum of the two. All dimensional attributes — ledger, legal entity, operating unit, organization, WIP entity, category, item, location, area, country, region, and the period/date columns — participate in the GROUP BY, meaning each output row represents a unique combination of those dimensions.

Key Columns

• LEDGER_ID, LEDGER_NAME — identify the accounting ledger associated with the transaction. Note the view text references SET_OF_BOOKS_ID and SET_OF_BOOKS_NAME, which map to these documented column names.
• LEGAL_ENTITY_ID, OPERATING_UNIT_ID, ORGANIZATION_ID — organizational hierarchy identifiers for legal entity, operating unit, and inventory organization.
• WIP_ENTITY_ID — the discrete job or work order identifier that produced the yield.
• CATEGORY_ID, INVENTORY_ITEM_ID — the item and its category for the assembly being tracked.
• LOCATION_ID, AREA_CODE, COUNTRY_CODE, REGION_CODE — geographic attributes of the reporting location.
• TRANSACTION_DATE — the date of the completion or scrap transaction.
• PERIOD_SET_NAME, PERIOD_YEAR, PERIOD_QUARTER, PERIOD_MONTH — accounting period dimensions enabling period-based rollups. The view text names these YEAR, QUARTER, and MONTH.
• COMPLETED_QUANTITY, SCRAP_QUANTITY, TOTAL_QUANTITY — the core yield measures. SCRAP_QUANTITY is the cumulative scrapped amount for the dimensional combination; TOTAL_QUANTITY equals completed plus scrapped.

Common Use Cases and Queries

The view is typically used to analyze production yield efficiency, scrap rates, and period-over-period scrap trends. A common query retrieves scrap quantities by organization and accounting period:

• SELECT ORGANIZATION_NAME, PERIOD_YEAR, PERIOD_MONTH, SUM(COMPLETED_QUANTITY) completed, SUM(SCRAP_QUANTITY) scrap, SUM(TOTAL_QUANTITY) total FROM WIP_BIS_PROD_ASSY_YIELD_V GROUP BY ORGANIZATION_NAME, PERIOD_YEAR, PERIOD_MONTH ORDER BY 2,3;
• Scrap percentage analysis by item: SELECT INVENTORY_ITEM_NAME, SUM(SCRAP_QUANTITY)/NULLIF(SUM(TOTAL_QUANTITY),0)*100 scrap_pct FROM WIP_BIS_PROD_ASSY_YIELD_V WHERE TRANSACTION_DATE BETWEEN :from_date AND :to_date GROUP BY INVENTORY_ITEM_NAME;
• Work-order-level yield review: SELECT WIP_ENTITY_ID, COMPLETED_QUANTITY, SCRAP_QUANTITY FROM WIP_BIS_PROD_ASSY_YIELD_V WHERE WIP_ENTITY_ID = :entity_id;

Because the view already aggregates and filters for existing records, it is well suited to direct reporting and ETL extraction without additional grouping on the base synonym.