Results for “cst_comp_snap_interface”

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

Overview

CST_COMP_SNAP_INTERFACE is a standard Oracle E-Business Suite table owned by the BOM (Bills of Material) schema. It resides in the manufacturing execution layer of Oracle Manufacturing and serves as a staging and interface table for assembly completion transactions. Specifically, it stores the assembly units completed at each operation step that are pending interface into the Cost Management (CST) subsystem through the standard transactions interface. In EBS 12.1.1 and 12.2.2 the table retains the same documented structure, with seventeen columns and a composite primary key.

The object captures operation-level completion and scrap quantities generated during Work in Process (WIP) execution, along with the identity of the originating work order and operation sequence. These records are read by concurrent processes that push completion data into the costing and transaction interface pipeline, where they are transformed into material transactions for inventory and cost accounting purposes.

From a Data Vault modeling perspective, the mined relationship data classifies this table heuristically as standalone, with no inferred foreign-key links to other hubs or satellites. That classification is a modeling suggestion only; functionally the table behaves as a transient interface staging entity keyed by a composite business identifier.

Key Information Stored

The table is keyed by the columns TRANSACTION_INTERFACE_ID, WIP_ENTITY_ID, and OPERATION_SEQ_NUM, defined physically by the primary key constraint CST_COMP_SNAP_INTERFACE_PK and mirrored by the unique index CST_COMP_SNAP_INTERFACE_U1. Because the same three columns constitute both the surrogate primary key and the unique business-key candidate, there is no separate synthetic identifier; the trio acts as the natural composite key identifying a single operation-level completion snapshot.

• TRANSACTION_INTERFACE_ID — Identifies the parent interface group to which this completion snapshot belongs.
• WIP_ENTITY_ID — References the work order (job or repetitive schedule) whose assembly is being completed.
• OPERATION_SEQ_NUM — The routing operation sequence at which the completion or scrap quantities were recorded.
• NEW_OPERATION_FLAG — Indicates whether the operation is newly created or first-time encountered.
• PRIMARY_QUANTITY — The primary unit-of-measure quantity associated with the snapshot.
• QUANTITY_COMPLETED — Units completed at the operation and eligible for interfacing.
• PRIOR_COMPLETION_QUANTITY — Cumulative completion quantity recorded before this snapshot.
• PRIOR_SCRAP_QUANTITY — Cumulative scrap quantity recorded before this snapshot.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the request that created or last processed the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking row creation and modification.

Common Use Cases and Queries

The most frequent use of this table is troubleshooting and reconciliation. Cost accounting teams query it to confirm whether operation-level completion quantities have been staged for costing, particularly when completion transactions do not appear in inventory or cost distributions. A typical diagnostic pattern filters rows by work order and operation:

• Selecting all snapshots for a given WIP_ENTITY_ID, ordered by OPERATION_SEQ_NUM, to review the completion progression across the routing.
• Joining TRANSACTION_INTERFACE_ID to the pending transaction records to trace whether the snapshot was successfully interfaced.
• Comparing QUANTITY_COMPLETED against PRIOR_COMPLETION_QUANTITY and PRIOR_SCRAP_QUANTITY to validate cumulative quantities and detect duplicate or missing completions.
• Filtering by CREATION_DATE and REQUEST_ID to isolate rows produced by a specific concurrent request run.

Reporting use cases include operation-level yield analysis and scrap trending, where staged quantities are extracted before interfacing to build custom dashboards. Because the table is interface-oriented, retained rows are typically short-lived; high row counts may indicate a stalled or failed interface process.

Related Objects

The table participates in the WIP-to-costing interface flow. Significant related objects include:

• CST_COMP_SNAP_INTERFACE_PK / CST_COMP_SNAP_INTERFACE_U1 — The primary key constraint and unique index enforcing the composite business key.
• WIP_ENTITIES / WIP_DISCRETE_JOBS — Work order master records joined via WIP_ENTITY_ID.
• WIP_OPERATIONS — Routing operations matched via WIP_ENTITY_ID and OPERATION_SEQ_NUM.
• MTL_TRANSACTIONS_INTERFACE — The downstream transaction interface populated from staged snapshots using TRANSACTION_INTERFACE_ID.
• CST_TRANSACTIONS / CST_ITEM_COSTS — Costing tables that ultimately consume completion data.
• FND_CONCURRENT_REQUESTS — Concurrent program context joined via REQUEST_ID for auditing interface runs.

These relationships, combined with the standard audit columns, allow administrators and developers to trace an operation completion from the work order through staging and into final costed transactions.