Search Results remove_custom_view_items

Overview

APPS.BSC_CUSTOM_VIEW_UI_WRAPPER is a valid PL/SQL package in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments that belongs to the Balanced Scorecard (BSC) module. It functions as a user-interface wrapper layer that abstracts the manipulation of custom view, tab view, and scorecard canvas components for the Balanced Scorecard HTML-based user interface. The package is owned by the APPS schema and is classified as a non-public (OTHER) API, indicating that it is intended primarily for internal consumption by other BSC packages rather than as a formally published integration interface.

The package bridges the presentation layer and the underlying data model by providing packaged procedures that add, update, and remove UI elements such as KPIs, labels, hotspots, links, launch pads, measures, tab views, and background images. It also exposes utility routines for managing the custom view canvas lifecycle and for retrieving identifiers and search strings. Because custom views in Balanced Scorecard correspond to configurable, user-defined scorecard layouts, this wrapper is central to rendering and persisting those layouts.

Key Procedures and Functions

The ETRM metadata documents 28 procedures and functions. The primary groups are as follows.

• Canvas and cleanup routines: COMPACT_CUSTOM_VIEW_LABELS, CLEAR_CUSTOM_VIEW_CANVAS, and REMOVE_CUSTOM_VIEW_ITEMS manage the removal and tidying of rendered elements from the custom view canvas.
• KPI and measure maintenance: ADD_OR_UPDATE_KPI, ADD_OR_UPDATE_KPI_LABEL, and ADD_OR_UPDATE_MEASURE create or update KPI indicators and their associated measures within a custom view.
• Label and hotspot maintenance: ADD_OR_UPDATE_LABEL and ADD_OR_UPDATE_HOTSPOT manage textual labels and interactive hotspot regions.
• Navigation and launch elements: ADD_OR_UPDATE_CUSTOM_VIEW_LINK and ADD_OR_UPDATE_LAUNCH_PAD manage hyperlinks and launch pad entries embedded in the view.
• Tab view management: ADD_OR_UPDATE_TAB_VIEW, ADD_OR_UPDATE_TAB_VIEW_KPI, ADD_OR_UPDATE_TAB_VIEW_BG, ADD_OR_UPDATE_TAB_VIEW_LABEL, IS_TAB_VIEW_EXIST, and COMPARE_TAB_VIEW_TIMESTAMP handle the creation, existence checking, timestamp comparison, and element population of tab views.
• Function and identifier utilities: ADD_OR_UPDATE_FUNCTION, DELETE_FUNCTION, GET_PARAM_SEARCH_STRING, and NEXT_CUSTOM_VIEW_ID manage form function associations and identifier generation.

No parameter lists are invented here; the procedures are described strictly by documented name and purpose.

Tables Accessed

The package reads and writes Balanced Scorecard configuration and presentation tables through APPS synonyms. Key referenced tables include BSC_TABS_B and BSC_TABS_TL, BSC_TAB_VIEWS_B, BSC_TAB_VIEW_KPI_TL, BSC_TAB_VIEW_LABELS_B and BSC_TAB_VIEW_LABELS_TL, and BSC_SYS_DATASETS_B. Image resources are managed via BSC_SYS_IMAGES, BSC_SYS_IMAGES_MAP_TL, and the BSC_SYS_IMAGE_ID_S sequence. Indicator metadata is held in BIS_INDICATORS and BIS_INDICATORS_VL, while form function integration uses FND_FORM_FUNCTIONS, FND_FORM_FUNCTIONS_S, and BIS_FORM_FUNCTION_EXTENSION. Region definitions are drawn from AK_REGIONS and AK_REGION_ITEMS_VL. These accesses explain why the package must coordinate with the underlying BSC data model and with form function registration.

Usage Notes

BSC_CUSTOM_VIEW_UI_WRAPPER is referenced by six other packages, including BSC_CUSTOM_VIEW_PVT, BSC_PORTLET_UI_WRAPPER, BSC_SCORECARD_PVT, BSC_SIMULATION_VIEW_PUB, BSC_SIMULATION_VIEW_PVT, and BSC_UPGRADES_GENERIC. It is therefore invoked indirectly whenever custom views are rendered or modified in the Balanced Scorecard UI, when simulations or portlets construct scorecard views, and during upgrades that migrate custom view definitions. It is not typically called directly from forms or concurrent programs; instead, it is consumed by the higher-level BSC private and public APIs that drive the Balanced Scorecard web interface. Customizations that need to manipulate custom view contents should prefer those documented higher-level APIs, treating this wrapper as an internal implementation layer.