Search Results dim_obj_table_name

Overview

APPS.BSC_BIS_DIM_OBJS_VL is a multilingual (MLS-enabled) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its FND design data identifier is BIS.BSC_BIS_DIM_OBJS_VL, confirming its origin within the Oracle Balanced Scorecard (BSC) and Business Intelligence System (BIS) product family. The view exposes the BIS/BSC dimension object registry used by the Performance Management Data (PMD) layer — the metadata backbone that defines the analytical dimensions, level hierarchies, key sizing, and drill behavior leveraged by Oracle Daily Business Intelligence and Balanced Scorecard reporting.

Because it is declared as a "MultiLingual view (a language resolved view of the data)," the _VL suffix indicates that the underlying _B (base) and _TL (translation) tables have already been joined and filtered by the session's language, returning one row per dimension object in the user's NLS_LANGUAGE. The view is registered as VALID, which matters when diagnosing broken dependency chains in the BIS schema after patching or cloning.

Underlying Base Objects

The ETRM metadata for this view does not enumerate explicit referenced base objects. By convention for this object class, BSC_BIS_DIM_OBJS_VL resolves from the BSC_BIS_DIM_OBJS_B and BSC_BIS_DIM_OBJS_TL tables, joined on the primary key BIS_DIM_OBJ_ID, with the translation table restricted by LANGUAGE. Administrative and design-time tools, including the Dimensional Model editor and the BIS BIS metadata generators, read this view rather than the base tables directly.

Key Columns

• SHORT_NAME (VARCHAR2 30) — unique short identifier for the dimension object.
• BIS_DIM_OBJ_ID / BSC_DIM_OBJ_ID — internal identifiers linking the BIS registry to the BSC registry.
• APPLICATION_ID — owning application, used to partition dimension objects by product.
• DIM_OBJ_VIEW_NAME, DIM_OBJ_TABLE_NAME, DIM_OBJ_PK_COL, WHERE_CLAUSE — the physical view/table, primary key column, and filter predicate used to materialize the dimension.
• NAME, DESCRIPTION, ABBREVIATION — presentation attributes resolved from the translation table.
• USER_KEY_SIZE and DISP_KEY_SIZE — the sizes of the user (surrogate) key and the display key respectively. DISP_KEY_SIZE is the attribute most frequently searched, as it governs the width required by the generated dimension key column in PMD summary tables and must be wide enough to hold concatenated display values.
• SOURCE_TYPE, DATA_SOURCE, TABLE_TYPE, EDW_FLAG — data-source classification and warehouse integration flags.
• MASTER_LEVEL, VALUE_ORDER_BY, COMP_ORDER_BY, CUSTOM_GROUP, COMPARISON_LABEL_CODE — hierarchy ordering and comparison configuration.
• LONG_LOV, DEFAULT_SEARCH, ENABLED, DRILL_TO_FORM_FUNCTION, HIDE_IN_DESIGN — UI/design-time behavior attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Administrators inspect this view to audit dimension key sizing before Performance Management patches, to reconcile BIS and BSC object registries, and to troubleshoot drill-to-form or LOV behavior. A typical search directly answers the query for disp_key_size:

SELECT short_name, name, user_key_size, disp_key_size, dim_obj_table_name
FROM   apps.bsc_bis_dim_objs_vl
WHERE  disp_key_size IS NOT NULL
ORDER  BY disp_key_size DESC;

To list enabled dimensions for a specific application:

SELECT d.short_name, d.name, d.dim_obj_view_name, d.application_id
FROM   apps.bsc_bis_dim_objs_vl d
WHERE  d.enabled = 'Y'
AND    d.application_id = :app_id;

To identify dimensions linked to the EDW:

SELECT short_name, edw_dim_id, edw_dim_dim_obj_id
FROM   apps.bsc_bis_dim_objs_vl
WHERE  edw_flag = 1;

Because the view is MLS-resolved, no LANGUAGE join is required; translated NAME and DESCRIPTION values are returned automatically for the session locale. Queries should always qualify the view with APPS. and be executed with the APPS schema or an equivalent read-privileged account.