Search Results detach_workspace

Overview

BSC_AW_MANAGEMENT is an Oracle EBS PL/SQL package owned by the APPS schema and classified as OTHER, meaning it is an internal infrastructure utility rather than a public business API. It is the workspace and locking controller for the Oracle Balanced Scorecard (BSC) Analytic Workspace (AW) subsystem. The package manages the lifecycle of the OLAP workspace attached to a BSC application session, including creating, attaching, detaching, committing, and dropping workspaces, and it coordinates row-level locks over the objects contained in that workspace. Its central abstraction is the lock set: a named collection of locked objects held together so that a transaction can update, release, or commit them atomically. The Lock Set design directly supports the "lock_set" search term, since BSC_AW_MANAGEMENT defines both a lock set record structure and dedicated procedures (SAVE_LOCK_SET, LOCK_LOCK_SET, COMMIT_LOCK_SET) to persist and manage these sets. The package references only DBMS_SQL and PLITBLM (via APPS synonyms), confirming that it acts as a thin control layer over dynamic SQL and workspace registration rather than a data-entry component. The header version stamp (120.8, dated 2006/03/31) indicates the package predates and remains compatible with Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes 33 documented procedures and functions, organized into workspace management, locking, and lock set handling.

• GET_WORKSPACE_LOCK — acquires a workspace-level lock, offered in overloaded forms based on object collection or mode.
• GET_LOCK — acquires locks on named objects or object collections, with overloads for mode/options or explicit locked object lists.
• GET_AW_WORKSPACE_NAME — returns the current analytic workspace name.
• ATTACH_WORKSPACE / DETACH_WORKSPACE / DETACH_AW_WORKSPACE — attach and release the workspace from the current session.
• CREATE_WORKSPACE / DROP_WORKSPACE — create or remove a workspace, with optional naming.
• COMMIT_AW / COMMIT_AW_MULTI — commit changes to the workspace, singly or across multiple locked objects.
• EXEC_WORKSPACE_SETTINGS — applies runtime workspace configuration.
• RELEASE_LOCK — releases a lock held on a specific object.
• SAVE_LOCK_SET / LOCK_LOCK_SET / COMMIT_LOCK_SET — persist a named lock set, acquire the locks defined within it, and commit it as a unit.
• GET_LOCK_OBJECT — resolves a lock object reference.
• CREATE_DEFAULT_ELEMENTS / SET_HASH_PARTITION_DIM / UPDATE_AW / INIT_ALL — initialize workspace elements, hash partition dimensions, update the AW, and perform full package initialization.

Tables Accessed

Per the ETRM metadata, the only referenced objects are the DBMS_SQL and PLITBLM synonyms. DBMS_SQL is used to execute dynamic DDL/DML against workspace and lock registry structures, while PLITBLM likely provides localization or PL/SQL table utilities. The package does not read or write application transaction tables directly; instead, its persistent state (workspace definitions, lock sets, locked object registries) is handled through the AW infrastructure and auxiliary table types such as lock_sets_tv and current_sessions_tb, which are populated dynamically rather than via static SQL. This confirms the package operates as a coordination layer rather than a data store.

Usage Notes

BSC_AW_MANAGEMENT is invoked programmatically by internal BSC components and by other PL/SQL packages rather than by end users. The ETRM metadata records 9 other packages referencing it, indicating a hub-and-spoke pattern in which higher-level BSC scorecard and AW processing routines delegate workspace and lock coordination to this package. It is typically called during AW session bootstrap (INIT_ALL, ATTACH_WORKSPACE), during scorecard update commits (COMMIT_AW, COMMIT_LOCK_SET), and during cleanup (DETACH_WORKSPACE, RELEASE_LOCK). Because it is classified OTHER and not documented as a public API, customizations should avoid direct invocation and instead rely on supported BSC entry points. Two write modes are supported — single-object (COMMIT_AW) and multi-object (COMMIT_AW_MULTI) — which matters when a logic operation spans several locked objects. On 12.2.x the package remains unchanged, so any migration testing should focus on DBMS_SQL behavior and workspace registration rather than on the package's own signature.