Search Results cst_cost_elem_exp_types




Overview
Explore in AI Chat

Overview

CST_COST_ELEM_EXP_TYPES is a reference and mapping table owned by the BOM schema (Bills of Material module) in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its documented description — "Expenditure types for cost elements" — defines its role: it associates Oracle Purchasing expenditure types with the cost elements used by the Cost Management (CST) costing engine. In a standard costing or average costing environment, transaction costs and material charges must be classified into cost elements such as Material, Material Overhead, Resource, Outside Processing, and Overhead. This table provides the mapping that determines which expenditure types feed which cost elements during cost collection and transaction cost processing.

The ETRM relationship metadata classifies this object as standalone using a heuristic Data Vault classification, meaning no foreign keys to parent tables were mined from the constraint structure. In Data Vault modeling terms, this suggests the table is best represented as a standalone hub or reference satellite rather than as a link between two hubs, though the absence of mined FK constraints does not preclude logical relationships maintained through application logic rather than database-level constraints.

Key Information Stored

The documented physical schema contains 13 columns. The following columns carry the substantive business meaning:

  • COST_ELEMENT_ID — the surrogate primary key, enforced by CST_COST_ELEM_EXP_TYPES_PK. Identifies the cost element to which expenditure types are assigned.
  • EXPENDITURE_TYPE_IN — the inbound expenditure type mapped to the cost element; typically used for receipts, returns, or inbound inventory transactions.
  • EXPENDITURE_TYPE_OUT — the outbound expenditure type mapped to the same cost element, used for issues, deliveries, or outbound cost flows.
  • ZD_EDITION_NAME — a partition or edition qualifier that participates in the unique index CST_COST_ELEM_EXP_TYPES_U1 (COST_ELEMENT_ID, ZD_EDITION_NAME). This composite unique index is the documented business-key candidate, distinguishing rows across editions or operating contexts for the same cost element.

Standard EBS audit and concurrent-manager columns complete the structure: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. These support who-audit trails and traceability back to the concurrent program or request that inserted or modified each row.

Common Use Cases and Queries

Typical scenarios include validating expenditure-type-to-cost-element setups before cost collection, diagnosing "no cost element" errors during transaction costing, and building reports that reconcile purchasing charge accounts against cost element assignments. A representative query joining the mapping to the cost element definition is:

  • SELECT m.COST_ELEMENT_ID, m.EXPENDITURE_TYPE_IN, m.EXPENDITURE_TYPE_OUT FROM BOM.CST_COST_ELEM_EXP_TYPES m WHERE m.COST_ELEMENT_ID = :p_id;
  • Audit query filtering by program context: SELECT * FROM BOM.CST_COST_ELEM_EXP_TYPES WHERE PROGRAM_ID = :prog AND LAST_UPDATE_DATE >= :since;
  • Uniqueness verification using the business-key candidate: SELECT COST_ELEMENT_ID, ZD_EDITION_NAME, COUNT(*) FROM BOM.CST_COST_ELEM_EXP_TYPES GROUP BY COST_ELEMENT_ID, ZD_EDITION_NAME HAVING COUNT(*) > 1;

Because the table is standalone, reporting joins are usually driven by the COST_ELEMENT_ID value rather than by declared foreign keys.

Related Objects

The ETRM metadata documents no foreign keys, so the following relationships are logical rather than constraint-enforced:

  • CST_COST_ELEMENTS — the cost element definition table, joined on COST_ELEMENT_ID; the primary logical parent of this object.
  • PO_EXPENDITURE_TYPES / PO_LINE_TYPES — Purchasing reference objects that define the values appearing in EXPENDITURE_TYPE_IN and EXPENDITURE_TYPE_OUT.
  • CST_TRANSACTIONS — the transaction cost table whose rows are classified into cost elements using this mapping.
  • CST_ITEM_COSTS — item cost records whose cost element breakdown depends on the same classification.
  • CST_COST_GROUPS — cost group definitions that reference cost elements maintained in this mapping.
  • Cost Management concurrent programs and the CSTPLP (cost processing) PL/SQL packages consume this configuration during cost collection.