Search Results function_area_short_name

Overview

APPS.BIS_DISPLAY_MEASURES_V is a dictionary-style reporting view in the Oracle E-Business Suite Business Intelligence System (BIS) schema, which underpins the Daily Business Intelligence (DBI) and E-Business Intelligence (EBI) product family. The view presents the catalog of measures defined in the EBS intelligence layer, exposing each measure's short name, display name, description, functional area assignment, application ownership, enabled and obsolete flags, and — most importantly for the search context — the ACTUAL_DATA_SOURCE column that maps a measure to its underlying data origin.

The object is documented with the notation "Oracle Internal Use Only," meaning Oracle Corporation does not support direct customer access to the data except through standard Oracle Applications programs. It is therefore best understood as a metadata backbone consumed by Oracle-provided views, public APIs, and BI Administration user interfaces rather than a supported end-user query target. In 12.1.1 and 12.2.2 the object remains VALID and is registered under FND Design Data as BIS.BIS_DISPLAY_MEASURES_V, confirming it is delivered as part of the standard APPLSYS/APPS installation.

Underlying Base Objects

The view is defined over the following objects in the APPS schema:

• BIS_APPLICATION_MEASURES — the association of measures to the applications that own or publish them.
• BIS_FUNCTIONAL_AREAS and BIS_FUNCTIONAL_AREAS_VL — the functional area definitions and their translated (VL) name columns.
• BIS_INDICATORS and BIS_INDICATORS_TL — indicator metadata and translated indicator text.
• BIS_MEASURES_EXTENSION_VL — the multi-language view that contributes the extended measure attributes, including the actual data source reference.
• BSC_SYS_DATASETS_VL — the Balanced Scorecard system dataset definitions used to resolve measure-to-dataset linkage.

The join across these objects assembles a denormalized, translated presentation of each measure so that downstream consumers do not need to resolve the functional area, indicator, dataset, and extension relationships themselves. The view is in turn referenced by PL/SQL packages including BIS_WEIGHTED_MEASURE_PUB (used for weighted and composite measure calculation) and BSC_CUSTOM_VIEW_UI_WRAPPER (used by the Balanced Scorecard custom view user interface).

Key Columns

• SHORT_NAME (VARCHAR2 30) — the internal unique key for the measure, used in cross-references and API calls.
• NAME (VARCHAR2 255) — the translated measure name presented in BI dashboards and administration pages.
• DESCRIPTION (VARCHAR2 1024) — the translated explanatory text for the measure.
• ACTUAL_DATA_SOURCE (VARCHAR2 240) — the resolved data source identifier for the measure, indicating the schema object, dataset, or extract from which the measure's values are derived. This is the column most often sought when tracing a DBI/BI measure back to its physical source.
• FUNCTION_NAME (VARCHAR2 480) — the report or calculation function associated with the measure.
• FUNCTIONAL_AREA_ID, FUNCTION_AREA_NAME, FUNCTION_AREA_SHORT_NAME — the functional area (for example, Payables, Receivables, Order Management) to which the measure belongs.
• APPLICATION_ID — the owning Oracle application identifier.
• ENABLED, OBSOLETE — control flags indicating whether the measure is active or has been retired.
• ISSEED — indicates whether the row is a seeded (Oracle-delivered) measure or a customer-defined one.
• MEASURE_TYPE (VARCHAR2 30) — classifies the measure (for example, standard versus weighted).

Common Use Cases and Queries

The principal use case is discovery and lineage: identifying which measures exist for a functional area, whether they are enabled, and where their data actually originates. Because the object is Oracle-internal, production use should be read-only diagnostics rather than integration. A typical query is:

SELECT short_name, name, functional_area_short_name, actual_data_source, enabled, obsolete FROM apps.bis_display_measures_v WHERE enabled = 'Y' AND obsolete = 'N' ORDER BY functional_area_short_name, short_name;

To locate every measure resolving to a particular source, filter on ACTUAL_DATA_SOURCE, for example with a LIKE predicate against the dataset or schema name of interest. To isolate Oracle-seeded measures for a given application, constrain APPLICATION_ID and ISSEED. Finally, joining SHORT_NAME back to BIS_WEIGHTED_MEASURE_PUB or the BSC custom view wrapper explains how a measure participates in weighted composites and scorecard displays.