Search Results is_more

Overview

APPS.BSC_CUSTOM_VIEW_PVT is a private PL/SQL package belonging to the Oracle Balanced Scorecard (BSC) application module within Oracle E-Business Suite. The package encapsulates the server-side implementation logic for managing custom dashboard views and tab layouts presented to end users of the Balanced Scorecard. Balanced Scorecard users configure their own tabs and associated KPI views, select default views per tab, and control which views are enabled, assigned, or unassigned. BSC_CUSTOM_VIEW_PVT supplies the internal machinery that supports these user-driven customizations, while the companion public package BSC_CUSTOM_VIEW_PUB exposes the documented API surface for callers.

The package naming convention follows the standard Oracle EBS PL/SQL layering model: the _PVT suffix indicates a private package that is not intended to be called directly by external integrations. It is referenced by one other package, which is consistent with its role as a subordinate implementation unit invoked by the public layer. The header carries a source header marker of BSCCVDVS.pls with a creation date of October 2001, placing the package within the original Balanced Scorecard development effort, and it has remained stable through the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

• IS_MORE — A function central to the package's view-paging logic. It processes a delimited list of custom views and returns the next custom view along with a Boolean indicator of whether additional views remain. This is the object most commonly searched for in relation to this package.
• GET_ENABLED_FLAG_FOR_VIEW — Returns the enabled status of a given tab and tab view combination, allowing the UI to suppress disabled views.
• GET_TAB_DEFAULT_VIEW — Retrieves the identifier of the default view associated with a specified tab.
• VALIDATE_TAB_VIEW — Confirms that a supplied tab and view pairing is valid before persistence or rendering.
• RETRIEVE_TAB — Populates a tab record structure from the underlying tables.
• RETRIEVE_TAB_VIEW — Populates a custom view record structure, mirroring the tab retrieval pattern.
• UPDATE_TAB_VIEW — Persists changes to an existing tab view definition.
• UPDATE_TAB_DEFAULT_VIEW — Sets or changes the default view designation for a tab.
• DELETE_CUSTOM_VIEW — Removes a custom view owned by a user.
• ASSIGN_UNASSIGN_VIEWS — A combined routine handling both assignment and removal of views from a user's layout.
• ASSIGN_CUST_VIEWS / UNASSIGN_CUST_VIEWS — Discrete routines that assign views to, or remove views from, a user's custom set.
• CREATE_TAB_VIEW — Creates a new tab view record.
• DELETE_CUSTOM_VIEW_LINKS — Cleans up dependent link records when a custom view is deleted.

Tables Accessed

The package operates against the core Balanced Scorecard configuration tables, accessed through APPS synonyms. BSC_TABS_B holds tab definitions; BSC_TAB_VIEWS_B and BSC_TAB_VIEWS_TL store tab view definitions and their translated names. BSC_TAB_VIEW_LABELS_B and BSC_TAB_VIEW_LABELS_TL hold label text for views, while BSC_TAB_VIEW_KPI_TL stores translated KPI labels associated with views. BSC_SYS_IMAGES and BSC_SYS_IMAGES_MAP_TL provide the system images and language mappings used to render view icons. FND_LANGUAGES is referenced to resolve the session language during multilingual retrieval and update operations.

Usage Notes

Because this is a private package, it is invoked indirectly through BSC_CUSTOM_VIEW_PUB rather than called by external code. In practice it is exercised from the Balanced Scorecard self-service forms and dashboard pages when a user creates, edits, reorders, or deletes custom views, and when the application resolves which views to render for a tab. The IS_MORE function in particular supports incremental rendering of a user's view list. Oracle recommends that customizations and integrations target the public package; direct calls to BSC_CUSTOM_VIEW_PVT are unsupported and may be affected by internal changes across releases.