Search Results cst_cogs_events_u2

Overview

CST_COGS_EVENTS is the accounting events table owned by the BOM schema in Oracle E-Business Suite, storing every event that impacts Cost of Goods Sold. Its scope covers sales order issues, RMA receipts, COGS Recognition events, and COGS Adjustment events created as a result of backdated COGS activity. The table records the quantities, percentages, and percentage changes required to build accounting distributions for each event, and it links related COGS events together by order line ID while establishing sequential relationships through the prior event ID and prior COGS percentage.

The table therefore serves two purposes. First, it provides the information necessary to create accounting distributions around COGS events. Second, it assists in generating additional COGS events by supplying the latest recorded COGS percentage for a given order line, a role performed in conjunction with CST_REVENUE_COGS_MATCH_LINES and CST_REVENUE_RECOGNITION_LINES during the Generate COGS Recognition Events concurrent request.

Under a heuristic Data Vault classification, CST_COGS_EVENTS behaves primarily as a link table, since it associates order lines, material transactions, and prior COGS events while carrying descriptive event attributes.

Key Information Stored

The table is physically stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and contains 21 documented columns. The most significant columns include:

• EVENT_ID — surrogate primary key and unique identifier for a COGS event row; enforced by the unique index CST_COGS_EVENTS_U1.
• MMT_TRANSACTION_ID — reference to the material transaction associated with the event; enforced by the unique index CST_COGS_EVENTS_U2, making it a business-key candidate.
• COGS_OM_LINE_ID — reference to the line ID of the original sales order issue, corresponding to OE_ORDER_LINES_ALL.LINE_ID; indexed non-uniquely by CST_COGS_EVENTS_N1.
• EVENT_OM_LINE_ID — the order line ID associated with the specific event being recorded.
• EVENT_DATE — truncated date of the COGS event; for recognition event types it corresponds to the Oracle Receivables GL date of the revenue recognition event.
• EVENT_TYPE — classification of the COGS event (issue, RMA receipt, recognition, or adjustment).
• COGS_PERCENTAGE and PRIOR_COGS_PERCENTAGE — the current and prior COGS percentage values used to compute distribution amounts.
• PRIOR_EVENT_ID and PARENT_EVENT_ID — self-referencing identifiers that build the sequential chain of related COGS events.
• EVENT_QUANTITY — quantity associated with the event.
• COSTED — flag indicating whether the event has been costed.
• REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID — concurrent program context identifying the process that created the row.

Common Use Cases and Queries

Typical reporting scenarios include tracing the COGS lifecycle for a sales order line, reconciling costed events with material transactions, and auditing the percentage chain used in recognition events. A common query pattern joins the table to material transactions and order lines:

• SELECT c.event_id, c.event_type, c.event_date, c.cogs_percentage, c.event_quantity FROM bom.cst_cogs_events c WHERE c.cogs_om_line_id = :line_id ORDER BY c.event_date;
• SELECT c.* FROM bom.cst_cogs_events c WHERE c.mmt_transaction_id = :mmt_id;
• SELECT c.* FROM bom.cst_cogs_events c WHERE c.costed = 'N' AND c.event_date >= :start_date;

Analysts also traverse the self-referencing chain via PRIOR_EVENT_ID and PARENT_EVENT_ID to reconstruct the sequence of backdated adjustments. Because EVENT_ID and MMT_TRANSACTION_ID are unique, they serve as reliable lookup keys in reconciliation reports.

Related Objects

The most significant related objects, based on documented foreign keys and processing dependencies, include:

• MTL_MATERIAL_TRANSACTIONS — referenced by CST_COGS_EVENTS.MMT_TRANSACTION_ID; provides transaction quantities and costs.
• OE_ORDER_LINES_ALL — referenced by CST_COGS_EVENTS.COGS_OM_LINE_ID; supplies sales order line context.
• CST_REVENUE_COGS_MATCH_LINES — used with the event table during COGS recognition event generation.
• CST_REVENUE_RECOGNITION_LINES — provides revenue recognition lines that drive recognition events.
• CST_COGS_EVENTS itself — self-referenced through PRIOR_EVENT_ID and PARENT_EVENT_ID.
• Generate COGS Recognition Events concurrent request — the primary process that reads and writes rows in this table.
• Downstream SLA accounting distribution processes that consume event rows to create journal entries.