Results for “pji_mt_measure_sets_vl”

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

Overview

PJI_MT_MEASURE_SETS_VL is an Oracle EBS 12.1.1 / 12.2.2 view owned by the APPS schema and registered as a VALID database object. It belongs to the PJI product family — Project Intelligence — which Oracle has since designated Obsolete in the E-Business Suite technology stack. Nevertheless, the view remains in released schemas because dependent metadata and historical reporting objects were never physically removed during upgrades.

The view presents a multilingual (translated) representation of measure sets used for reporting in Oracle Projects. A "measure set" is a named grouping of project performance indicators or metrics that Project Intelligence uses to render analyses, dashboards, and extract-style reports. By exposing both the technical definition of a measure set and its user-facing translated name and description, PJI_MT_MEASURE_SETS_VL allows report builders and integration developers to resolve a measure set code into a display label without joining the _B and _TL tables manually. In practice, this view functions as the primary query surface for customers or extension code that needs translated measure set metadata.

Underlying Base Objects

Two documented base objects are referenced by the view, both exposed to APPS as synonyms:

• PJI_MT_MEASURE_SETS_B — the base (non-translated) table holding the measure set definition, including its code, type, format, source, formula, and DB column mapping.
• PJI_MT_MEASURE_SETS_TL — the translation table supplying the language-specific NAME and DESCRIPTION values.

The join key is MEASURE_SET_CODE, combined with a language predicate of T.LANGUAGE = USERENV('LANG'). This is the standard EBS MLS (Multi-Lingual Support) pattern: the _B table provides one row per measure set, and the _TL table provides one row per installed language, with the view filtering to the session's current language at query time. All base table columns are exposed, together with the translated NAME and DESCRIPTION.

Key Columns

• ROW_ID — the ROWID of the base _B row, used for row identification and updates through the view.
• MEASURE_SET_CODE — the unique identifier for the measure set; join key between the _B and _TL tables.
• MEASURE_SET_TYPE — classifies the measure set (for example, the type of metric grouping it represents).
• MEASURE_FORMAT, MEASURE_SOURCE, MEASURE_FORMULA — define how the measure set's values are formatted, where they originate, and how they are calculated.
• DB_COLUMN_NAME — the underlying database column mapped to the measure set.
• NAME, DESCRIPTION — the translated display name and description, resolved from the _TL table for the session language.
• OBJECT_VERSION_NUMBER — OAF-style optimistic locking column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit trail.

Common Use Cases and Queries

Because Project Intelligence is obsolete, most usage involves reading measure set metadata for migration, reconciliation, or historical reference rather than building new PI reports. Typical scenarios include:

• Listing all defined measure sets in the current session language for documentation or migration mapping.
• Inspecting MEASURE_FORMULA and DB_COLUMN_NAME to understand how a specific KPI was computed before migrating to a successor reporting product.
• Resolving a measure set code captured in legacy extract data into its translated name.

Sample query enumerating measure sets:

SELECT measure_set_code, name, measure_set_type, measure_source, db_column_name
FROM apps.pji_mt_measure_sets_vl
ORDER BY measure_set_code;

Restricting to a known measure set:

SELECT name, description, measure_formula, last_update_date
FROM apps.pji_mt_measure_sets_vl
WHERE measure_set_code = 'YOUR_CODE';

Because the view is a synonym-based APPS object, queries should be fully qualified as APPS.PJI_MT_MEASURE_SETS_VL or issued from an APPS-initialized session. As the product is obsolete, no new functionality should be built on this view; it is retained primarily for backward compatibility.