Results for “cwm2_olap_delete”

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

Overview

OLAPSYS.CWM2_OLAP_DELETE is a component of the Oracle OLAP analytic workspace metadata infrastructure that ships with the database and is exposed within Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Although it resides in the OLAPSYS schema rather than in the APPS schema, the package forms part of the Common Warehouse Metamodel (CWM) API that Oracle EBS relies upon when managing OLAP catalog objects, cubes, dimensions, and measure catalogs that underpin Discoverer, Oracle OLAP, and Business Intelligence reporting layers. The business function of the package is subtractive rather than additive: it provides the documented entry points by which OLAP metadata definitions are removed from the OLAP catalog after they are no longer required or before they are redefined. Its status is VALID in the ETRM registry, confirming the body compiles cleanly in supported EBS releases. The user search term "cwm_utility" reflects the package's close association with the CWM_UTILITY table and the wider CWM utility family, since the delete operations rely on shared classification and utility metadata to locate the objects being purged.

Key Procedures and Functions

The package body exposes four documented procedures. Each name states its own scope and no parameter lists are published in the available metadata; the following descriptions are limited to documented purpose.

• DELETE_DIMENSION — Removes a dimension definition and its dependent metadata from the OLAP catalog, invoking the CWM2_OLAP_DIMENSION and CWM_CLASSIFY infrastructure to clear classification records associated with the dimension.
• DELETE_CUBE — Removes cube definitions from the catalog, operating in conjunction with CWM_OLAP_CUBE and the export tables EXPORTOLAP1_CUBES, EXPORTOLAP2_CUBES and EXPORTOLAPMR_DIMENSIONS so that staged export records are reconciled before deletion.
• DELETE_MEASURE_CATALOG — Purges measure catalog entries, using CWM2_OLAP_CATALOG and the ALL$OLAP_CATALOGS and ALL$OLAP2_CATALOGS views to identify the catalog rows to be removed.
• DELETE_OLAP_CATALOG — Removes an entire OLAP catalog definition, coordinating with CWM2_OLAP_MANAGER and CWM2_OLAP_EXCEPTIONS to preserve error-handling integrity during the cascade.

Tables Accessed

The documented table references, resolved through APPS synonyms, are CWM_CLASSIFY, CWM_OLAP_CUBE, CWM_UTILITY and DBMS_ASSERT. CWM_CLASSIFY stores the classification records that bind OLAP objects to their CWM types and is therefore central to any delete operation. CWM_OLAP_CUBE holds the cube definitions removed by DELETE_CUBE. CWM_UTILITY provides the shared helper metadata consulted across the CWM suite, which explains the "cwm_utility" search association. DBMS_ASSERT is not a table but the Oracle assertion package called to validate schema and object name inputs before dynamic SQL is executed, mitigating SQL injection risk during deletion. The dependency listing additionally shows the package body reading the ALL$OLAP_CATALOGS and ALL$OLAP2_CATALOGS dictionary views and referencing EXPORT2UCATALOG_ENTITY_USES and the EXPORTOLAP family of tables, confirming that deletions must be reconciled against export staging data. CWM2_OLAP_CATALOG, CWM2_OLAP_CUBE, CWM2_OLAP_DIMENSION, CWM2_OLAP_EXCEPTIONS and CWM2_OLAP_MANAGER are referenced as in-schema package dependencies.

Usage Notes

CWM2_OLAP_DELETE is not referenced by any other database object and is not invoked automatically by EBS application forms or concurrent programs. It is called directly, either from SQL*Plus sessions connected as OLAPSYS, from the Oracle Enterprise Manager OLAP administration interface, or from custom PL/SQL maintenance scripts that automate cleanup of obsolete OLAP definitions. Because the procedures remove catalog records and cascade into classification and export metadata, they should be executed only after confirming that dependent Discoverer workbooks, OLAP reports or BI objects will not be invalidated. As the package is owned by OLAPSYS and marked proprietary, custom code should invoke it with fully qualified names and appropriate privileges. The strong presence of DBMS_ASSERT confirms that callers should pass validated object identifiers rather than unsanitized strings. In EBS 12.1.1 and 12.2.2 environments the package is typically exercised during data migration, environment refresh, or decommissioning of legacy OLAP analytic workspaces.