Results for “cst_activities_v”

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

Overview

CST_ACTIVITIES_V is an APPS-owned, VALID database view in the Oracle E-Business Suite BOM – Bills of Material product family. It exposes activity definitions used by Oracle Cost Management and appears as a SINGLE-ORG view, meaning it is intended for deployment against a single operating unit or organization context rather than the consolidated multi-org reporting pattern. In Oracle EBS 12.1.1 and 12.2.2 this view is documented under the ETRM (E-Business Suite Technical Reference Manual) as a reporting and integration access point over the underlying CST_ACTIVITIES table.

The view denormalizes the activity's basis code by joining to the MFG_LOOKUPS view for lookup type CST_BASIS, so consumers receive both the coded value in DEFAULT_BASIS_TYPE and its user-facing meaning in the BASIS column. This makes the view convenient for reports, interfaces, and conversion programs that need readable activity attributes without performing an explicit lookup join. The presence of the MULTIPLE_ORG_FLAG derived column indicates the view also signals whether the activity is defined at a single organization level or shared.

Underlying Base Objects

Per the documented view text, CST_ACTIVITIES_V is defined over two referenced objects: CST_ACTIVITIES, exposed through a SYNONYM, and MFG_LOOKUPS, which is itself a VIEW. The join is an outer join from CST_ACTIVITIES (alias CA) to MFG_LOOKUPS (alias BASIS), constrained by:

• BASIS.LOOKUP_TYPE (+) = 'CST_BASIS'
• BASIS.LOOKUP_CODE (+) = CA.DEFAULT_BASIS_TYPE

Because the lookup join is outer, activities with a null or unrecognized DEFAULT_BASIS_TYPE are still returned, with BASIS null. The view selects CA.ROWID directly, and the ORACLE column is derived via DECODE(CA.ORGANIZATION_ID, NULL, 1, 2), which yields MULTIPLE_ORG_FLAG. A null ORGANIZATION_ID produces 1, indicating the activity is not organization-specific; a populated ORGANIZATION_ID produces 2, indicating an organization-level activity. The view does not join to MTL_SYSTEM_ITEMS or any organization master, so no organization name validation is performed within the view itself.

Key Columns

• ACTIVITY_ID — Primary identifier for the activity record.
• ACTIVITY — The activity name or code as entered by the user.
• ORGANIZATION_ID — Owning organization; null when the activity is not organization-specific.
• MULTIPLE_ORG_FLAG — Derived flag: 1 when ORGANIZATION_ID is null, 2 otherwise.
• DESCRIPTION — Free-text description of the activity.
• DEFAULT_BASIS_TYPE — Coded basis value, the column most frequently searched for by users and the driver of the lookup join.
• BASIS — The MFG_LOOKUPS meaning for DEFAULT_BASIS_TYPE under lookup type CST_BASIS.
• DISABLE_DATE — Date the activity becomes inactive, supporting effective-dated reporting.
• OUTPUT_UOM — Unit of measure for activity output.
• VALUE_ADDED_ACTIVITY_FLAG — Indicates whether the activity is treated as value-added.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments passed through from the base table.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN for audit reporting.

Common Use Cases and Queries

Typical uses include activity listings for cost rollup analysis, validation of DEFAULT_BASIS_TYPE values ahead of data conversion, and extracts feeding external cost models that require the lookup meaning rather than the code.

• Listing active activities with readable basis: SELECT ACTIVITY, DESCRIPTION, DEFAULT_BASIS_TYPE, BASIS, OUTPUT_UOM FROM APPS.CST_ACTIVITIES_V WHERE DISABLE_DATE IS NULL ORDER BY ACTIVITY;
• Filtering by basis type for audit or reconciliation: SELECT ACTIVITY_ID, ACTIVITY, ORGANIZATION_ID, DEFAULT_BASIS_TYPE FROM APPS.CST_ACTIVITIES_V WHERE DEFAULT_BASIS_TYPE = :p_basis_type;
• Detecting organization-independent activities: SELECT ACTIVITY, MULTIPLE_ORG_FLAG FROM APPS.CST_ACTIVITIES_V WHERE MULTIPLE_ORG_FLAG = 1;
• Finding records whose basis code has no valid lookup: SELECT ACTIVITY, DEFAULT_BASIS_TYPE FROM APPS.CST_ACTIVITIES_V WHERE BASIS IS NULL AND DEFAULT_BASIS_TYPE IS NOT NULL;

Queries should be issued against the APPS schema, and reporting users should be granted appropriate read privileges on the synonym rather than on the base table.