Results for “cst_eam_cost_elements”

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

Overview

CST_EAM_COST_ELEMENTS is a reference (setup) table owned by the BOM schema in Oracle E-Business Suite, classified under the Bills of Material product family. It defines the valid Enterprise Asset Management (EAM) cost elements — the cost categories used to classify maintenance work order charges such as labor, material, equipment, and outside processing. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the master list from which EAM cost collection, period balance, and asset cost reporting logic derives its category values. Because it is a low-volume, slowly changing reference table whose primary key is a surrogate identifier, the ETRM Data Vault heuristic classifies it as hub-leaning. In a Data Vault model this would typically be represented as a hub (EAM cost element business entity) surrounded by descriptive satellites, with dependent transactional tables acting as links to the hub.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• EAM_COST_ELEMENT_ID — the surrogate primary key (CST_EAM_COST_ELEMENTS_PK) uniquely identifying each cost element row. It is also the leading column of the unique index CST_EAM_COST_ELEMENTS_U1 (EAM_COST_ELEMENT_ID, ZD_EDITION_NAME), making it a business-key candidate.
• EAM_COST_ELEMENT — the user-facing name or code of the cost element used in EAM transactions and reports.
• DESCRIPTION — the descriptive text explaining the purpose of the cost element.
• ZD_EDITION_NAME — the edition identifier supporting Oracle's edition-based redefinition (EBR) architecture in 12.2.x, allowing online patching without downtime. It forms the second column of the unique index.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record creation and modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the request that last populated or updated the row.

Common Use Cases and Queries

CST_EAM_COST_ELEMENTS is used to drive EAM maintenance cost reporting, period-end cost rollups, and the defaulting of cost elements on maintenance work orders. A typical join resolves the cost element name for maintenance balance data:

• Lookup/validation query — SELECT eam_cost_element_id, eam_cost_element, description FROM bom.cst_eam_cost_elements WHERE zd_edition_name = 'SET1';
• Reporting query joining period balances to names: SELECT p.*, c.eam_cost_element, c.description FROM cst_eam_period_balances p, cst_eam_cost_elements c WHERE p.maintainable_cost_category = c.eam_cost_element_id;
• Identifying the default cost element configured for maintenance parameters via WIP_EAM_PARAMETERS.DEF_EAM_COST_ELEMENT_ID.

Because the table stores setup metadata rather than transactional volume, it is most valuable as a lookup dimension in EAM cost and asset reporting extracts.

Related Objects

The documented foreign keys show that CST_EAM_COST_ELEMENTS is referenced by four dependent tables, confirming its role as a hub in the EAM cost model:

• WIP_EAM_PARAMETERS — references this table through DEF_EAM_COST_ELEMENT_ID, defining the default cost element for EAM maintenance parameters.
• CST_EAM_ASSET_PER_BALANCES — references it via MAINT_COST_CATEGORY, linking asset periodic balances to cost elements.
• CST_EAM_BALANCE_BY_ACCOUNTS — references it via TXN_TYPE, associating balance-by-account records with cost elements.
• WIP_EAM_PERIOD_BALANCES — references it via MAINT_COST_CATEGORY, tying period balance records to EAM cost elements.

These relationships make CST_EAM_COST_ELEMENTS the central reference point for EAM maintenance cost definition and reporting across the BOM and WIP schemas.