Search Results cst_cost_updates




Overview
Explore in AI Chat

Overview

The WIP_SCRAP_VALUES table is a critical transactional data store within the Oracle E-Business Suite Work in Process (WIP) module. It serves as the definitive repository for capturing the detailed cost accounting impact of assembly scrap transactions. When a component or assembly is scrapped from a job or schedule, the system records the associated cost distribution across different cost elements (such as material, resource, overhead, and outside processing) in this table. Its primary role is to ensure accurate cost tracking, variance analysis, and financial reporting for manufacturing operations by maintaining a granular, auditable record of every scrap event's financial consequences.

Key Information Stored

The table's structure is designed to uniquely identify and quantify the cost of a scrap transaction. Its composite primary key consists of four columns: TRANSACTION_ID, which links to the material transaction in MTL_MATERIAL_TRANSACTIONS; LEVEL_TYPE, which indicates the cost level; COST_ELEMENT_ID, which links to the specific cost element in CST_COST_ELEMENTS; and COST_UPDATE_ID, which references the cost update batch in CST_COST_UPDATES. While the provided metadata does not list all value columns, the table's purpose implies it contains at least one column for the actual scrap cost amount (e.g., COST, SCRAP_VALUE) corresponding to each combination in the primary key, thereby breaking down the total scrap cost by element.

Common Use Cases and Queries

This table is central to scrap analysis and cost reconciliation. A common use case involves generating reports to analyze scrap costs by job, assembly, cost element, or department over a period. Financial controllers use this data to calculate manufacturing variances and assess operational efficiency. For technical consultants, a typical query involves joining to related transaction and master tables to extract a comprehensive scrap history. A sample SQL pattern might be:

  • SELECT ws.TRANSACTION_ID, mmt.TRANSACTION_DATE, cce.COST_ELEMENT, ws.LEVEL_TYPE, ws.COST
  • FROM WIP.WIP_SCRAP_VALUES ws,
  • INV.MTL_MATERIAL_TRANSACTIONS mmt,
  • CST.CST_COST_ELEMENTS cce
  • WHERE ws.TRANSACTION_ID = mmt.TRANSACTION_ID
  • AND ws.COST_ELEMENT_ID = cce.COST_ELEMENT_ID
  • AND mmt.TRANSACTION_DATE BETWEEN :P_START_DATE AND :P_END_DATE;

This data is also essential for period-end closing procedures to ensure all scrap costs are properly accounted for in the general ledger.

Related Objects

The WIP_SCRAP_VALUES table maintains strict referential integrity through its documented foreign key relationships. It is a child table to several key master and transactional tables in the manufacturing and cost modules. The specific relationships are:

  • MTL_MATERIAL_TRANSACTIONS: The TRANSACTION_ID column references MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID. This links every scrap cost record to its originating material transaction.
  • CST_COST_ELEMENTS: The COST_ELEMENT_ID column references CST_COST_ELEMENTS.COST_ELEMENT_ID. This ties the scrap cost to a specific accounting element like Material or Resource.
  • CST_COST_UPDATES: The COST_UPDATE_ID column references CST_COST_UPDATES.COST_UPDATE_ID. This associates the scrap cost with a specific cost maintenance or update batch, which is crucial for audit trails and understanding which cost version was applied.

These relationships position WIP_SCRAP_VALUES as a central hub connecting transactional data from Inventory (INV), cost master data from Cost Management (CST), and the scrap event itself from Work in Process (WIP).