Search Results load_valueset

Overview

AD_AW_LOADER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under ETRM as an OTHER API. Its purpose is to load, populate, and maintain Oracle Analytical Workspace (AW) and OLAP model artifacts directly from PL/SQL. The package acts as a server-side loader that abstracts the underlying DBMS_AW and DBMS_LOB functionality, allowing EBS components to define dimensions, valuesets, formulas, models, properties, and programs programmatically rather than through manual AW DDL scripts. It is particularly relevant to the Oracle Demand Planning and Advanced Planning family of products in Release 12.1.1 and 12.2.2, where analytical workspaces underpin forecasting and planning calculations.

The package is declared AUTHID CURRENT_USER, so execution privileges and name resolution follow the calling schema context. The header revision ($Header: adawld9is.pls 120.0) confirms this is a long-standing internal EBS utility that has remained stable across the 12.x line. The user search term "update_aw" maps directly to the public procedure UPDATE_AW, the package's primary entry point for refreshing a live analytical workspace after its constituent objects have been loaded.

Key Procedures and Functions

• ATTACH_AW — Attaches the session to a specified analytical workspace for a given schema, establishing the AW context required before subsequent load operations.
• CREATE_OBJECT — Creates an AW object by name, type, attributes, and load descriptorth; supports definition of dimensions, models, and related OLAP structures.
• DELETE_OBJECT — Removes a named AW object from the workspace.
• LOAD_DIMENSION_INT — Loads a dimension whose members are represented as integer values.
• LOAD_DIMENSION_VALUES — Populates a dimension with values supplied through the DIM_VALUES collection type.
• LOAD_FORMULA — Loads a formula expression into the current analytical workspace.
• LOAD_MODEL — Loads an OLAP model definition.
• LOAD_PROGRAM — Loads an AW program, using a CLOB parameter to accommodate large program bodies.
• LOAD_PROPERTIES — Loads object properties via the PROP_VALUES associative array indexed by VARCHAR2.
• LOAD_VALUESET — Loads a valueset for a dimension, again using the DIM_VALUES collection type.
• UPDATE_AW — Commits or refreshes the analytical workspace after load operations; this is the procedure users most commonly reference when searching for "update_aw".

The package also defines two public collection types: DIM_VALUES (a table of VARCHAR2(32) indexed by BINARY_INTEGER) and PROP_VALUES (a table of VARCHAR2(32) indexed by VARCHAR2(32)). These types shape the bulk-loading interfaces.

Tables Accessed

ETRM metadata documents that AD_AW_LOADER references only the following objects through APPS synonyms: DBMS_AW, DBMS_LOB, and PLITBLM. DBMS_AW is the Oracle-supplied PL/SQL API for analytical workspace management; AD_AW_LOADER calls it to create, populate, and update AW objects. DBMS_LOB is used to handle large objects, notably for the CLOB-based LOAD_PROGRAM interface. PLITBLM is the internal PL/SQL integer table type utility used to manage index-by table structures underlying the DIM_VALUES and PROP_VALUES collections. No EBS application base tables are directly referenced; all persistence is delegated to the OLAP infrastructure managed by DBMS_AW.

Usage Notes

ETRM records that AD_AW_LOADER is not referenced by any other documented package (referenced by 0 other packages), indicating it is invoked at the top of a call chain rather than as a shared utility. Typical invocation paths include concurrent programs and internal EBS setup or upgrade routines that build or refresh analytical workspaces for planning products. Because the package is AUTHID CURRENT_USER, callers execute with their own privileges, and schemas must hold appropriate grants on DBMS_AW and DBMS_LOB.

The standard call sequence is ATTACH_AW followed by one or more LOAD_* or CREATE_OBJECT operations and then UPDATE_AW to persist the workspace. Custom code should never bypass UPDATE_AW when changes must be committed, and consumers should treat this package as an internal, undocumented-for-customers interface subject to change between point releases. Assistance from Oracle Support is advisable before extending or wrapping these procedures in custom EBS components.