Results for “prior_scrap_quantity”

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

Overview

CST_COMP_SNAPSHOT is a BOM (Bills of Material) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the assembly units completed at each operation step within a Work in Process (WIP) job. It functions as a point-in-time capture of completion activity, recording the quantities reported as complete or scrapped at a given operation sequence number and tying those quantities back to the material transaction that generated the movement. The table is central to how Oracle WIP and Cost Management reconcile operation-level completion activity with the associated inventory and cost transactions.

From a dimensional modeling perspective, the ETRM heuristic Data Vault classification for this object is a link. That is a modeling suggestion rather than an enforced constraint: the table connects a WIP entity, a material transaction, and an operation sequence, which is the classic pattern of an associative (link) structure between business keys rather than a hub of a single business concept or a satellite of descriptive attributes.

Key Information Stored

The physical table is owned by the BOM schema and documents 17 columns in the 12.2.2 ETRM schema. The most operationally significant columns are:

• TRANSACTION_ID — Identifier of the originating material transaction; part of the primary key and a foreign key to MTL_MATERIAL_TRANSACTIONS.
• WIP_ENTITY_ID — Identifier of the WIP job (discrete job or repetitive schedule) against which completion occurred; part of the primary key and a foreign key to WIP_ENTITIES.
• OPERATION_SEQ_NUM — The operation sequence step at which the completion quantity was reported; part of the primary key.
• PRIMARY_QUANTITY — The primary quantity completed for the operation, expressed in the primary unit of measure.
• QUANTITY_COMPLETED — The quantity of assembly units completed at this operation step.
• PRIOR_COMPLETION_QUANTITY — The cumulative quantity completed before the current transaction, used to derive net movement.
• PRIOR_SCRAP_QUANTITY — The cumulative scrap quantity recorded before the current transaction.
• NEW_OPERATION_FLAG — Indicates whether this completion represents movement into a new operation step.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the row and when.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the request that inserted or updated the row.

The surrogate/primary key is CST_COMP_SNAPSHOT_PK, defined over (TRANSACTION_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM). The unique index CST_COMP_SNAPSHOT_U1 covers the same three columns, making them the documented business-key candidate for the table. Uniqueness is therefore enforced on the combination of transaction, WIP entity, and operation sequence.

Common Use Cases and Queries

Typical usage centers on operation-level completion and scrap reporting, WIP job reconciliation, and cost/variance analysis. A common pattern joins the snapshot to the WIP job header and the material transaction to reconstruct completion history for a job:

• Reporting quantity completed and scrapped per operation for a given WIP entity over a date range.
• Reconciling snapshot completion rows against MTL_MATERIAL_TRANSACTIONS to validate that every counted completion has a corresponding transaction.
• Analyzing scrap rates by operation to identify yield loss at a specific routing step.
• Feeding cost roll-up and variance reports that compare prior completion and scrap quantities with current values.

A representative query pattern is: select c.TRANSACTION_ID, c.WIP_ENTITY_ID, c.OPERATION_SEQ_NUM, c.QUANTITY_COMPLETED, c.PRIOR_COMPLETION_QUANTITY, c.PRIOR_SCRAP_QUANTITY from CST_COMP_SNAPSHOT c where c.WIP_ENTITY_ID = :wip_entity_id order by c.OPERATION_SEQ_NUM, c.TRANSACTION_ID. Joining to WIP_ENTITIES on WIP_ENTITY_ID and to MTL_MATERIAL_TRANSACTIONS on TRANSACTION_ID enriches the result with job and transaction attributes.

Related Objects

The following objects are the most significant dependencies, grounded in the documented foreign keys:

• WIP_ENTITIES — joined on CST_COMP_SNAPSHOT.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_ID; supplies job or schedule context.
• MTL_MATERIAL_TRANSACTIONS — joined on CST_COMP_SNAPSHOT.TRANSACTION_ID = MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID; provides the movement and cost transaction detail.
• WIP_OPERATIONS / WIP_OPERATION_SEQUENCES — reference the operation sequence steps that OPERATION_SEQ_NUM relates to.
• MTL_TRANSACTION_TYPES / MTL_SYSTEM_ITEMS — reachable via the material transaction join for classification and item context.
• CST_COMP_SNAPSHOT_PK and CST_COMP_SNAPSHOT_U1 — the constraints enforcing row uniqueness on transaction, WIP entity, and operation sequence.
• WIP completion and move transaction APIs — the processing layer that populates this snapshot during operation completion.

Because the table is a link between a WIP entity and a material transaction, queries should treat it as an associative record of operation-level completion rather than as the master definition of a job or item.