Search Results pji_mt_measures_v




Overview
Explore in AI Chat

Overview

PJI_MT_MEASURES_V is a reporting view owned by the APPS schema in Oracle EBS Project Intelligence (PJI). It presents a consolidated, denormalized picture of the measures that Project Intelligence uses for performance reporting, analytics, and integration with external tools. A measure in this context represents an individual quantitative indicator—such as cost variance, earned value, budget-to-actual, or a custom formula—organized within a measure set.

The view joins the measure-level definition view (PJI_MT_MEASURES_VL) to the measure-set-level definition view (PJI_MT_MEASURE_SETS_VL) so that each row carries both the measure attributes and the descriptive attributes of the set to which it belongs. Because Project Intelligence is used to assemble project performance dashboards, extracts, and third-party BI tooling, PJI_MT_MEASURES_V functions primarily as a discovery and metadata surface: consumers query it to determine which measures exist, how they are grouped, which database column or PL/SQL API supplies their value, and how they should be formatted when displayed.

Underlying Base Objects

The view is defined over two documented base objects, both of which are themselves translated (_VL) views in the APPS schema:

  • PJI_MT_MEASURES_VL — supplies the measure-level rows and is aliased as MSR in the view text. It contributes measure identifiers, measure codes, extended type information, and the PL/SQL API reference used to derive the measure value.
  • PJI_MT_MEASURE_SETS_VL — supplies the measure-set rows and is aliased as MSS. It contributes the measure set code, set type, format, database column name, and the name and description of the set.

The two views are joined on the measure set code (MSR.MEASURE_SET_CODE = MSS.MEASURE_SET_CODE), forming a one-to-many relationship in which a single measure set can own many measures. This join is a pure metadata join; no transactional or fact data is involved. Because both parents are _VL views, the language-specific name and description columns will render in the session language of the querying user.

Key Columns

  • MEASURE_SET_CODE — the identifier of the parent measure set; also the join key between the two base views and the value present in both the MSS and MSR halves of the query.
  • MEASURE_SET_TYPE — classifies the measure set, allowing consumers to distinguish, for example, standard versus user-defined groupings.
  • MEASURE_FORMAT — the display format applied to the measure value when rendered in Project Intelligence reporting.
  • DB_COLUMN_NAME — a documented column of the view and, per the user search term, the most frequently interrogated attribute. It identifies the underlying database column associated with the measure set and is typically used when mapping measures to fact tables or building extracts.
  • MEASURE_SET_NAME / MEASURE_SET_DESCRIPTION — language-sensitive descriptive attributes of the set.
  • MEASURE_ID — the unique identifier of the individual measure.
  • MEASURE_SET_CDOE — a second occurrence of the measure set code carried from the MSR side (note the documented spelling anomaly in the view definition).
  • MEASURE_CODE — the business-facing code for the measure, used in formulas and API calls.
  • XTD_TYPE — the extended type of the measure, indicating the data type or functional category of the measure value.
  • PL_SQL_API — the name of the PL/SQL API that computes or returns the measure value, essential when replicating measure logic outside of Project Intelligence.
  • MEASURE_NAME / MEASURE_DESCRIPTION — language-sensitive naming and documentation for the individual measure.

Common Use Cases and Queries

The view is most commonly used for metadata discovery, particularly when locating the database column backing a measure (DB_COLUMN_NAME) or the API that supplies its value. A typical query lists all measures within a given set:

  • SELECT measure_code, measure_name, db_column_name, pl_sql_api FROM pji_mt_measures_v WHERE measure_set_code = :set_code;
  • SELECT measure_set_name, measure_code, measure_name, xtd_type, measure_format FROM pji_mt_measures_v ORDER BY measure_set_name, measure_name;
  • SELECT DISTINCT db_column_name FROM pji_mt_measures_v WHERE db_column_name IS NOT NULL;

These queries support extract design, documentation, and integration development. Because the view is a metadata join over translated parents, consumers should filter on the measure set or measure codes rather than expect transactional volumes, and should be aware that rows repeat the measure-set attributes for each measure in the set.