Results for “cwm2_olap_manager”

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

Overview

OLAPSYS.CWM2_OLAP_MANAGER is the diagnostic and tracing utility package for the Oracle OLAP (Oracle9i/10g OLAP) analytic workspace infrastructure delivered with the Oracle database in which Oracle E-Business Suite 12.1.1 and 12.2.2 are deployed. Although the package is owned by the OLAPSYS schema rather than by APPS, it is exposed to the E-Business Suite application schema and is referenced by 23 other PL/SQL packages, making it a shared logging service for OLAP metadata build, refresh, and validation operations. Its business function is to provide a controlled mechanism for capturing, echoing, and persisting diagnostic messages during OLAP metadata processing; the ETRM classification "OTHER" reflects that it is an internal Oracle-supplied infrastructure package rather than an EBS business API.

Key Procedures and Functions

The package exposes nine documented program units. SET_ECHO_ON and SET_ECHO_OFF toggle whether log messages are echoed to the caller (typically DBMS_OUTPUT); they act as global switches governing verbosity. BEGIN_LOG opens a logging session, directing output to a named directory and file with an optional append behaviour, and END_LOG closes that session and flushes any buffered content. LOG_NOTE writes an informational message subject to the current echo and logging settings; LOG_NOTE_FORCED writes the same style of message unconditionally, bypassing echo suppression so that critical notes are always emitted. LOG_MESSAGE records a message identified by name together with up to five substitution text fragments, allowing parameterised, translatable diagnostic strings; LOG_MESSAGE_FORCED performs the identical operation but ignores the normal suppression/echo controls, guaranteeing the message reaches the log. LOG_RAW_MESSAGES emits accumulated raw message buffers, typically used to dump low-level OLAP engine output. The "forced" variants, including LOG_MESSAGE_FORCED, are the entry points relied upon when operators require unconditional evidence of execution flow, such as confirming that a specific build step was reached regardless of the prevailing logging configuration.

Tables Accessed

No application tables are referenced directly. The package is documented as using the following via APPS synonyms or database-supplied packages: DBMS_OUTPUT for echoing messages to the session, UTL_FILE for writing the physical log file named in BEGIN_LOG, and UTL_RAW together with PLITBLM for handling raw and line-buffer message payloads. Because all persistence is file- or session-based, the package leaves no rows in EBS application tables.

Usage Notes

This package is not invoked from EBS forms. It is called internally by the OLAP metadata packages and by any custom code that needs consistent OLAP diagnostics — for example, during Analytic Workspace builds, dimension and cube metadata synchronisation, or RDBMS-to-AW mapping refresh. Administrators enable tracing by setting echo on and beginning a log before running the parent OLAP process. The forced procedures should be used sparingly, as they write regardless of suppression settings and can generate substantial output. In EBS 12.1.1 and 12.2.2, availability depends on the database OLAP option and on the APPS user holding the required synonyms and UTL_FILE directory grants.