Results for “bisfv_ind_customizations_v”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BISFV_IND_CUSTOMIZATIONS_V is a seeded Oracle E-Business Suite view owned by the APPS schema, delivered as part of the BIS (Applications BIS / Balanced Scorecard and Indicator) product family. Its purpose is to expose indicator definitions that have been translated and optionally customized, presenting a single denormalized row per indicator for a given runtime language. The view is marked VALID in both Oracle EBS 12.1.1 and 12.2.2 and is treated as a reporting and integration surface rather than a transactional object.
The view draws its meaning from the intersection of two concerns: language-specific descriptive text (the NAME and DESCRIPTION attributes identified by the "ind_tl" search term, indicating the BIS_INDICATORS_TL translation table) and customer-level customization of indicator enablement. By combining these, the view answers the operational question of "which indicators are available, in my language, and what is their customized activation state." It is most commonly consumed by Oracle Discoverer workbooks, BI Publisher reports, and custom PL/SQL routines that render scorecard content.
Underlying Base Objects
The documented view text confirms the view is defined over two base tables in the APPS schema:
- BIS_INDICATORS (alias IND) — the primary indicator definition table holding indicator identity, ownership, audit columns, dataset linkage, and the base ENABLED and OBSOLETE flags.
- BIS_INDICATORS_TL (alias IND_TL) — the translation table supplying language-dependent NAME and DESCRIPTION values, joined on INDICATOR_ID.
The join predicates restrict output to the session language via IND_TL.LANGUAGE = USERENV('LANG') and exclude obsolete indicators through NVL(IND.OBSOLETE, 'F') = 'F'. No additional documented referenced base objects exist beyond these two tables, although the view text invokes the database function BIS_MEASURE_PUB.GET_CUSTOMIZED_ENABLED, a dependency that should be considered when troubleshooting performance or execution errors.
Key Columns
- INDICATOR_ID — unique surrogate key for the indicator; the join column linking base and translation records.
- SHORT_NAME — the language-independent identifier used in programmatic references and cross-references.
- NAME and DESCRIPTION — translated display text sourced from BIS_INDICATORS_TL for the current session language.
- ENABLED — derived value evaluated as
NVL(BIS_MEASURE_PUB.GET_CUSTOMIZED_ENABLED(INDICATOR_ID), IND.ENABLED), giving precedence to any customer customization over the seeded default. - DATASET_ID — identifies the dataset supplying the indicator's underlying measures.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from BIS_INDICATORS.
Common Use Cases and Queries
Typical usage includes validating customized indicator availability, driving scorecard UI lists, and reconciliation after data migration. A basic listing of active indicators in the session language:
SELECT indicator_id, short_name, name FROM bis fv_ind_customizations_v WHERE enabled = 'Y';- Filtering by dataset:
SELECT name, dataset_id FROM bis fv_ind_customizations_v WHERE dataset_id = :p_dataset; - Audit extraction:
SELECT short_name, last_update_date, last_updated_by FROM bis fv_ind_customizations_v ORDER BY last_update_date DESC;
Because NAME and DESCRIPTION derive from the translation table, queries returning blank descriptive text generally indicate a missing BIS_INDICATORS_TL row for the caller's LANGUAGE value rather than a view defect.
-
APPS.BISFV_IND_CUSTOMIZATIONS_V·↳ BIS_INDICATORS·↳ BIS_INDICATORS_TL·↳ BIS_MEASURE_PUB·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
SYNONYM: APPS.BIS_INDICATORS 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
eTRM - BIS Tables and Views 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - BIS Tables and Views 12.1.1