Search Results cst_cost_types_pk

Overview

CST_COST_TYPES is a foundational reference table in Oracle E-Business Suite Release 12.1.1 and 12.2.2, owned by the BOM (Bills of Material) schema and shared across the Cost Management (CST) and Bills of Material (BOM) product family. It stores the definition of every cost type configured within the enterprise, including the standard, average, FIFO, LIFO, and user-defined cost types that drive inventory valuation, WIP costing, and manufacturing rollups. Each row represents one cost type scoped to a specific inventory organization, making the table the master reference from which virtually all costing activity in the system derives its context.

Because the table is referenced by a very large number of transactional and setup tables across Cost Management, Work in Process, Purchasing, Order Management, and discrete manufacturing, it functions as a canonical lookup rather than a transactional entity. In Data Vault modeling terms, the heuristic classification for CST_COST_TYPES is a hub: it holds a stable, non-overlapping business key set (cost type identity) with descriptive attributes such as costing method and frozen standard flags attached. This classification is offered as a modeling suggestion only; the operational EBS schema treats it as a normal reference table.

Key Information Stored

The table contains 43 documented columns in the 12.2.2 schema. The most consequential are:

• COST_TYPE_ID – surrogate primary key, enforced by the CST_COST_TYPES_PK constraint. This is the value propagated into every dependent costing table via foreign key.
• COST_TYPE – the business-facing cost type name (for example, "Frozen Cost", "Average Cost", or a user-defined name). Together with ORGANIZATION_ID it forms the CST_COST_TYPES_UK1 unique key.
• ORGANIZATION_ID – the inventory organization to which the cost type is scoped; a second unique index, CST_COST_TYPES_U2, combines COST_TYPE, ORGANIZATION_ID, and ZD_EDITION_NAME.
• COSTING_METHOD_TYPE – indicates whether the cost type is used for standard, average, FIFO, LIFO, or other costing bases.
• FROZEN_STANDARD_FLAG – marks the frozen standard cost type used for revaluation and variance analysis.
• DEFAULT_COST_TYPE_ID – points to the default cost type applied when none is explicitly chosen.
• DESCRIPTION – free-text description used in setup and inquiry forms.
• BOM_SNAPSHOT_FLAG and ALTERNATE_BOM_DESIGNATOR – control which bill of material snapshot is used during cost rollup for this cost type.
• ALLOW_UPDATES_FLAG – determines whether cost records associated with the cost type can be modified.
• DISABLE_DATE – the date after which the cost type becomes inactive.
• PL_ELEMENT_FLAG, PL_RESOURCE_FLAG, PL_OPERATION_FLAG, PL_ACTIVITY_FLAG – enable or disable cost element, resource, operation, and activity collection during rollup.
• AVAILABLE_TO_ENG_FLAG and COMPONENT_YIELD_FLAG – control engineering availability and component yield behavior.
• LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID – standard audit and concurrent program columns.
• ZD_EDITION_NAME – the editioning column introduced under the 12.2 Online Patching architecture, participating in both unique indexes.

Common Use Cases and Queries

The most frequent reporting pattern is to resolve a COST_TYPE_ID surfaced from a transaction table back to its human-readable name and organization. A typical join appears below:

• Cost type lookup: SELECT ct.cost_type, ct.description, ct.costing_method_type FROM cst_cost_types ct WHERE ct.cost_type_id = :p_id;
• Item cost reporting: join CST_ITEM_COSTS to CST_COST_TYPES on COST_TYPE_ID to display item costs by cost type name, filtered by ORGANIZATION_ID.
• Rollup validation: query FROZEN_STANDARD_FLAG = 'Y' to isolate the frozen cost type used in revaluation and standard cost variance reports.
• Setup audit: list all active cost types per organization where DISABLE_DATE IS NULL, ordered by COST_TYPE.
• WIP and transaction costing: join MTL_MATERIAL_TRANSACTIONS or WIP_PAC_ACTUAL_COST_DETAILS on COST_TYPE_ID to report actual cost by cost type.
• Edition-aware queries (12.2): include ZD_EDITION_NAME when reporting under online patching to avoid spanning editions.

Related Objects

CST_COST_TYPES is referenced by more than eighty foreign keys. The most significant dependents include:

• CST_ITEM_COSTS – item cost records, joined on CST_ITEM_COSTS.COST_TYPE_ID = CST_COST_TYPES.COST_TYPE_ID.
• CST_ITEM_COST_DETAILS – detailed cost element breakdown, joined on COST_TYPE_ID.
• MTL_MATERIAL_TRANSACTIONS – inventory transactions stamped with COST_TYPE_ID at the time of costing.
• WIP_PAC_ACTUAL_COST_DETAILS and WIP_PAC_PERIOD_BALANCES – WIP actual cost and period balance records joined on COST_TYPE_ID.
• CST_ACTIVITY_COSTS, CST_RESOURCE_COSTS, CST_DEPARTMENT_OVERHEADS – cost element, resource, and overhead rates tied to a cost type.
• CST_PAC_PERIODS – costing periods associated with a cost type.
• CST_LE_COST_TYPES – legal entity to cost type mapping, joined twice (COST_TYPE_ID and PAC_RATES_COST_TYPE_ID).
• CST_COST_TYPE_HISTORY – audit trail of cost type definition changes.
• CST_COST_UPDATES and CST_RCV_ACQ_COSTS – cost update batches and receiving acquisition cost records.

Because of the breadth of dependencies, changes to CST_COST_TYPES should be made through the Cost Type setup forms or the Cost Management APIs rather than by direct DML, to preserve referential integrity across the many dependent costing tables.