Results for “cst_activity_costs”

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

Overview

CST_ACTIVITY_COSTS is a cost management table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the cost associated with a specific manufacturing or business activity, resolved by activity, cost type, and organization. In the Oracle Cost Management model, activities represent the discrete operations — setup, run, move, resource usage, and overhead absorption — that consume resources during production, and this table holds the monetary and unit-based results of costing those activities.

Under a heuristic Data Vault classification mined from its foreign key structure, CST_ACTIVITY_COSTS is best modeled as a link entity. It resolves the many-to-many relationship between activities (CST_ACTIVITIES) and cost types (CST_COST_TYPES) within an organization, and it carries descriptive cost measures. Note that this is a modeling suggestion inferred from the FK topology, not an Oracle-declared classification.

Key Information Stored

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

• ACTIVITY_ID — identifies the activity being costed; part of the composite primary key and a foreign key to CST_ACTIVITIES.
• COST_TYPE_ID — identifies the cost type (for example frozen, average, or standard) under which the cost is recorded; foreign key to CST_COST_TYPES.
• ORGANIZATION_ID — the inventory/costing organization scope for the record.
• TOTAL_COST — the total cost accumulated for the activity within the given cost type and organization.
• TOTAL_ACTIVITY_UNITS — the total activity units (such as machine hours, labor hours, or move quantities) consumed.
• UNIT_COST — the derived cost per activity unit, typically the ratio of total cost to activity units.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns providing change tracking.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the process that created or last refreshed the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) segment, available for customer-defined cost detail.

The surrogate primary key is CST_ACTIVITY_COSTS_PK, defined over (ACTIVITY_ID, COST_TYPE_ID, ORGANIZATION_ID). The unique index CST_ACTIVITY_COSTS_U1 covers the same three columns in the order (ACTIVITY_ID, ORGANIZATION_ID, COST_TYPE_ID) and serves as the business-key candidate.

Common Use Cases and Queries

Typical uses include activity-based cost reporting, overhead absorption analysis, unit cost trending, and reconciliation between frozen and current cost types. Analysts commonly join this table to activities and cost types to produce readable activity cost rollups.

• Retrieving unit costs for a given organization and cost type:

  SELECT activity_id, cost_type_id, organization_id,
         total_cost, total_activity_units, unit_cost
    FROM   cst_activity_costs
   WHERE   organization_id = :org_id
     AND   cost_type_id    = :cost_type_id;

• Joining to the activity definition to obtain activity names and descriptions:

  SELECT a.activity, c.unit_cost, c.total_cost
    FROM   cst_activity_costs c, cst_activities a
   WHERE   c.activity_id = a.activity_id
     AND   c.organization_id = :org_id;

• Comparing cost types side by side to detect variances between standard and frozen activity costs.
• Feeding downstream cost rollup or profitability reports where activity consumption drives product cost.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign key relationships:

• CST_ACTIVITIES — referenced by CST_ACTIVITY_COSTS.ACTIVITY_ID; defines the activity master.
• CST_COST_TYPES — referenced by CST_ACTIVITY_COSTS.COST_TYPE_ID; defines cost type context.
• CST_ACTIVITY_COSTS_PK — primary key constraint on the table.
• CST_ACTIVITY_COSTS_U1 — unique index establishing the business-key candidate.
• Cost Management concurrent programs that populate REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE during activity cost calculation.

Because the table resides in the BOM schema but is consumed across Cost Management and Manufacturing, joins to organization and item master objects are standard when producing end-to-end cost reporting.