Results for “cst_cost_elements”

50+ results




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

Overview

CST_COST_ELEMENTS is the master definition table for cost elements within Oracle E-Business Suite. In the context of the Bills of Material (BOM) product schema, it establishes the canonical set of cost elements — the fundamental building blocks that classify how inventory, work in process, and manufacturing costs are grouped and accumulated. Although the table is owned by the BOM schema in the ETRM 12.2.2 documentation, its reach extends across the entire Oracle Cost Management and Manufacturing footprint, because virtually every costing transaction, cost detail row, and elemental cost record references a cost element through a foreign key.

In a typical Oracle EBS implementation, this table is populated and maintained by the Cost Management application, with the standard seeded elements being Material, Material Overhead, Resource, Outside Processing, and Overhead. These elements serve as the classification dimensions along which item costs, actual costs, and standard costs are stored and reported. With thirteen documented columns and a compact row count (one row per defined cost element), CST_COST_ELEMENTS operates effectively as a reference or lookup dimension table.

Under a Data Vault modeling heuristic mined from its foreign key structure, CST_COST_ELEMENTS is classified as hub-leaning. This is a modeling suggestion rather than a documented EBS fact: the table holds a stable, uniquely identified business concept (the cost element) with no intrinsic dependency on a parent entity, which aligns with the characteristics of a Data Vault hub. Practitioners designing a warehouse layer over EBS costing data may reasonably treat it as a hub with a surrogate key on COST_ELEMENT_ID.

Key Information Stored

The most important columns in CST_COST_ELEMENTS are:

All of these columns are documented in the ETRM 12.2.2 physical schema. The surrogate key COST_ELEMENT_ID is distinct from the business-key candidate COST_ELEMENT, and the ZD_EDITION_NAME column is relevant only in the 12.2 multi-edition architecture, though the object is compatible with both 12.1.1 and 12.2.2 environments.

Common Use Cases and Queries

Because this table is small and stable, it is most often used as a lookup to resolve cost element descriptions in costing reports. A common pattern joins CST_COST_ELEMENTS to a detail table to label cost breakdowns:

Reports covering standard cost adjustments, WIP scrap valuation, and period-close variance analysis all rely on this table to translate numeric cost element identifiers into meaningful labels.

Related Objects

The foreign key relationships documented in the ETRM metadata identify the principal dependent objects. Each of the following references CST_COST_ELEMENTS through COST_ELEMENT_ID:

These relationships confirm the table's central role as a hub referenced by both Cost Management and Manufacturing dependent objects.