Search Results cst_cogs_events




Overview
Explore in AI Chat

Overview

In Oracle EBS 12.1.1 and 12.2.2, CST_COGS_EVENTS is a Cost Management table (physically owned by the BOM schema) that serves as the accounting events repository for Cost of Goods Sold (COGS) Recognition. It records the discrete events that drive the percentage-complete or event-based recognition of COGS against order lines. Each row captures a recognition event tied to a specific material transaction and, where applicable, a specific order line, forming the transactional audit trail that feeds COGS accounting entries and period-end cost recognition reporting.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as a link table: it connects material movement (via MMT_TRANSACTION_ID to MTL_MATERIAL_TRANSACTIONS) with order line context (via COGS_OM_LINE_ID to OE_ORDER_LINES_ALL). The presence of descriptive and state columns also gives it satellite-like characteristics, but the dominant relationship pattern is associative.

Key Information Stored

The table has 21 documented columns. The most operationally significant are the following:

  • EVENT_ID — the surrogate primary key for each COGS recognition event. It is enforced by the unique index CST_COGS_EVENTS_U1, making it the canonical single-column identifier.
  • MMT_TRANSACTION_ID — foreign key to MTL_MATERIAL_TRANSACTIONS, anchoring the event to the underlying inventory/shipping transaction. It is also a documented business-key candidate via unique index CST_COGS_EVENTS_U2, indicating one COGS event per material transaction in practice.
  • COGS_OM_LINE_ID — foreign key to OE_ORDER_LINES_ALL, linking the event to the originating sales order line.
  • EVENT_OM_LINE_ID and EVENT_QUANTITY — the order line and quantity associated with the event, supporting quantity-based recognition.
  • COGS_PERCENTAGE and PRIOR_COGS_PERCENTAGE — the cumulative and previously recognized COGS percentages, enabling incremental recognition calculations.
  • PRIOR_EVENT_ID and PARENT_EVENT_ID — self-referencing lineage columns that chain events together for reversal, adjustment, and hierarchical recognition scenarios.
  • EVENT_TYPE — classification of the recognition event.
  • EVENT_DATE — the accounting date of the event, essential for period assignment.
  • COSTED — flag indicating whether the event has been processed by the costing engine.
  • LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard EBS audit and concurrent program context columns used for traceability.

Common Use Cases and Queries

Typical scenarios include reconciling recognized COGS against shipped material transactions, auditing recognition percentages by order line, and reporting period COGS events for financial close. A representative join pattern follows:

  • Join CST_COGS_EVENTS to MTL_MATERIAL_TRANSACTIONS on MMT_TRANSACTION_ID to obtain transaction date, quantity, and item context.
  • Join to OE_ORDER_LINES_ALL on COGS_OM_LINE_ID to retrieve order number, line, and customer information.
  • Filter COSTED = 'Y' and EVENT_DATE within a period range to isolate posted recognition activity.
  • Self-join on PRIOR_EVENT_ID to reconstruct the recognition chain for a given order line.

These patterns support subledger-to-GL reconciliation, deferred COGS analysis, and exception reporting for events that remain unprocessed (COSTED not set).

Related Objects

  • MTL_MATERIAL_TRANSACTIONS — joined via CST_COGS_EVENTS.MMT_TRANSACTION_ID; the source inventory transaction.
  • OE_ORDER_LINES_ALL — joined via CST_COGS_EVENTS.COGS_OM_LINE_ID; the originating order line.
  • CST_COGS_EVENTS (self) — joined via PRIOR_EVENT_ID and PARENT_EVENT_ID for event lineage.
  • Cost Management COGS recognition concurrent programs that populate and consume this table.
  • COGS recognition and cost accounting reports in the Bill of Materials and Cost Management modules.