Results for “export_dimension”

5 results




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

Overview

OLAPSYS.CWM2_OLAP_EXPORT is a wrapped PL/SQL package body owned by the OLAPSYS schema and shipped as part of the Oracle OLAP option stack that is installed alongside Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CWM2 (Common Warehouse Metamodel, version 2) family of packages that Oracle OLAP uses to expose analytic workspace metadata through a set of PL/SQL APIs. The package provides the export side of the CWM2 metadata bridge: it serializes the definitions of OLAP dimensions, cubes, and the surrounding OLAP catalog into portable metadata form so that they can be inspected, migrated, or reconstructed by other tools.

Because the body is wrapped (the source text in the data dictionary is obfuscated), the internal implementation cannot be read directly. The documented API classification is OTHER, meaning it is not a public EBS application API and carries no support commitment for direct customer calls. Within EBS the package is primarily relevant to administrators and developers investigating OLAP metadata objects, upgrade utilities, or the interaction between the OLAP option and the EBS database tier.

Key Procedures and Functions

Three procedures are documented for this package body. Parameter lists are not published and are deliberately omitted here.

  • EXPORT_DIMENSION — Exports the metadata definition of an OLAP dimension. This is the granular workhorse of the package: it reads the dimensional definition, including its levels and hierarchies, and renders it into the export stream or repository that the caller expects.
  • EXPORT_CUBE — Exports the metadata definition of an OLAP cube, including its measure and dimension associations. It complements EXPORT_DIMENSION by handling the fact-oriented side of the analytic workspace.
  • EXPORT_OLAP_CATALOG — Exports the catalog-level metadata, in effect orchestrating the dimension and cube exports into a single coherent OLAP catalog representation.

All three are export-oriented; there are no documented import-side counterparts in this package body.

Tables Accessed

The ETRM metadata lists three referenced objects, reached through APPS synonyms.

  • DBA_USERS — Read to resolve and validate schema ownership of the OLAP objects being exported, for example to confirm that the OLAP catalog objects belong to the expected owner before serialization.
  • PLITBLM — The standard PL/SQL interim table used in EBS for parsing and resolving PL/SQL source; its presence suggests the package's wrapped compilation path or invocation of dynamic SQL during export.
  • UTL_FILE — Used to write the exported metadata output to a server-side file, consistent with the export purpose of all three procedures.

No persistent OLAP metadata tables are named in the excerpt, so any further object access is not documented at this level.

Usage Notes

CWM2_OLAP_EXPORT is not invoked from any standard EBS form in normal business flows, and the metadata records zero downstream package references. In practice it is encountered in three situations. First, during OLAP administration or metadata migration, where a DBA or developer calls the export procedures to capture dimension and cube definitions to a file via UTL_FILE. Second, during diagnostics when an OLAP catalog appears inconsistent and the exported definition must be compared against the live catalog. Third, in upgrade and patching investigations, where the wrapped package appears in the OLAPSYS schema listing.

Because the package is wrapped and classified OTHER, direct invocation should be treated as unsupported and attempted only in a non-production environment with the necessary directory object and file system privileges granted to the calling schema. The record for "!ock" in the searched documentation resolves to this OLAP export package body; no other EBS object matches that string.