Search Results cst_cost_types_u2

Overview

BOM.CST_COST_TYPES is the master definition table for cost types within the Oracle E-Business Suite Cost Management module. Every costed transaction, cost rollup, and valuation inquiry in Oracle EBS resolves to a row in this table, because all cost records reference a cost type. The table is seeded with three system cost types — Frozen (used by standard costing organizations), Average (used by average costing organizations), and Pending (used as a staging area for cost updates before they are applied) — and customers may define additional user cost types subject to the ALLOW_UPDATES_FLAG and costing-method rules.

In Data Vault terms, the mined foreign-key topology classifies CST_COST_TYPES as a hub. This is a modeling suggestion: the table holds a stable business key (COST_TYPE plus ORGANIZATION_ID) surrounded by descriptive attributes, and dozens of downstream cost tables attach to it as satellites or links through COST_TYPE_ID. It therefore functions as the reference hub for the entire costing subject area.

Key Information Stored

The surrogate primary key is COST_TYPE_ID (CST_COST_TYPES_PK). Two unique indexes supply the business-key candidates: CST_COST_TYPES_U1 on COST_TYPE_ID and CST_COST_TYPES_U2 on (COST_TYPE, ORGANIZATION_ID), the latter being the search term the user referenced. In 12.2.2 these unique indexes include ZD_EDITION_NAME, reflecting the editioning model used by Online Patching.

• COST_TYPE — varchar2(10) name of the cost type (for example, Frozen or Average); half of the U2 business key.
• ORGANIZATION_ID — owning inventory organization; the other half of the U2 key, making cost types organization-scoped.
• COSTING_METHOD_TYPE — numeric flag identifying whether the cost type is standard or average.
• FROZEN_STANDARD_FLAG — indicates whether the row is the frozen standard cost type.
• DEFAULT_COST_TYPE_ID — the cost type used as the default when performing cost rollups; a self-referencing pointer to COST_TYPE_ID.
• BOM_SNAPSHOT_FLAG — controls whether the bill structure is saved during a cost rollup for this cost type.
• ALTERNATE_BOM_DESIGNATOR — alternate BOM designator applied during rollup.
• ALLOW_UPDATES_FLAG — whether cost records for this cost type may be modified.
• PL_ELEMENT_FLAG, PL_RESOURCE_FLAG, PL_OPERATION_FLAG, PL_ACTIVITY_FLAG — determine whether the Cost Rollup groups rolled-up costs by cost element, sub-element, resource, operation sequence number, or activity.
• DESCRIPTION and the fifteen ATTRIBUTE columns — descriptive text and the standard DFF extension block.
• Standard WHO and concurrent columns — LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID and related audit fields.

Common Use Cases and Queries

Costing reports and interfaces almost always begin by resolving a cost type. Typical patterns include listing all cost types in an organization, finding the frozen cost type for a standard-costing organization, or joining to CST_ITEM_COSTS to report item valuation by cost type.

• Lookup a cost type by name: SELECT cost_type_id, costing_method_type, frozen_standard_flag FROM bom.cst_cost_types WHERE cost_type = :name AND organization_id = :org_id — this query is served by CST_COST_TYPES_U2.
• Identify the frozen cost type: filter FROZEN_STANDARD_FLAG = 1 for a given ORGANIZATION_ID to drive standard-cost inquiries.
• Rollup configuration reporting: select COST_TYPE, PL_ELEMENT_FLAG, PL_RESOURCE_FLAG, PL_OPERATION_FLAG, PL_ACTIVITY_FLAG, BOM_SNAPSHOT_FLAG to document how each cost type groups its rollup output.
• Item cost reporting: join CST_ITEM_COSTS or CST_ITEM_COST_DETAILS to CST_COST_TYPES on COST_TYPE_ID to label valuation rows with a human-readable cost type name.
• Interface validation: validate inbound COST_TYPE_ID values in MTL_TRANSACTIONS_INTERFACE or CST_ITEM_COSTS_INTERFACE against this hub before processing.

Related Objects

CST_COST_TYPES is referenced by an unusually large number of tables, since essentially every costing table carries a COST_TYPE_ID. The most significant dependencies include:

• CST_ITEM_COSTS and CST_ITEM_COST_DETAILS (COST_TYPE_ID → COST_TYPE_ID) — the primary item cost store.
• CST_ACTIVITY_COSTS, CST_RESOURCE_COSTS, and CST_DEPARTMENT_OVERHEADS (COST_TYPE_ID) — activity, resource, and overhead rates per cost type.
• CST_COST_TYPE_HISTORY and CST_COST_UPDATES — audit trail of cost type changes and pending updates.
• MTL_MATERIAL_TRANSACTIONS (COST_TYPE_ID) — transaction cost attribution.
• CST_LE_COST_TYPES (COST_TYPE_ID, PAC_RATES_COST_TYPE_ID) — the dual reference used by Landed Cost.
• CM_RLUP_CTL, CM_CUPD_CTL, and CM_ACPR_CTL — Cost Management concurrent-process control tables that key their work by COST_TYPE_ID.
• WIP_PARAMETERS and WIP_ACCOUNTING_CLASSES — work-in-process defaults referencing the cost type.
• MTL_ABC_COMPILE_HEADERS (COST_TYPE) — ABC compilation keyed by cost type name rather than ID.

Because the table is a dependency hub, changes or deletions of a cost type row are constrained by these foreign keys and should be performed through the Cost Management setup forms rather than by direct DML.