Search Results trx_source_line_id




Overview
Explore in AI Chat

Overview

BOM.CST_LC_MMT_GT is a global temporary table (GTT) in the Oracle EBS Cost Management module, owned by the BOM schema. It serves as an intermediate staging structure used during the material transaction cost collection and cost distribution process. The acronym "LC" denotes "Layer Cost" / "Landing Cost" processing within the Cost Management Transaction Interface, while "MMT" refers to Material Movement Transactions and "GT" confirms its global temporary nature.

The table is defined with a data duration of SYS$TRANSACTION, meaning rows are visible only to the session that inserted them and are automatically purged at transaction commit or rollback. This design is intentional: concurrent costing processes can populate identical column sets without row-level contention, and Oracle maintains transactional isolation without the overhead of permanent storage or manual cleanup. PCTFREE is set to 10 and PCTUSED to 40, typical for transient high-volume staging where insert/delete churn dominates over updates.

The table functions principally as a transient staging area between the Material Transaction Cost Interface and the final Cost Management distributions. Because the schema is documented as essentially standalone, the heuristic Data Vault classification suggests treating it as a link/transaction snapshot rather than a durable hub or satellite: it captures a moment-in-time relationship between a transaction, its source, and its costing attributes, but it is not intended to persist as an enterprise entity.

Key Information Stored

The 37 documented columns capture the costing identity, accounting disposition, and journal context of a material transaction. The most significant columns include:

Common Use Cases and Queries

Because the table is session-scoped and ephemeral, its practical use is within debugging, tracing, and reconciliation during a costing run rather than for persistent reporting. A typical diagnostic session joins the staging rows back to permanent transaction tables while the concurrent program is still active:

SELECT m.lcm_transaction_id, m.transaction_id, m.trx_source_line_id,
       m.inventory_item_id, m.organization_id, m.primary_quantity,
       m.value_change, m.costed_flag
FROM   bom.cst_lc_mmt_gt m
WHERE  m.acct_period_id = :period
AND    m.costed_flag = 'N';

Cost analysts use the table to identify transactions that failed to cost (COSTED_FLAG = 'N'), to verify that accounting buckets were populated correctly, and to trace a transaction back to its source document via TRX_SOURCE_LINE_ID. Where material movements appear out of balance with General Ledger distributions, comparing staged rows to final CST_* distributions isolates whether the failure occurred during collection or during distribution.

Related Objects