Search Results get_default_dim_object_value

Overview

BIS_UTIL is a shared utility package in the APPS schema that provides low-level helper routines for the Oracle E-Business Suite Business Intelligence System (BIS) and Balanced Scorecard (BSC) product family. It is classified as a UTIL API, meaning it exposes no business-level transaction endpoints; instead, it centralizes common operations such as short-name validation, date-stamp verification for optimistic locking, display formatting of exception precision values, and navigation URL construction for report and form launches. The package is documented as VALID on both Oracle EBS 12.1.1 and 12.2.2 and contains 42 procedures and functions. Its role is infrastructural: it is referenced by 16 other packages, including BIS_DIMENSION_PUB, BIS_FUNCTIONAL_AREA_PUB, BIS_POSTACTUAL, BSC_UTILITY, GL_BIS_ALERTS_PKG, and HR_BIS_ALERTS, all of which depend on BIS_UTIL for validation and formatting consistency across the BI Foundation schema.

Key Procedures and Functions

The documented routines fall into several functional groups:

• Validation and concurrency: VALIDATE_FOR_UPDATE and GET_UPDATE_DATE_FOR_OWNER support optimistic-locking checks against a caller-supplied update date; VALIDATE_SHORT_NAME enforces naming rules for short-name columns used across BIS entities.
• Workflow integration: START_WORKFLOW, STRT_WF_PROCESS, and START_WORKFLOW_ENGINE initiate Oracle Workflow processes and workflow engine calls from BIS context, typically for exception alerts and corrective-action flows.
• Formatting and numeric utilities: GET_TIME_LEVEL_VALUE resolves a value at a given time level; GET_EPS and EPS_PRECISION_FORMAT_MASK retrieve exception-precision settings and the corresponding Oracle format mask used to render them.
• Navigation and URL construction: BUILD_REPORT_URL assembles a runnable report URL; SHOW_APPLICATION resolves application display information; GET_DEFAULT_APPLICATION_ID returns the default application identifier.
• Metadata lookups: GET_OBJECT_TYPE, GET_APPS_ID_BY_SHORT_NAME, GET_DIM_OBJECTS_BY_DIM, and GET_DEFAULT_DIM_OBJECT_VALUE resolve object types, application IDs, and dimension-object mappings from the BI metadata model.
• Region and portlet helpers: GET_PAGES_USING_PARAMPORTLET identifies pages that consume a parameter portlet; SAVE_PROTOTYPE_VALUES persists prototype configuration values.
• Environment checks: IS_DEV_ENV_SET and IS_INTERNAL_CUSTOMER gate behavior based on deployment environment and customer classification.

Tables Accessed

BIS_UTIL reads and writes through APPS synonyms. AK_REGIONS and AK_REGION_ITEMS (with AK_REGION_ITEMS_VL) are queried to resolve region and portlet metadata referenced by the page and portlet helpers. FND_FORM_FUNCTIONS and FND_FORM_FUNCTIONS_VL provide the function registry used for form-function lookups and URL construction. FND_APPLICATION and FND_MENU_ENTRIES supply application and menu metadata for navigation and default-application resolution. BIS_DIMENSIONS and BIS_DIMENSIONS_TL back the dimension lookup routines, while BIS_INDICATORS, BIS_LEVELS, BIS_LEVELS_TL, and BIS_TARGET_LEVELS provide indicator and level metadata for time-level and default-object-value resolution. Exception workflow state is stored in BIS_EXCPT_WF_S, and scorecard structures BSC_KPIS_B, BSC_SYS_DIM_LEVELS_B, and BSC_SYS_DIM_LEVELS_BY_GROUP are consulted for KPI and system dimension-level integration.

Usage Notes

BIS_UTIL is not intended for direct invocation by end users or concurrent programs. It is called programmatically by BIS and BSC public packages, by alert packages (GL_BIS_ALERTS_PKG, HR_BIS_ALERTS, BIX_ALERT), and by upgrade utilities such as BSC_UPGRADES. The package also references itself (BIS_UTIL - show dependent code), indicating internal reuse of its own helpers. Customer and partner extensions to the BI Foundation schema should reference BIS_UTIL rather than reimplement short-name validation, URL construction, or update-date checks, to remain consistent with Oracle's internal conventions. Because the package is heavily reused, any modification requires a full dependency recompilation of the 16 dependent packages; Oracle therefore ships it as a sealed internal API and it should not be altered in a production environment.