Search Results get_column

Overview

APPS.BSC_IM_INT_MD is an internal metadata-management package belonging to the Oracle Balanced Scorecard (BSC) product family, specifically the Intelligence Module (IM) integration layer. Its core business function is to define, persist, and retrieve the structural metadata that describes the analytical objects used by the BSC/DBI/EDW stack — dimensions, levels, columns, hierarchies, level relations, mappings, and cubes. In effect, the package acts as the programmatic interface to the metadata repository: it declares the PL/SQL record and collection types that model every metadata entity (for example, IM_MD_DIMENSIONS_R, IM_MD_LEVELS_R, IM_MD_COLUMNS_R, IM_MD_LEVEL_RELATIONS_R, IM_MD_HIERARCHIES_R, and IM_MD_MAPPING_R) and exposes creation and retrieval routines that populate and query those structures. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than its owner — a deliberate choice that lets integration callers act against their own schema context. The $Header annotation (BSCIMDUS.pls 115.0, 2003) identifies it as a mature component carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes roughly 46 documented routines, organized symmetrically as create/get pairs. The CREATE_* group builds metadata definitions: CREATE_DIMENSION, CREATE_LEVEL, CREATE_COLUMN, CREATE_LEVEL_RELATION, CREATE_HIERARCHY, CREATE_MAPPING, CREATE_MAPPING_DETAIL, and CREATE_CUBE each instantiate one metadata entity. Supporting DDL-oriented helpers — CREATE_FK, CREATE_UK, and CREATE_OBJECT — generate the foreign key, unique key, and object definitions associated with the metadata model.

• CREATE_LEVEL_RELATION — the routine most directly relevant to the "create_level_relation" search. It defines the parent/child relationship between two levels in a hierarchy, populating the IM_MD_LEVEL_RELATIONS_R structure fields: child_level, parent_level, child_fk, parent_pk, hier_name, dim_name, apps_origin, and property. This is the mechanism by which the dimensional hierarchy's referential structure is declared.
• GET_* functions — GET_DIMENSION, GET_LEVEL, GET_DIM_FOR_LEVEL, GET_COLUMN, GET_LEVEL_RELATION, GET_HIERARCHY, GET_MAPPING, and GET_TIME — retrieve previously registered metadata, typically returning the matching collection type for downstream processing.
• Utility routines — GET_TIME (timestamp helper) and RESET_INT_METADATA (clears integration metadata state before a refresh or rebuild cycle).
• Global variables — g_debug, g_stmt, and g_status_message provide diagnostic tracing and statement/status capture across the package's lifecycle.

No parameter lists are documented in the ETRM excerpt, so invocation details should be confirmed against the package specification in the target EBS instance.

Tables Accessed

The documented table reference is PLITBLM, accessed via an APPS synonym. PLITBLM is the canonical EBS PL/SQL table used by the FND_* utility family for temporary storage, status tracking, and message assembly. In this package it supports the metadata build operations — buffering metadata payloads and status messages as records are created or fetched — rather than serving as the persistent metadata store itself. The metadata entities themselves are modeled by the package's record and collection types and persisted through the CREATE_* and GET_* routines, which likely write to BSC/DBI metadata tables whose names are not enumerated in the excerpt.

Usage Notes

BSC_IM_INT_MD is classified as OTHER (internal API), not as a public or business-facing interface, and is referenced by four other packages within the EBS code base. It is typically invoked indirectly: during BSC Intelligence Module setup, integration refresh, and dimensional/hierarchical metadata definition, most often driven by concurrent programs or internal bootstrap code rather than directly from a form. Developers performing custom extension work on BSC or DBI metadata should treat the CREATE_* routines as the supported entry points for registering dimensions, levels, columns, hierarchies, and level relations, and should call RESET_INT_METADATA before rebuilding metadata in a refresh scenario. Because the package is AUTHID CURRENT_USER, custom callers must possess the necessary object privileges on the underlying metadata tables in their own schema context.