Search Results activity_desc

Overview

EDW_OPI_ACTV_ACTV_LCV is a reporting and integration view belonging to the OPI (Operations Intelligence) product family, which is documented as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to source all activities from both Discrete Manufacturing and Process Manufacturing into a single, consolidated activity dimension. The view implements a UNION of two heterogeneous source streams: activity records originating from the OPM (Process Manufacturing) schema, anchored on FM_ACTV_MST, and activity records originating from the Oracle Process/Discrete Costing model, anchored on CST_ACTIVITIES. Each row is tagged with a source discriminator ('-OPM' or '-OPI') embedded in the surrogate key, allowing downstream ETL processes and Operations Intelligence dashboards to distinguish origin systems while consuming a uniform structure.

The view exposes a fixed business key of ALL in the ALL_FK column, indicating that no true hierarchy or parent assignment is derived at this layer; the column exists to satisfy the EDW star-schema contract expected by dependent materialized views and fact loads. Because the object is documented as "Not implemented in this database," it exists in the ETRM repository as a definition only and may not be physically present in a given instance.

Underlying Base Objects

The documented view text references two primary base tables and one support object:

• FM_ACTV_MST — the OPM activity master, supplying ACTIVITY, ACTIVITY_DESC, and COST_ANALYSIS_CODE in the first UNION branch.
• CST_ACTIVITIES — the cost management activity table, supplying ACTIVITY, ACTIVITY_ID, DESCRIPTION, and VALUE_ADDED_ACTIVITY_FLAG in the second branch.
• EDW_LOCAL_INSTANCE — an instance-code lookup joined into both branches to produce a globally unique ACTIVITY primary key via concatenation of the activity identifier and INSTANCE_CODE.

No other base objects are documented in the ETRM metadata, though the OPM branch implies a join to the OPM organization or cost analysis master through the COST_ANALYSIS_CODE value.

Key Columns

• ALL_FK — constant 'ALL'; used as a dummy foreign key for EDW dimension conformance.
• ACTV_PK — concatenated surrogate key in the form ACTIVITY-INSTANCE_CODE-SOURCE, uniquely identifying each activity across instances and modules.
• ACTV_DP — data pattern / display class, always 'ACTV'.
• ACTV_CODE, NAME, ACTV_NAME — activity identifiers and descriptive labels; ACTV_NAME is populated only in the OPI branch.
• COST_ANALYSIS_CODE — the cost analysis grouping from FM_ACTV_MST; NULL for OPI-sourced rows. This is the column most frequently referenced when users search for cost analysis attribution.
• VALUE_ADDED — 1/0 translation of VALUE_ADDED_ACTIVITY_FLAG; NULL for OPM rows.
• USER_ATTRIBUTE1–5 — placeholder descriptive flexfield columns, cast to NULL.
• LAST_UPDATE_DATE, CREATION_DATE — audit timestamps inherited from the source tables.

Common Use Cases and Queries

Typical usage involves activity dimension enrichment for Operations Intelligence fact tables and cross-module activity reporting. A representative query filtering on the cost analysis node is:

• SELECT ACTV_PK, ACTV_CODE, COST_ANALYSIS_CODE FROM EDW_OPI_ACTV_ACTV_LCV WHERE COST_ANALYSIS_CODE = :code;
• SELECT ACTV_PK, NAME, VALUE_ADDED FROM EDW_OPI_ACTV_ACTV_LCV WHERE ACTV_PK LIKE '%-OPI'; — isolates discrete/costing activities only.
• SELECT ACTV_PK FROM EDW_OPI_ACTV_ACTV_LCV WHERE COST_ANALYSIS_CODE IS NULL; — identifies OPM-sourced rows where cost analysis is not applicable.

Because the object is flagged obsolete and not implemented in the reference database, integrators should confirm its presence before deploying dependent reports, and consider whether a successor OPI or analytics view has superseded it in later patch levels.