Results for “transaction_costed_date”

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

Overview

MTL_CST_ACTUAL_COST_DETAILS is a transaction-level cost detail table residing in the INV schema of Oracle E-Business Suite (validated for 12.1.1 and 12.2.2). It stores actual cost information broken down by cost element and by cost level, capturing the before-and-after cost state of each material transaction processed by the Cost Management (CST) engine. Where MTL_MATERIAL_TRANSACTIONS records the physical movement of inventory, MTL_CST_ACTUAL_COST_DETAILS records the monetary consequences of that movement: the prior cost, the newly computed cost, the variance arising from the difference, and the cost element to which each amount belongs.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this table behaves as a link — it connects material transactions, cost elements, and inventory items/ organizations — while also carrying descriptive and numeric attributes (ACTUAL_COST, PRIOR_COST, NEW_COST, variances) that would typically be modeled as a satellite attached to that link. Both readings are consistent with the documented FK topology. The table is populated during the cost processor run and is central to cost variance analysis, period-close reconciliation, and per-transaction cost audit.

Key Information Stored

The documented physical schema contains 25 columns. The most significant are summarized below.

• Composite primary key (surrogate): LAYER_ID, TRANSACTION_ID, ORGANIZATION_ID, COST_ELEMENT_ID, LEVEL_TYPE, TRANSACTION_ACTION_ID — defined by MTL_CST_ACTUAL_COST_DETAILS_PK.
• Business-key candidate: the unique index MTL_CST_ACTUAL_COST_DETAILS_U1 covers TRANSACTION_ID, ORGANIZATION_ID, LAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE, TRANSACTION_ACTION_ID and can serve as the natural business key.
• INVENTORY_ITEM_ID — the item affected by the transaction; joins to MTL_SYSTEM_ITEMS_B.
• ACTUAL_COST — the cost amount computed for the layer/element combination.
• PRIOR_COST and NEW_COST — the cost before and after the transaction, enabling delta reporting.
• VARIANCE_AMOUNT — the difference between prior and new cost; the primary driver of cost-variance reporting.
• PAYBACK_VARIANCE_AMOUNT and ONHAND_VARIANCE_AMOUNT — specialised variance components used in payback and on-hand revaluation analysis.
• INSERTION_FLAG and USER_ENTERED — flags distinguishing system-generated records from user-entered adjustments.
• TRANSACTION_COSTED_DATE — the date the transaction was costed, used for period alignment.
• Standard EBS audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — provide WHO-column and concurrency context.

Common Use Cases and Queries

Typical scenarios include cost-variance analysis during period close, reconciliation of the cost processor output against the general ledger, and forensic audit of a single transaction's cost impact.

Sample pattern — all cost elements for a transaction:

• SELECT TRANSACTION_ID, COST_ELEMENT_ID, LEVEL_TYPE, PRIOR_COST, NEW_COST, VARIANCE_AMOUNT FROM MTL_CST_ACTUAL_COST_DETAILS WHERE TRANSACTION_ID = :txn_id AND ORGANIZATION_ID = :org_id;

Sample pattern — variance by item for a costing period:

• SELECT INVENTORY_ITEM_ID, COST_ELEMENT_ID, SUM(VARIANCE_AMOUNT) FROM MTL_CST_ACTUAL_COST_DETAILS WHERE ORGANIZATION_ID = :org_id AND TRANSACTION_COSTED_DATE BETWEEN :start AND :end GROUP BY INVENTORY_ITEM_ID, COST_ELEMENT_ID;

Reporting often joins the table to MTL_MATERIAL_TRANSACTIONS for transaction type/date context, to CST_COST_ELEMENTS for element names, and to MTL_SYSTEM_ITEMS_B for item descriptions.

Related Objects

• MTL_MATERIAL_TRANSACTIONS — joined via TRANSACTION_ID; supplies transaction type, date, quantity, and source context.
• CST_COST_ELEMENTS — joined via COST_ELEMENT_ID; resolves element names (Material, Material Overhead, Resource, Overhead, Outside Processing).
• MTL_SYSTEM_ITEMS_B — joined via INVENTORY_ITEM_ID and ORGANIZATION_ID; provides item attributes.
• MTL_CST_TRANSACTION_COSTS — aggregate transaction cost header feeding detail rows.
• MTL_CST_LAYER_COSTS — layer-level cost record referenced by LAYER_ID.
• CST_TRANSACTION_COST_DETAILS / Cost Management concurrent programs — populate and reconcile this table during periodic costing.