Results for “cst_activities”

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

Overview

CST_ACTIVITIES is the master definition table for activity-based costing within Oracle E-Business Suite. Owned by the BOM (Bills of Material) schema, it stores the activity records that identify discrete cost-generating activities performed during manufacturing, such as setup, run, and material-handling tasks. In Oracle EBS 12.1.1 and 12.2.2, this table underpins both standard Bills of Material costing and Work in Process (WIP) transaction accounting by providing the activity dimension against which resource charges, overhead assignments, and item cost details are recorded.

The table carries a heuristic Data Vault classification of hub, which is a natural modeling suggestion: CST_ACTIVITIES stores the durable, business-key-driven identity of each activity, while surrounding cost and transaction tables act as satellites and links referencing it. Its central position in the costing model is evidenced by the large number of foreign keys pointing into it from both the BOM and CST/WIP application families.

Key Information Stored

The table contains 34 documented columns. The most significant include:

• ACTIVITY_ID — surrogate primary key (CST_ACTIVITIES_PK) and also the sole column of unique index CST_ACTIVITIES_U1.
• ORGANIZATION_ID and ACTIVITY — together form business-key candidate CST_ACTIVITIES_U2, enforcing uniqueness of an activity name within an inventory organization.
• DESCRIPTION — the user-facing name or explanation of the activity.
• DEFAULT_BASIS_TYPE — the default basis used to allocate activity costs.
• DISABLE_DATE — controls the active lifespan of the activity definition.
• OUTPUT_UOM — the unit of measure for activity output.
• VALUE_ADDED_ACTIVITY_FLAG — indicates whether the activity is value-added, supporting cost analysis and reporting.
• ZD_EDITION_NAME — the edition discriminator used in the 12.2.2 schema, participating in both unique indexes.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and the 15 ATTRIBUTE flex columns along with REQUEST_ID, PROGRAM_ID, and related program columns for concurrent processing traceability.

Common Use Cases and Queries

CST_ACTIVITIES is typically queried to resolve activity names for costing reports, to validate activity setup before resource assignment, and to join transaction-level cost records to their activity definitions. A representative reporting query lists active activities in an organization:

• SELECT ACTIVITY_ID, ACTIVITY, DESCRIPTION, DEFAULT_BASIS_TYPE, OUTPUT_UOM FROM CST_ACTIVITIES WHERE ORGANIZATION_ID = :org AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE);

A common join pattern connects activity costs and WIP transactions to obtain activity-level cost drivers:

• SELECT a.ACTIVITY, c.COST_ELEMENT_ID, c.ACTIVITY_COST FROM CST_ACTIVITIES a JOIN CST_ACTIVITY_COSTS c ON c.ACTIVITY_ID = a.ACTIVITY_ID WHERE a.ORGANIZATION_ID = :org;

Reporting use cases include activity-based overhead analysis via CST_DEPARTMENT_OVERHEADS, tracing resource charges from BOM_OPERATION_RESOURCES, and reconciling WIP cost transactions against MTL_TRANSACTION_ACCOUNTS by activity dimension.

Related Objects

The FK relationship data identifies several significant dependent tables that reference CST_ACTIVITIES on ACTIVITY_ID (or DEFAULT_ACTIVITY_ID in one case):

• BOM_OPERATION_RESOURCES — joins on ACTIVITY_ID; links operation resources to their activity.
• BOM_RESOURCES — joins on DEFAULT_ACTIVITY_ID; supplies the default activity for a resource.
• CST_ACTIVITY_COSTS — joins on ACTIVITY_ID; stores the cost rates per activity.
• CST_DEPARTMENT_OVERHEADS — joins on ACTIVITY_ID; maps departmental overheads to activities.
• CST_ITEM_COST_DETAILS — joins on ACTIVITY_ID; records item cost breakdowns by activity.
• MTL_TRANSACTION_ACCOUNTS — joins on ACTIVITY_ID; holds accounting entries stamped with activity.
• WIP_TRANSACTIONS and WIP_TRANSACTION_ACCOUNTS — join on ACTIVITY_ID; capture shop-floor activity consumption and its accounting.
• WIP_OPERATION_RESOURCES and WIP_SUB_OPERATION_RESOURCES — join on ACTIVITY_ID; assign activities to work-in-process operation resources.

Together these relationships confirm CST_ACTIVITIES as the hub of activity-based costing, connecting BOM setup data with cost accumulation and accounting across the manufacturing lifecycle.