Search Results cst_comp_snapshot

Overview

The CST_COMP_SNAPSHOT table is a core transactional data object within the Oracle E-Business Suite Bills of Material (BOM) module. Its primary function is to serve as a detailed ledger for tracking manufacturing progress by storing a historical snapshot of assembly units completed at each specific operation step on a discrete job or schedule. This table is critical for maintaining accurate work-in-process (WIP) costing and production reporting, as it captures the precise quantity of assemblies moved through the routing at the moment a material transaction is processed. It acts as a supporting table for the cost management and WIP modules, enabling the system to calculate and reconcile costs at an operational granularity.

Key Information Stored

The table's structure is designed to link a material transaction to its corresponding production job and operation detail. The primary key uniquely identifies a snapshot record through a combination of TRANSACTION_ID, WIP_ENTITY_ID, and OPERATION_SEQ_NUM. The TRANSACTION_ID column links directly to the material transaction that caused the completion. The WIP_ENTITY_ID identifies the specific discrete job or repetitive schedule. The OPERATION_SEQ_NUM denotes the sequence number of the operation within the job's routing where the completion occurred. While the provided metadata does not list all columns, typical data would include the quantity completed (COMPLETION_QUANTITY) and the transaction date, forming a complete record of production movement.

Common Use Cases and Queries

This table is essential for operational and cost analysis reporting. A common use case is tracing the completion history of a specific job to analyze yield or throughput at each operation. It is also queried extensively during period-end cost reconciliation to validate WIP valuation. For instance, to find all completion snapshots for a given job, a query would join to WIP_ENTITIES. A typical reporting pattern involves joining CST_COMP_SNAPSHOT to MTL_MATERIAL_TRANSACTIONS for transaction dates and to WIP_ENTITIES for job details.

• Sample Query Pattern: SELECT ccs.transaction_id, ccs.operation_seq_num, mmt.transaction_date, we.wip_entity_name FROM bom.cst_comp_snapshot ccs JOIN inv.mtl_material_transactions mmt ON ccs.transaction_id = mmt.transaction_id JOIN wip.wip_entities we ON ccs.wip_entity_id = we.wip_entity_id WHERE we.wip_entity_id = :p_job_id;

Related Objects

The CST_COMP_SNAPSHOT table maintains defined foreign key relationships with two primary transactional tables, as documented in the ETRM metadata.

• WIP_ENTITIES: Joined via CST_COMP_SNAPSHOT.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_ID. This relationship provides access to the discrete job or repetitive schedule header information, such as the job name, assembly item, and status.
• MTL_MATERIAL_TRANSACTIONS: Joined via CST_COMP_SNAPSHOT.TRANSACTION_ID = MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID. This critical link ties the completion snapshot to the broader inventory transaction, providing context like transaction date, time, and the ultimate source and destination of the material movement.