Search Results cst_activities_uk1

Overview

The CST_ACTIVITIES table is a core master data table within the Bills of Material (BOM) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the central repository for defining activities used in activity-based costing and manufacturing accounting. An activity, in this context, represents a specific type of work or operation performed within a manufacturing organization, such as machine setup, labor, or quality inspection. The table's primary role is to provide a standardized list of activities that can be assigned to resources, operations, and cost transactions, enabling the detailed collection, allocation, and analysis of overhead and resource costs throughout the production lifecycle.

Key Information Stored

The table's structure is designed to uniquely identify and describe activities within a specific organizational context. The primary key is ACTIVITY_ID, a unique system-generated identifier. A critical unique key constraint (CST_ACTIVITIES_UK1) enforces the combination of the ACTIVITY column, which holds the name or code of the activity (e.g., 'MACHINE', 'LABOR'), and the ORGANIZATION_ID, which ties the activity definition to a specific inventory organization. This ensures activity names are unique per organization. While the provided metadata does not list all columns, typical columns in this table would include descriptive fields like DESCRIPTION, a DISABLE_DATE for deactivating activities, and various WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) for auditing.

Common Use Cases and Queries

The primary use case is the setup and maintenance of activity-based costing models. Activities defined here are linked to departmental overhead rates and resources to calculate accurate product costs. Common reporting and query scenarios include listing all active activities for an organization, identifying activities used in specific cost transactions, or validating activity assignments. A typical SQL query to retrieve activity details would be:

• SELECT activity_id, activity, description FROM bom.cst_activities WHERE organization_id = :org_id AND disable_date IS NULL ORDER BY activity;

Another critical use case is troubleshooting cost collection and accounting entries. When reviewing detailed cost transactions in tables like CST_ITEM_COST_DETAILS or WIP_TRANSACTION_ACCOUNTS, joining to CST_ACTIVITIES provides the human-readable activity name for analysis.

Related Objects

As indicated by its extensive foreign key relationships, the CST_ACTIVITIES table is a fundamental reference point for numerous transactional and setup tables across Cost Management, Bills of Material, and Work in Process. Key related objects include:

• Costing & Accounting: CST_ACTIVITY_COSTS (stores cost rates per activity), CST_ITEM_COST_DETAILS, CST_AE_LINES, MTL_TRANSACTION_ACCOUNTS.
• Resource & Routing Definition: BOM_RESOURCES (default activity), BOM_OPERATION_RESOURCES, BOM_STD_OP_RESOURCES.
• Work in Process Execution: WIP_OPERATION_RESOURCES, WIP_TRANSACTIONS, WIP_TRANSACTION_ACCOUNTS, WIP_COST_TXN_INTERFACE.
• Overhead Setup: CST_DEPARTMENT_OVERHEADS, which links activities to departments for applying overhead costs.

This network of dependencies underscores the table's integral position in connecting engineering and routing definitions (BOM) with financial cost accounting (CST).