Search Results mtl_pac_cost_subelements




Overview
Explore in AI Chat

Overview

The MTL_PAC_COST_SUBELEMENTS table is a core transactional data repository within Oracle E-Business Suite Inventory (INV) module. It plays a critical role in the Periodic Average Costing (PAC) process, which is a standard cost accounting method used in manufacturing and distribution environments. Specifically, this table stores detailed records of material overhead sub-elements charged to inventory transactions within a specific accounting period. It enables the system to track and allocate overhead costs—such as indirect materials, labor, or machine costs—to inventory items, thereby facilitating accurate period-end valuation and cost analysis. The table's existence is fundamental to maintaining granular cost visibility and ensuring that the total cost of an item reflects all applicable overhead components as defined by the organization's cost accounting setup.

Key Information Stored

The table's structure is designed to uniquely identify a cost charge for a specific transaction within a period and cost group. Its primary key is a composite of TRANSACTION_ID, PAC_PERIOD_ID, COST_GROUP_ID, COST_ELEMENT_ID, LEVEL_TYPE, and RESOURCE_ID. Important columns include TRANSACTION_ID, which links to the originating material transaction in MTL_MATERIAL_TRANSACTIONS, and PAC_PERIOD_ID, which ties the record to a specific costing period in CST_PAC_PERIODS. The COST_GROUP_ID and COST_TYPE_ID columns reference the cost group and cost type used for the calculation. The COST_ELEMENT_ID and RESOURCE_ID columns identify the specific overhead cost element (from CST_COST_ELEMENTS) and the associated resource (from BOM_RESOURCES) that incurred the charge. The LEVEL_TYPE indicates the application level of the overhead. Together, these columns store the quantitative and qualitative details of every material overhead application.

Common Use Cases and Queries

A primary use case is auditing and reconciling period-end inventory valuations. Analysts query this table to verify the overhead costs absorbed by inventory during a period, which is crucial for financial reporting. Another common scenario is troubleshooting cost discrepancies; by examining the sub-element details for a specific transaction, users can identify if an expected overhead charge was applied correctly. A typical query pattern involves joining to transaction and period tables to analyze overhead costs by item, period, or cost group. For example:

  • Identifying all overhead charges for a specific transaction: SELECT * FROM MTL_PAC_COST_SUBELEMENTS WHERE TRANSACTION_ID = <id> AND PAC_PERIOD_ID = <period_id>;
  • Summarizing total material overhead cost by period and cost element for reporting: SELECT PAC_PERIOD_ID, COST_ELEMENT_ID, SUM(BASE_TRANSACTION_VALUE) FROM MTL_PAC_COST_SUBELEMENTS GROUP BY PAC_PERIOD_ID, COST_ELEMENT_ID;

Related Objects

MTL_PAC_COST_SUBELEMENTS is centrally connected to several key inventory and costing tables via foreign key relationships, as documented in the ETRM. These relationships enforce data integrity and are essential for joins in reports and interfaces.

  • CST_COST_GROUPS: Joined via COST_GROUP_ID to identify the cost group.
  • MTL_MATERIAL_TRANSACTIONS: Joined via TRANSACTION_ID to link to the source inventory transaction.
  • CST_PAC_PERIODS: Joined via PAC_PERIOD_ID to associate records with a specific costing period.
  • CST_COST_TYPES: Joined via COST_TYPE_ID to determine the costing method (e.g., Average Cost).
  • CST_COST_ELEMENTS: Joined via COST_ELEMENT_ID to obtain the name and type of the overhead element.
  • BOM_RESOURCES: Joined via RESOURCE_ID to get details on the specific resource (e.g., machine, labor) charged.