Search Results cst_cost_type_history




Overview
Explore in AI Chat

Overview

The CST_COST_TYPE_HISTORY table is a core data repository within the Oracle E-Business Suite Bills of Material (BOM) module, specifically for Oracle EBS releases 12.1.1 and 12.2.2. It serves as a historical audit and control mechanism for cost accounting processes. As indicated by its description, it stores critical information related to cost rollup calculations and the purge history of cost types. This table enables organizations to track when standard costs were rolled up for items or categories, providing an essential audit trail for financial reporting and cost management. Its existence is fundamental to maintaining data integrity and supporting compliance by preserving a record of past costing activities.

Key Information Stored

The table's structure, as defined by its primary and foreign keys, reveals the specific data it holds. The primary key is a composite of COST_TYPE_ID and ORGANIZATION_ID, ensuring historical records are unique per cost type and inventory organization. Key foreign key relationships point to the core data entities involved in costing. The INVENTORY_ITEM_ID and ORGANIZATION_ID columns link to MTL_SYSTEM_ITEMS_B, storing history for specific items. The CATEGORY_ID and CATEGORY_SET_ID columns link to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B, respectively, storing history for cost updates performed at the category level. While the specific detail columns are not listed in the provided metadata, the table logically stores timestamps of rollup or purge events, the user who initiated the action, and the status or version of the cost data at that point in time.

Common Use Cases and Queries

This table is primarily accessed for audit inquiries, troubleshooting cost history, and generating compliance reports. Common operational scenarios include verifying the date of the last cost rollup for a critical component before a financial period close, or identifying which items were affected by a specific cost update run. A typical analytical query would join this table to CST_COST_TYPES and MTL_SYSTEM_ITEMS_B to produce a report of cost update history. For example:

  • Identifying the latest rollup for a cost type: SELECT MAX(creation_date), cost_type_id, organization_id FROM bom.cst_cost_type_history GROUP BY cost_type_id, organization_id;
  • Auditing item-specific cost history: SELECT cth.*, msib.segment1 item_code FROM bom.cst_cost_type_history cth, mtl_system_items_b msib WHERE cth.inventory_item_id = msib.inventory_item_id AND cth.organization_id = msib.organization_id AND msib.segment1 = '<ITEM>';

Related Objects

The foreign key constraints explicitly define this table's critical dependencies within the EBS schema. Its primary relationship is with CST_COST_TYPES, which defines the master list of costing methods (like Frozen, Average, Pending). It is intrinsically linked to inventory master data through MTL_SYSTEM_ITEMS_B. Furthermore, its connections to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B allow it to support category-based costing operations. This table is a central point in the cost management data model, sitting downstream from master data definitions and upstream from detailed cost transaction tables, which would likely reference the historical snapshots or periods tracked here.