Search Results create_tab

Overview

APPS.BSC_SCORECARD_PUB is the public PL/SQL API for the Oracle Balanced Scorecard (BSC) module, a component of Oracle E-Business Suite in releases 12.1.1 and 12.2.2. The package exposes the programmatic interface through which scorecard "tabs" — the individual scorecard views or scorecards displayed within the Balanced Scorecard application — are created, retrieved, updated, deleted, and secured. A tab in this context represents a scorecard entity that may be nested hierarchically through a parent tab relationship and is associated with responsibilities, models, and user access grants.

The package is classified as a PUB (public) API, meaning it is intended for external invocation by forms, concurrent programs, and custom code rather than being internal-only. It operates on the underlying BSC tables and integrates with Oracle Application Object Library (FND) tables to manage functional grants, menu entries, and responsibility-based access. The header comment ($Header: BSCPTABS.pls 120.1) indicates the file's origin as the tab-focused portion of the BSC PL/SQL library.

Key Procedures and Functions

The package documents sixteen procedures and functions. The primary data-type support routine is Initialize_Tab_Entity_Rec, which initializes a Bsc_Tab_Entity_Rec record to its default state before use in create or update operations. The Create_Tab procedure is overloaded: one signature accepts only the entity record and returns status, while the second additionally returns the populated entity record with the generated tab identifier. Retrieve_Tab, Update_Tab, and Delete_Tab provide the standard CRUD lifecycle for tab entities.

Access-management procedures include Create_Tab_Access, which establishes or modifies user access to a tab; Create_Tab_Grants, which creates the FND functional grants required for the tab; and Check_Tab_UserAccess together with Check_Tab_UserAccess_Func_Only, which validate whether a user may view or operate on a tab, the latter checking function-level privileges alone. Validation routines Validate_Scorecard_Revoke and Validate_Scorecard_Access enforce rules before access is granted or revoked. Hierarchy and ordering are supported by Is_Child_Tab_Of, which tests parent-child relationships between tabs, and Is_Tab_Ordering_Enabled, which reports whether tab ordering is active. Timestamp maintenance is handled by Update_Tab_Time_Stamp and Update_System_Time_Stamp.

Tables Accessed

The package reads and writes BSC_TABS_B and BSC_TABS_TL, the base and translated tables that store tab definitions including names, help text, and language-specific attributes; the entity record flattens columns from both. BSC_USER_TAB_ACCESS stores per-user access records and is the target of the access and grant procedures. Integration with Oracle Application Object Library uses FND_FORM_FUNCTIONS, FND_GRANTS, FND_MENUS, FND_MENU_ENTRIES, FND_OBJECTS, and FND_RESPONSIBILITY to register function security and responsibility-level access for scorecard tabs.

Usage Notes

BSC_SCORECARD_PUB is invoked primarily by the Oracle Balanced Scorecard forms and by concurrent programs that provision or synchronize scorecards and their access grants. The package is referenced by seven other packages, reflecting a central role in the BSC module's internal call graph. Custom extensions that must create or maintain scorecard tabs should call Create_Tab, Update_Tab, and Delete_Tab rather than writing directly to the underlying tables, and should use the access and validation routines to keep FND grants synchronized. Callers must supply the p_commit flag, which defaults to FND_API.G_FALSE, and should inspect x_return_status and the message count/data outputs on every call.