Search Results bsc_im_int_md
Overview
The APPS.BSC_IM_INT_MD package body is an Oracle EBS component that belongs to the Balanced Scorecard (BSC) intelligence module metadata layer. Its core business function is to build and manage an in-memory metadata repository that describes the dimensional model used by the BSC intelligence engine — dimensions, levels, hierarchies, mappings, columns, cubes, and the relationships between them. Rather than persisting this metadata directly to base tables at definition time, the package assembles a PL/SQL collection of records (im_md_dimensions_t, im_md_levels_t and analogous typed collections) that is subsequently consumed by downstream processing and packaging logic. The API is designed around a create/get pattern: CREATE_* procedures and functions register new metadata objects, while GET_* functions retrieve them from the in-memory structures. Metadata is classified as an OTHER API in ETRM 12.1.1, and the package is documented as being referenced by four other packages, confirming its role as a foundational rather than terminal component in the BSC dependency chain.
Key Procedures and Functions
The package exposes 46 documented procedures and functions. The create-side API registers the dimensional constructs:
- CREATE_DIMENSION — registers a dimension by name and application origin, together with its description and property values. It performs a duplicate check on the composite (dimension name, application origin) key before extending the in-memory collection.
- CREATE_LEVEL — registers a level within a dimension, capturing the level name, owning application origin, parent dimension, number of children, description, and property.
- CREATE_COLUMN — defines a column belonging to a level or dimension.
- CREATE_LEVEL_RELATION — establishes parent/child relationships between levels.
- CREATE_HIERARCHY — registers a hierarchy definition over the level structure.
- CREATE_MAPPING and CREATE_MAPPING_DETAIL — define mappings and their constituent detail rows, used to translate source data into the dimensional model.
- CREATE_CUBE — registers a cube construct for analytical aggregation.
- CREATE_FK, CREATE_UK, and CREATE_OBJECT — register foreign key, unique key, and generic object metadata respectively.
- RESET_INT_METADATA — clears the in-memory metadata collections, allowing a fresh definition cycle.
The retrieval API mirrors the create-side functions: GET_DIMENSION, GET_LEVEL, GET_DIM_FOR_LEVEL, GET_COLUMN, GET_LEVEL_RELATION, GET_HIERARCHY, and GET_MAPPING return the stored metadata for consumers. GET_TIME provides a timing value used for load and processing diagnostics.
Tables Accessed
According to the documented metadata, the package references one table via an APPS synonym: PLITBLM. This table is used in support of the metadata assembly and retrieval operations, most plausibly for logging or staging of the in-memory structures during the create/get lifecycle. The primary metadata itself is held in PL/SQL collection types rather than being written to dedicated persistent tables within this package body.
Usage Notes
BSC_IM_INT_MD is typically invoked from other BSC packages (four documented callers), from concurrent programs that build the intelligence metadata model, and from custom code that must register or interrogate dimensional definitions before a load or aggregation run. Because the metadata is held in package-level state, callers should sequence operations so that RESET_INT_METADATA precedes a new definition cycle when reusing the session. Error handling within create routines sets a status message and calls the logging helper write_to_log_file_n, so callers should inspect return values rather than relying solely on exceptions.
-
PACKAGE BODY: APPS.BSC_IM_INT_MD
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:BSC_IM_INT_MD, status:VALID,
-
PACKAGE: APPS.BSC_IM_INT_MD
12.1.1
owner:APPS, object_type:PACKAGE, object_name:BSC_IM_INT_MD, status:VALID,
-
PACKAGE: APPS.BSC_IM_UTILS
12.1.1
owner:APPS, object_type:PACKAGE, object_name:BSC_IM_UTILS, status:VALID,
-
PACKAGE BODY: APPS.BSC_OLAP_MAIN
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:BSC_OLAP_MAIN, status:VALID,
-
PACKAGE BODY: APPS.BSC_BSC_ADAPTER
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:BSC_BSC_ADAPTER, status:VALID,
-
PACKAGE BODY: APPS.BSC_MV_ADAPTER
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:BSC_MV_ADAPTER, status:VALID,
-
PACKAGE BODY: APPS.BSC_IM_UTILS
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:BSC_IM_UTILS, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: APPS.BSC_IM_INT_MD
12.1.1
-
APPS.BSC_BSC_ADAPTER dependencies on BSC_IM_INT_MD
12.1.1
-
APPS.BSC_MV_ADAPTER dependencies on BSC_IM_INT_MD
12.1.1
-
APPS.BSC_OLAP_MAIN dependencies on BSC_IM_INT_MD
12.1.1
-
APPS.BSC_IM_INT_MD dependencies on BSC_IM_INT_MD
12.1.1
-
APPS.BSC_IM_UTILS dependencies on BSC_IM_INT_MD
12.1.1
-
PACKAGE BODY: APPS.BSC_IM_INT_MD
12.1.1
-
SYNONYM: PUBLIC.PLITBLM
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:PLITBLM, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,