Search Results mtl_actual_cost_subelement

Overview

The MTL_ACTUAL_COST_SUBELEMENT table is a core transactional data repository within the Oracle E-Business Suite Inventory (INV) module. It functions as the detailed ledger for capturing and storing the material overhead subelement costs associated with individual inventory transactions. When a material transaction is costed, any applied material overhead is broken down into its constituent subelements, and the cost details for each are recorded in this table. This granular storage is critical for maintaining accurate and auditable inventory valuation, enabling precise cost analysis, and supporting the reconciliation of general ledger accounts for inventory-related activities in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary role is to link a specific material transaction to its detailed cost breakdown. Its key columns establish these relationships and store the associated cost figures. The TRANSACTION_ID column is the critical foreign key that ties each subelement cost record to its parent transaction in the MTL_MATERIAL_TRANSACTIONS table. The COST_ELEMENT_ID identifies the type of cost element (like Material, Material Overhead, Resource, etc.) by referencing the CST_COST_ELEMENTS table. For resource-related overheads, the RESOURCE_ID column links to the BOM_RESOURCES table. The table also contains columns to store the actual cost amounts (e.g., BASE_TRANSACTION_VALUE, ACTUAL_COST) and rates applied, providing a complete audit trail for the cost calculation of each transaction subelement.

Common Use Cases and Queries

This table is essential for detailed cost inquiry and troubleshooting. A primary use case is analyzing the complete cost composition of a specific material transaction, such as a receipt or issue. For example, to see all overhead subelements applied to a particular transaction, one would query this table filtered by the relevant TRANSACTION_ID. It is also fundamental for period-end cost reconciliation reports, where the sum of costs in this table for a given period and subinventory should reconcile with the inventory valuation reports. Common SQL patterns involve joining to MTL_MATERIAL_TRANSACTIONS for transaction details (like item, date, quantity) and to CST_COST_ELEMENTS or BOM_RESOURCES for descriptive names of the cost elements and resources.

• SELECT macs.*, mmt.transaction_date, cce.cost_element FROM inv.mtl_actual_cost_subelement macs JOIN inv.mtl_material_transactions mmt ON macs.transaction_id = mmt.transaction_id JOIN cst.cst_cost_elements cce ON macs.cost_element_id = cce.cost_element_id WHERE mmt.transaction_id = :p_trx_id;

Related Objects

The MTL_ACTUAL_COST_SUBELEMENT table maintains defined foreign key relationships with several fundamental EBS tables, as documented in the ETRM metadata. These relationships are central to its integrity and function.

• MTL_MATERIAL_TRANSACTIONS: The primary relationship is via MTL_ACTUAL_COST_SUBELEMENT.TRANSACTION_ID → MTL_MATERIAL_TRANSACTIONS. Every record in this table must correspond to a valid inventory transaction.
• CST_COST_ELEMENTS: The cost element type is validated through MTL_ACTUAL_COST_SUBELEMENT.COST_ELEMENT_ID → CST_COST_ELEMENTS.
• BOM_RESOURCES: For overheads tied to specific resources, the relationship MTL_ACTUAL_COST_SUBELEMENT.RESOURCE_ID → BOM_RESOURCES provides the resource details.

This table is also a key source for inventory valuation and cost management reports, and its data feeds into the Cost Management and General Ledger modules for financial posting.