Search Results set_aggregation_operator




Overview
Explore in AI Chat

Overview

The OLAPSYS.CWM2_OLAP_CUBE package is a component of the Oracle OLAP metadata infrastructure (the CWM2 family of packages) that ships with the Oracle database. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, it provides the programmatic interface used to define, modify, and maintain OLAP cube metadata stored in the OLAP catalog. Cubes are the central analytical objects in the OLAP option, aggregating measure data across one or more dimensions for query and reporting. This package encapsulates the data-definition operations for cubes: creating a cube, associating dimensions with it, setting descriptive attributes and aggregation behaviour, applying locks, and dropping the cube when no longer required. Because it operates on metadata rather than on the physical summary data itself, it is the entry point for any process that needs to register or reshape a cube definition visible to OLAP-aware tools and to the EBS environment.

The package is owned by OLAPSYS and is classified under the generic API classification OTHER in the ETRM repository. It exposes twelve documented procedures and is referenced by one other package, indicating it forms part of a layered metadata API where higher-level routines delegate cube-definition work to it.

Key Procedures and Functions

  • CREATE_CUBE — Creates a new cube definition for a given owner and cube name, accepting a display name, short description, and full description. This is the operation most commonly associated with the search term "create_cube".
  • SET_CUBE_NAME — Renames an existing cube definition.
  • SET_DISPLAY_NAME — Updates the user-facing display name of a cube.
  • SET_SHORT_DESCRIPTION — Updates the short description attribute.
  • SET_DESCRIPTION — Updates the full description attribute.
  • SET_MV_SUMMARY_CODE — Associates a materialized view summary code with the cube, linking the logical cube to its summary storage.
  • DROP_CUBE — Removes a cube definition, with a silent option controlling error feedback.
  • LOCK_CUBE — Obtains a lock on a cube definition, with an optional wait-for-lock flag, protecting metadata during concurrent modification.
  • ADD_DIMENSION_TO_CUBE — Attaches an existing dimension (by owner and name) to a cube.
  • SET_DEFAULT_CUBE_DIM_CALC_HIER — Designates the default calculation hierarchy for a dimension within the cube.
  • SET_AGGREGATION_OPERATOR — Sets the aggregation operator specification that governs how measures are rolled up across the cube's dimensions.
  • REMOVE_DIMENSION_FROM_CUBE — Detaches a dimension from the cube definition.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed via an APPS synonym. PLITBLM is a standard Oracle EBS PL/SQL table used for caching and staging collections during processing, consistent with the package's pattern of reading parameter values into in-memory structures before applying them to the OLAP metadata repository. Because the package is part of the OLAPSYS-owned OLAP catalog layer, its substantive metadata reads and writes target the underlying OLAP dictionary (and, through the SET_MV_SUMMARY_CODE routine, associate cubes with their materialized-view summary definitions). The ETRM metadata documents only PLITBLM explicitly as a referenced table.

Usage Notes

This package is normally invoked programmatically rather than interactively. It is not exposed through a standard EBS form and is not registered as a standalone concurrent program; instead it is called from custom PL/SQL, from other OLAP metadata packages (one package is documented as referencing it), and from administrative or migration scripts that build or rebuild cube definitions. Typical invocation sequences are:

  • Call CREATE_CUBE to register the cube, then ADD_DIMENSION_TO_CUBE for each dimension, followed by SET_AGGREGATION_OPERATOR and SET_DEFAULT_CUBE_DIM_CALC_HIER to complete the definition.
  • Wrap modifications in LOCK_CUBE where concurrent changes are possible.
  • Use DROP_CUBE for cleanup, and the SET_* procedures for incremental metadata adjustments.

Because the routines execute as the invoking user and touch OLAP catalog objects owned by OLAPSYS, callers require appropriate privileges on the package and the underlying metadata. Sites should treat direct calls as controlled administrative operations, test changes in a non-production environment, and confirm behaviour against the specific EBS 12.1.1 or 12.2.2 database release in use, since OLAP catalog internals can differ between database versions.