Results for “wip_scrap_values”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The WIP_SCRAP_VALUES table, owned by the WIP (Work in Process) schema, stores the cost information associated with assembly scrap transactions in Oracle EBS 12.1.1 and 12.2.2. It is the authoritative repository for the monetary breakdown of material scrapped from a work order or flow schedule, capturing how each scrap event decomposes across cost elements prior to and during cost roll-up. The table is populated when scrap transactions are processed through Work in Process and the corresponding material movement is recorded.
From a Data Vault modeling perspective, the mined foreign key structure classifies WIP_SCRAP_VALUES heuristically as a link table — a transactional table that records a relationship between a material transaction and one or more cost dimension entities (cost element and cost update). Because the table also carries descriptive measures such as COST_ELEMENT_VALUE, a practitioner may alternately model it as a link with an attached satellite. Treating it as a link is the recommended heuristic given its composite foreign keys and transactional grain.
Key Information Stored
The table contains 14 documented columns. The most operationally significant are:
- TRANSACTION_ID — References the originating scrap transaction in MTL_MATERIAL_TRANSACTIONS. This is the central business identifier tying cost values back to the physical material movement.
- LEVEL_TYPE — Identifies the level of the work order structure (or accumulation level) at which the cost was recorded, such as operation or assembly level.
- COST_ELEMENT_ID — References CST_COST_ELEMENTS, identifying the cost element (e.g., material, resource, overhead, outside processing) to which the value applies.
- COST_UPDATE_ID — References CST_COST_UPDATES, linking the scrap value to the specific cost update event or cost set against which it was valued.
- COST_ELEMENT_VALUE — The monetary amount of the scrap value attributed to the identified cost element and level.
- LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns supporting audit and change tracking.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request and program that created or last updated the row.
The primary key WIP_SCRAP_VALUES_PK is a composite of TRANSACTION_ID, LEVEL_TYPE, COST_ELEMENT_ID, and COST_UPDATE_ID. The unique index WIP_SCRAP_VALUES_U1 mirrors the same column set, making these four columns the documented business-key candidates in addition to serving as the surrogate composite key. Because the key includes COST_ELEMENT_ID and COST_UPDATE_ID, each scrap transaction can carry multiple rows — one per cost element and cost-update context.
Common Use Cases and Queries
Typical uses include scrap cost analysis, work order variance reporting, and reconciliation of WIP scrap activity to the general ledger. A representative query joins the table to material transactions to report scrap costs by cost element:
- Summing COST_ELEMENT_VALUE by COST_ELEMENT_ID to determine the cost composition of scrap across a date range.
- Joining to MTL_MATERIAL_TRANSACTIONS on TRANSACTION_ID to retrieve item, organization, and transaction quantity context.
- Joining to CST_COST_ELEMENTS and CST_COST_UPDATES to resolve cost element names and cost set identifiers for reporting.
- Correlating scrap values with WIP cost distributions to validate that scrapped assemblies were relieved from WIP at the correct valuation.
For example, scrap value by transaction and element can be obtained by joining WIP_SCRAP_VALUES to MTL_MATERIAL_TRANSACTIONS on TRANSACTION_ID and grouping by COST_ELEMENT_ID. Because the table is highly transactional, queries should always be filtered by date or transaction identifiers to avoid full scans.
Related Objects
The most significant related objects, derived from the documented foreign keys, are:
- MTL_MATERIAL_TRANSACTIONS — joined on TRANSACTION_ID; provides the underlying scrap material movement and item context.
- CST_COST_ELEMENTS — joined on COST_ELEMENT_ID; supplies cost element definitions and names.
- CST_COST_UPDATES — joined on COST_UPDATE_ID; identifies the cost update or cost set used for valuation.
- WIP_TRANSACTIONS / WIP_TRANSACTION_ACCOUNTS — related WIP transactional and accounting tables referencing the same transaction flow.
- CST_TRANSACTION_COST_DETAILS — the cost detail layer into which scrap cost values ultimately feed.
These relationships position WIP_SCRAP_VALUES as the cost-detail bridge between WIP material movements and the cost management subsystem.
-
Cost information for assembly scrap transactions
-
Cost information for assembly scrap transactions
-
TABLE: WIP.WIP_SCRAP_VALUES 12.2.2
-
TABLE: WIP.WIP_SCRAP_VALUES 12.1.1
-
VIEW: WIP.WIP_SCRAP_VALUES# 12.2.2
-
PACKAGE BODY: APPS.CSTPLCAS 12.2.2
-
PACKAGE: APPS.CSTPLCAS 12.2.2
-
PACKAGE BODY: APPS.CSTPLCAS 12.1.1
-
PACKAGE: APPS.CSTPLCAS 12.1.1
-
PACKAGE: APPS.CSTPCFMS 12.1.1
-
VIEW: WIP.WIP_SCRAP_VALUES# 12.2.2
-
APPS.CSTPLCAS SQL Statements 12.1.1
-
PACKAGE: APPS.CSTPCFMS 12.2.2
-
PACKAGE BODY: APPS.CSTPCFMS 12.2.2
-
EURO as a functional currency table for WIP_SCRAP_VALUES.
-
PACKAGE BODY: APPS.CSTPCFMS 12.1.1
-
APPS.CSTPLCAS SQL Statements 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
EURO as a functional currency table for WIP_SCRAP_VALUES.
-
12.2.2 DBA Data 12.2.2
-
PACKAGE BODY: APPS.CSTPACWS 12.1.1
-
PACKAGE: APPS.CSTPACWS 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
PACKAGE: APPS.CSTPACWS 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
PACKAGE BODY: APPS.CSTPACWS 12.2.2
-
PACKAGE BODY: APPS.CSTPLCAS 12.2.2