Search Results is_child_tab_of

Overview

APPS.BSC_SCORECARD_PUB is the public PL/SQL API for the Oracle Balanced Scorecard (BSC) module in Oracle E-Business Suite 12.1.1 and 12.2.2. The package exposes the maintained, published entry points that external components — Oracle Forms, concurrent programs, and custom extensions — must call when creating, modifying, or removing scorecard tabs (the configurable scorecard "pages" that group KPIs and related scorecard content). It is classified as a PUB API and is backed by the private implementation package BSC_SCORECARD_PVT; the PUB layer performs public validation, message handling, and grant/access orchestration while the PVT layer holds the core logic. The object is VALID in the APPS schema and is not referenced by any other database object, but it itself references seven or more dependent packages and a set of BSC and FND (Application Object Library) tables.

Key Procedures and Functions

The documented API surface contains sixteen procedures and functions:

• INITIALIZE_TAB_ENTITY_REC — initializes the tab entity record used by subsequent create/update calls.
• CREATE_TAB — creates a new scorecard tab definition, including its base and translated records.
• RETRIEVE_TAB — returns the attribute values of an existing tab.
• UPDATE_TAB — modifies an existing tab definition.
• DELETE_TAB — removes a tab definition.
• CREATE_TAB_ACCESS — establishes user-level access to a tab.
• CREATE_TAB_GRANTS — creates the function/menu grants that make a tab accessible through the responsibility and menu structure.
• UPDATE_TAB_TIME_STAMP — refreshes the timestamp of a tab record.
• UPDATE_SYSTEM_TIME_STAMP — refreshes the system-level timestamp associated with scorecard tab processing.
• IS_CHILD_TAB_OF — determines whether a tab has a parent/child relationship to another tab.
• CHECK_TAB_USERACCESS — validates whether a user has access to a tab, including function-level checks.
• CHECK_TAB_USERACCESS_FUNC_ONLY — performs the function-grant-only portion of the access check.
• VALIDATE_SCORECARD_REVOKE — validates a request to revoke scorecard access.
• VALIDATE_SCORECARD_ACCESS — validates a request to grant or check scorecard access.
• IS_TAB_ORDERING_ENABLED — indicates whether tab ordering is enabled for the current context.

Parameter lists are not reproduced here; only the documented purposes are stated.

Tables Accessed

The package reads and writes the following tables, accessed through APPS synonyms:

• BSC_TABS_B — base table holding tab definitions.
• BSC_TABS_TL and BSC_TABS_VL — translated and view layers for tab text.
• BSC_USER_TAB_ACCESS — per-user tab access assignments.
• FND_FORM_FUNCTIONS — function definitions used when creating tab grants.
• FND_GRANTS — grants linking tabs to menus/responsibilities.
• FND_MENUS and FND_MENU_ENTRIES — menu structure used to expose tabs.
• FND_OBJECTS — object registration supporting grants.
• FND_RESPONSIBILITY — responsibility context for access validation.

Usage Notes

BSC_SCORECARD_PUB is invoked from the Balanced Scorecard setup and administration forms, from concurrent programs that provision or maintain scorecard tabs and grants, and from custom code that must manage scorecard configuration. Callers should use the PUB entry points rather than the underlying BSC_SCORECARD_PVT procedures, since PUB enforces validation rules, raises messages through FND_MSG_PUB and FND_MESSAGE, and derives session context from FND_GLOBAL. Access checks rely on FND_GRANTS, FND_MENUS and FND_RESPONSIBILITY, so grants must exist before CHECK_TAB_USERACCESS returns a positive result. Because the package is not referenced by any database object, it is safe to treat as a standalone public API boundary within the BSC module.