Search Results msd_aw_loader_pvt

Overview

MSD_AW_LOADER_PVT is a private (PVT) PL/SQL package body owned by APPS in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to load and maintain Oracle OLAP Analytic Workspace (AW) objects from the relational staging structures used by the Demand Planning and related Advanced Planning products in the MSD schema. The package acts as an integration bridge between the EBS metadata tables and the embedded OLAP engine, invoking the DBMS_AW built-in through a controlled, repeatable loading interface.

The header comment identifies the release as 120.0 (2005/05/25), confirming this package has been stable across both R12 codelines. The naming convention _PVT signals that the package is not part of the public API surface; it is intended to be called from other MSD packages, concurrent programs, or administration routines within APPS, not from customer extensions.

Key Procedures and Functions

• CALL_AW — A helper function that executes an arbitrary AW command through DBMS_AW and trims leading newline characters from the returned result string.
• ATTACH_AW — Attaches an analytic workspace read/write using the schema and workspace name supplied by the caller. It detects the execution context (development session as MSD versus ADPATCH session as APPS) and conditionally detaches and re-attaches the AW so the correct alias resolves.
• CREATE_OBJECT — Creates an OLAP object (dimension, variable, or similar) in the attached workspace.
• LOAD_DIMENSION_INT — Loads the internal representation of a dimension, typically from staging tables into the AW dimension.
• LOAD_DIMENSION_VALUES — Populates the members or values associated with a dimension.
• LOAD_FORMULA — Transfers formula definitions into the analytic workspace.
• LOAD_MODEL — Loads model metadata and definitions used by the planning engine.
• LOAD_PROGRAM — Loads program definitions into the workspace. This is the procedure most frequently searched for, because it is the entry point used when synchronising planning program metadata into the OLAP environment.
• LOAD_PROPERTIES — Loads object properties or attribute values for previously created AW objects.
• LOAD_VALUESET — Loads value set definitions consumed by the planning engine.
• UPDATE_AW — Persists changes made to the workspace, committing or updating the AW after a batch of loads.

All ten entries are documented in the ETRM metadata for release 12.2.2; parameter lists are not reproduced here because the source excerpt is truncated.

Tables Accessed

The ETRM documentation lists three dependencies, all of which are APPS synonyms for built-in packages rather than ordinary application tables:

• DBMS_AW — The Oracle-supplied PL/SQL interface to the OLAP engine, used for interp (interpret/execute AW commands) and execute.
• DBMS_LOB — Used for large object manipulation, typically when streaming long formula or model definitions into the workspace.
• PLITBLM — A helper package used for table-driven parsing and iteration of PL/SQL collections during the load routines.

The package references no application data tables directly; it reads from staging and metadata structures owned elsewhere in the MSD schema and writes only into the attached analytic workspace.

Usage Notes

MSD_AW_LOADER_PVT is invoked internally. Typical entry points are the MSD concurrent programs that build or refresh analytic workspaces, and administrative scripts run as APPS during ADPATCH or during a manual workspace refresh. Because ATTACH_AW distinguishes between development (MSD) and patching (APPS) sessions, integrators should be aware that attaching an AW under the wrong schema context will silently skip the attach step.

The ETRM metadata records Referenced by 0 other packages, indicating no other distributed APPS package calls into this one directly; callers are therefore concurrent programs, forms-level code, or customer scripts. Any custom code that wishes to use these routines must run inside APPS, must have the workspace already attached or allow ATTACH_AW to do so, and should call UPDATE_AW after the load sequence to persist the changes.