Results for “cwm2_olap_exceptions”

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

Overview

The OLAPSYS.CWM2_OLAP_EXCEPTIONS package is an internal Oracle OLAP metadata repository component that resides in the OLAPSYS schema, the owner of the OLAP Catalog (CWM2) metadata objects. Its role is to define and manage the exception-handling framework used throughout the CWM2 OLAP API layer. In Oracle E-Business Suite 12.1.1 and 12.2.2, the OLAP Catalog provides the analytic workspace and dimensional metadata model used by tools such as Oracle Discoverer, OracleBI Beans, and the standard EBS analytics that depend on pre-built OLAP dimensions, cubes, and measures. Because the CWM2 packages rely on a shared, consistent error-signaling mechanism, CWM2_OLAP_EXCEPTIONS centralizes the declaration of named exceptions and the associated error-raising and message-retrieval logic for the entire OLAP metadata API surface.

Key Procedures and Functions

The documented metadata lists zero explicitly named procedures or functions for this package. As recorded in the ETRM extract, the package is classified under the generic API type OTHER and exposes no individually documented program units. In practice, the package functions as a supporting definition module rather than a transaction-oriented API: it publishes named PL/SQL exceptions (and, typically, associated error-number constants and message handlers) that are referenced by the surrounding CWM2 packages. Because no parameter signatures are documented, individual callable interfaces should not be assumed; developers should treat the package as an exception-declaration resource consumed indirectly by other CWM2 modules rather than as an entry point invoked directly.

Tables Accessed

The ETRM metadata states that OLAPSYS.CWM2_OLAP_EXCEPTIONS does not reference any database object. Accordingly, the package performs no direct reads or writes against OLAP Catalog tables, and no referenced tables are exposed through APPS synonyms. Its data is entirely declarative — exception names and error message constants — resolved at compile time rather than by SQL access. Any persistence of OLAP metadata occurs in the calling packages (for example, the CWM2 catalog and dimension packages), not within this exception module.

Usage Notes

The package sits at the base of a large dependency chain. The ETRM metadata records that it is referenced by 23 dependent objects, including CWM1_OLAP_VALIDATE_METADATA, CWM2_OLAP_CATALOG, CWM2_OLAP_CLASSIFY, CWM2_OLAP_CUBE, CWM2_OLAP_DELETE, CWM2_OLAP_DIMENSION, CWM2_OLAP_DIMENSION_ATTRIBUTE, CWM2_OLAP_EXPORT, CWM2_OLAP_HIERARCHY, CWM2_OLAP_LEVEL, CWM2_OLAP_LEVEL_ATTRIBUTE, CWM2_OLAP_MANAGER, CWM2_OLAP_MEASURE, CWM2_OLAP_OLAPAPI_ENABLE, CWM2_OLAP_PC_TRANSFORM, CWM2_OLAP_TABLE_MAP, CWM2_OLAP_UTILITY, CWM2_OLAP_VALIDATE, CWM2_OLAP_VALIDATE_METADATA, CWM2_OLAP_VERIFY_ACCESS, DBMS_AWM, DBMS_AWM_PRV, and DBMS_ODM. It is also granted to PUBLIC, reflecting its broad internal availability. Because its dependencies run one direction — the package references nothing while being referenced by many — it must remain VALID for the OLAP Catalog APIs to compile and function. EBS DBAs typically encounter it during OLAP Catalog validation or when recompiling invalid OLAP objects after patching or database upgrades; direct invocation from Oracle Forms, concurrent programs, or custom code is neither expected nor supported.