Search Results set_short_description




Overview

The OLAPSYS.CWM2_OLAP_MEASURE package is a component of the Oracle OLAP metadata management infrastructure, part of the CWM2 (Common Warehouse Metamodel) API used by Oracle's analytical workspace and OLAP catalog. Within Oracle EBS 12.1.1 and 12.2.2, the package is owned by the OLAPSYS schema and is classified under the ETRM as an OTHER API. Its purpose is to manage the lifecycle and descriptive metadata of measures — the quantitative data values (such as Sales Amount, Quantity, or Cost) that are associated with a cube or fact object in an OLAP analytic workspace definition.

The package provides stored procedures to create, rename, describe, lock, and drop measures, thereby maintaining consistency between the OLAP catalog metadata and the underlying dimensional model. In EBS deployments, this metadata supports the analytic workspace objects leveraged by Oracle Business Intelligence and Discoverer-based reports against the EBS data warehouse.

Key Procedures and Functions

ETRM documents seven procedures in this package:

  • CREATE_MEASURE — Creates a new measure definition. It accepts the cube owner, cube name, measure name, display name, short description, and full description, establishing the measure's identifying and descriptive attributes in the OLAP metadata repository.
  • SET_MEASURE_NAME — Renames an existing measure, taking the cube owner, cube name, current measure name, and the new measure name. This is the procedure used when a measure's internal identifier must change.
  • SET_DISPLAY_NAME — Updates the user-facing display name of a measure. This is the procedure most relevant to the term searched (set_display_name), as it controls the label presented in OLAP clients and reports without altering the underlying measure name.
  • SET_SHORT_DESCRIPTION — Modifies the short description attribute of a measure, typically used for compact captions or tooltips.
  • SET_DESCRIPTION — Updates the full, long description of a measure, providing detailed documentation visible in metadata browsers.
  • DROP_MEASURE — Removes a measure definition from the OLAP metadata repository, identified by cube owner, cube name, and measure name.
  • LOCK_MEASURE — Acquires a lock on the specified measure to serialize concurrent metadata modifications, with an optional wait-for-lock flag defaulting to false.

Tables Accessed

The ETRM metadata excerpt does not enumerate the specific tables referenced via APPS synonyms for this package. Based on the OLAP CWM2 architecture, these procedures operate on the OLAPSYS metadata repository tables that persist cube and measure definitions — the internal CWM2 catalog tables that store measure names, display names, and description attributes. Because the package is owned by OLAPSYS (not APPS), EBS integration typically occurs through qualified references or grants rather than direct APPS synonyms. No tables are documented in the supplied excerpt, and no other packages are documented as referencing this package (referenced by 0 other packages).

Usage Notes

This package is an infrastructure-level API rather than an end-user-facing application program. It is typically invoked by Oracle OLAP administrative utilities, metadata synchronization routines, or custom PL/SQL code that programmatically manages analytic workspace definitions. Because it is not referenced by any other documented package and no APPS synonyms are listed, it is unlikely to be called directly from standard EBS Forms or concurrent programs; instead, it operates beneath the OLAP management tooling layer.

When customizing or extending EBS analytics, the SET_DISPLAY_NAME, SET_DESCRIPTION, and related procedures may be invoked from custom concurrent programs or scripts to relabel measures without recreating them. Modifications should be performed by a user with privileges on the OLAPSYS schema, and the LOCK_MEASURE procedure should be considered when concurrent updates are possible. Direct manipulation is best limited to controlled administrative windows, as altering OLAP catalog metadata can affect downstream reporting and analytic workspace refresh behavior.