Search Results activity_output_uom

Overview

CST_XLA_ACTIVITY_REF_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is catalogued under the BOM (Bills of Material) product family but functions as a reference denormalization layer for Costing activity data consumed by the Subledger Accounting (XLA) engine. The name prefix CST_XLA_ACTIVITY_REF_V indicates that the view supplies the activity dimension required when SLA derives the accounting for cost transactions in Oracle Cost Management.

The view exposes the identifying attributes of an activity together with the full set of fifteen descriptive flexfield (DFF) attribute columns and the DFF structure name. This makes it the standard reference for reporting and integration when activity-level context is needed in accounting, costing, or BOM-driven cost rollup logic.

The object is documented with a status of VALID, confirming it is compiled and available for query in a supported environment.

Underlying Base Objects

The view is defined over a single base object, documented in the ETRM metadata as the synonym CST_ACTIVITIES. The view text shows a straightforward projection with column aliasing:

• ACTIVITY is renamed to ACTIVITY_NAME.
• DESCRIPTION becomes ACTIVITY_DESCRIPTION.
• OUTPUT_UOM becomes ACTIVITY_OUTPUT_UOM.
• VALUE_ADDED_ACTIVITY_FLAG is decoded from the stored YES/NO form into a compact Y/N flag.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 are surfaced with the ACTIVITY_ prefix to disambiguate them from attributes belonging to other cost objects.

Because the view is read-only and performs no joins, it inherits the row set of CST_ACTIVITIES without aggregation or filtering. Any security or org-level restriction applicable to the base table is therefore not masked by the view.

Key Columns

• ACTIVITY_ID — Primary identifier of the activity; the join key to cost transaction and XLA reference tables.
• ACTIVITY_NAME — User-visible activity name.
• ACTIVITY_DESCRIPTION — Free-text description of the activity.
• ACTIVITY_OUTPUT_UOM — Unit of measure for the activity output, used in cost-per-unit derivation.
• VALUE_ADDED_ACTIVITY_FLAG — Y/N indicator of whether the activity adds value; relevant to cost analysis and activity-based reporting.
• ACTIVITY_ATTRIBUTE_CATEGORY — The DFF structure (context) name. This is the column most commonly referenced when reporting on activity_attribute_category, since it identifies which flexfield context is active for the activity.
• ACTIVITY_ATTRIBUTE1 … ACTIVITY_ATTRIBUTE15 — The individual DFF segment values, valid only when the corresponding category is populated.

Common Use Cases and Queries

Typical uses include activity-level SLA reporting, validation of DFF setup, and integration extracts feeding costing analytics. To list all populated DFF contexts:

SELECT ACTIVITY_ID, ACTIVITY_NAME, ACTIVITY_ATTRIBUTE_CATEGORY
FROM APPS.CST_XLA_ACTIVITY_REF_V
WHERE ACTIVITY_ATTRIBUTE_CATEGORY IS NOT NULL
ORDER BY ACTIVITY_NAME;

To inspect a specific context and its segments:

SELECT ACTIVITY_ID, ACTIVITY_NAME, ACTIVITY_ATTRIBUTE_CATEGORY,
       ACTIVITY_ATTRIBUTE1, ACTIVITY_ATTRIBUTE2
FROM APPS.CST_XLA_ACTIVITY_REF_V
WHERE ACTIVITY_ATTRIBUTE_CATEGORY = 'COST_ACTIVITY';

To flag value-added activities for cost analysis:

SELECT ACTIVITY_ID, ACTIVITY_NAME, VALUE_ADDED_ACTIVITY_FLAG
FROM APPS.CST_XLA_ACTIVITY_REF_V
WHERE VALUE_ADDED_ACTIVITY_FLAG = 'Y';

Because the view performs no filtering, adding the ATTRIBUTE_CATEGORY predicate is the recommended access path when querying large activity sets, and joins back to CST_ACTIVITIES should be made on ACTIVITY_ID rather than on name to avoid duplicates.