Results for “cwm2_olap_catalog”

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

Overview

The OLAPSYS.CWM2_OLAP_CATALOG package is part of the Oracle OLAP metadata infrastructure delivered under the OLAPSYS schema, which implements the Common Warehouse Metamodel (CWM2) API. Although it resides in the OLAPSYS schema rather than within the APPS schema directly, it is exposed to Oracle E-Business Suite environments (12.1.1 and 12.2.2) through public synonyms such as CWM2_OLAP_CATALOG that are referenced by OLAPSYS-owned code. Its business function is to manage the lifecycle and descriptive attributes of OLAP catalogs — the top-level containers that organize OLAP analytic workspaces, dimensions, cubes, measures, and related metadata objects within the OLAP repository. In effect, this package provides the administrative foundation upon which higher-level OLAP metadata operations are built, allowing the catalog structure to be created, named, described, re-parented, and removed programmatically.

Key Procedures and Functions

The ETRM documentation records eight documented units within this package. Based on documented naming and the standard CWM2 catalog API, they serve the following purposes:

• CREATE_CATALOG — Creates a new OLAP catalog object in the OLAP metadata repository, establishing the top-level container for subsequent metadata definitions.
• SET_CATALOG_NAME — Assigns or changes the descriptive name associated with an existing catalog.
• SET_DESCRIPTION — Sets or updates the free-text description stored for a catalog, supporting documentation and discoverability.
• SET_PARENT_CATALOG — Defines or reassigns the parent catalog, enabling hierarchical nesting of catalogs.
• DROP_CATALOG — Removes an existing catalog and its associated metadata definition from the repository.
• LOCK_CATALOG — Places a lock on a catalog to prevent conflicting concurrent modification during metadata operations.
• ADD_CATALOG_ENTITY — Associates an entity (such as a dimension, cube, or workspace) with a given catalog.
• REMOVE_CATALOG_ENTITY — Detaches a previously associated entity from a catalog.

These procedures collectively provide CRUD and structural-management capability over catalog metadata. No parameter lists are documented in the ETRM extract, so signatures should be verified against the actual package specification at runtime.

Tables Accessed

The ETRM metadata for this object indicates that its table access is realized through OLAPSYS-owned repository objects rather than direct APPS-schema synonyms; the documented reference list shows dependencies on SYS.STANDARD and internal OLAPSYS objects. Practically, the package reads from and writes to the OLAP metadata repository tables that store catalog definitions, names, descriptions, parent-child relationships, and catalog-entity associations. Because the CWM2 catalog layer underpins the analytic workspace metadata model, these operations persist the catalog header record and the join records linking catalogs to their constituent entities. The absence of explicit APPS synonym references confirms that this package operates within the OLAPSYS metadata domain and is not directly bound to transactional EBS application tables.

Usage Notes

This package is an internal component of the Oracle OLAP CWM2 API rather than a user-facing EBS feature. It is referenced by the sibling packages CWM2_OLAP_CATALOG (the public synonym) and CWM2_OLAP_DELETE, and is itself documented as referencing the single dependent package listed in the ETRM extract. Typical invocation occurs through:

• OLAP metadata management routines executed during analytic workspace deployment and maintenance;
• Upgrade, patch, and metadata synchronization operations that create or reorganize catalog structures;
• Custom PL/SQL solutions that programmatically build OLAP metadata using the CWM2 API conventions.

Direct invocation from EBS forms or concurrent programs is uncommon; the package is generally called indirectly by higher-level OLAP administrative code. In 12.1.1 and 12.2.2, the OLAPSYS schema and its packages are present as part of the database-tier OLAP option, but they should not be modified manually. Any custom development referencing CWM2_OLAP_CATALOG should treat it as an Oracle-controlled interface and validate behavior against the specific database patch level, since catalog metadata structures are sensitive to upgrades.