Search Results bsc_custom_view_pvt




Overview
Explore in AI Chat

Overview

APPS.BSC_CUSTOM_VIEW_PUB is a public PL/SQL package belonging to the Oracle Balanced Scorecard (BSC) module of Oracle E-Business Suite. It exposes the application programming interface used to manage custom tab views — the personalized dashboard layouts that individual users or administrators define within a Balanced Scorecard tab. The package header (BSCCVDBS.pls, version 120.0) declares a set of strongly typed record and table structures, including Bsc_Cust_View_Rec_Type, Bsc_Cust_View_Tbl_Type, and Bsc_Tab_Rec_Type, which mirror the columns of the underlying BSC tables. These types allow bulk operations across multiple custom views in a single call. Because the package is classified as a PUB (public) API, it is the sanctioned integration point for creating, assigning, unassigning, and deleting custom views, insulating callers from direct DML against the base tables. The package is referenced by four other packages in the EBS instance, confirming its role as a foundational utility within the Balanced Scorecard subsystem. The naming convention reflects a common EBS pattern: the private body is documented as BSCCVDBS.pls, while the deployed public synonym is BSC_CUSTOM_VIEW_PUB.

Key Procedures and Functions

The ETRM metadata documents five procedures, all of which share responsibility for the custom-view lifecycle:

  • ASSIGN_CUST_VIEWS — Assigns one or more custom views to a target user or tab configuration. This is the procedure most closely associated with the user search term "assign_cust_views" and is the primary entry point for granting view visibility.
  • ASSIGN_UNASSIGN_VIEWS — A combined operation that reconciles a desired set of assigned views against the current state, performing both assignments and unassignments in a single transaction. This is typically used when synchronizing a complete view list rather than making incremental changes.
  • UNASSIGN_CUST_VIEWS — Removes the association between custom views and their current owner or tab, without deleting the underlying view definition.
  • DELETE_CUSTOM_VIEW — Removes a custom view definition itself. This is a destructive operation distinct from unassignment.
  • DELETE_CUSTOM_VIEW_LINKS — Deletes the link records that connect custom views to their associated tabs or owners, cleaning up referential relationships as part of the deletion workflow.

Parameter lists are not reproduced here; callers should consult the package specification in the database for exact signatures.

Tables Accessed

The package operates against four documented tables, accessed through APPS synonyms:

  • BSC_TAB_VIEWS_B — The base table storing custom view definitions (tab_id, tab_view_id, enabled_flag, audit columns).
  • BSC_TAB_VIEWS_TL — The translation table providing the user-facing name and help text for each view.
  • BSC_TABS_B — The parent tab definitions, supplying kpi_model, bsc_model, cross_model, default_model, zoom_factor, parent_tab_id, and owner_id context for each view.
  • BSC_SYS_IMAGES — Supplies the image_id used when rendering the visual icon associated with a custom view.

Reads dominate the assignment and unassignment paths, while the delete procedures perform the corresponding writes and cleanup across these tables.

Usage Notes

BSC_CUSTOM_VIEW_PUB is normally invoked indirectly through the Balanced Scorecard administrative forms and concurrent programs rather than called directly by end users. Custom integrations, data migration scripts, and personalization extensions call it when they need to programmatically replicate view assignments between environments or users. Because the package manipulates audit columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) and translation rows, callers should ensure the correct application context (FND_GLOBAL.APPS_INITIALIZE) is established before invocation. Deletion procedures should be invoked in the documented order — removing links before the view itself — to avoid orphaned records. As a public API, it is supported across Oracle EBS 12.1.1 and 12.2.2, and is the recommended alternative to direct DML on the BSC_TAB_VIEWS tables.