Search Results log_n

Overview

BSC_AW_MANAGEMENT is the workspace concurrency-control package for Oracle Balanced Scorecard (BSC) Analytic Workspace (AW) operations in Oracle E-Business Suite 12.1.1 and 12.2.2. Analytic Workspaces are OLAP schemas that hold the cubes, dimensions, and measures used by Balanced Scorecard reporting. Multiple sessions — adapters, loaders, and graphical user interfaces — may attempt to modify the same AW simultaneously. The package coordinates these accesses so that writers obtain exclusive control when required while not blocking readers unnecessarily.

The comments in the package source state the design intent explicitly: adapter and loader processes do not acquire exclusive locks directly. Instead they request that a workspace be attached and supply a list of the objects they intend to touch. BSC_AW_MANAGEMENT then inspects the database version and acquires the appropriate lock. If a conflicting lock already exists, the caller waits. On Oracle 10g and later, a global variable (g_locked_objects) records which objects have been locked; when a commit is encountered, those objects are released and the commit is issued, mirroring the database's own release-locks-on-commit semantics.

Key Procedures and Functions

• GET_WORKSPACE_LOCK — Overloaded entry point that acquires the workspace lock. One form accepts a list of objects and options; the other accepts a lock mode and options. It decides between a partial (object-list) lock and a full read/write lock based on whether any objects were supplied and on the database version.
• GET_LOCK and GET_LOCK_OBJECT — Perform the underlying lock acquisition in a specific mode and for a specific object.
• RELEASE_LOCK — Releases a held lock.
• ATTACH_WORKSPACE and DETACH_WORKSPACE — Attach and detach an analytic workspace. attach_workspace is the search term that led to this object; it is the documented operation by which a session binds to an AW prior to reading or writing its objects.
• DETACH_AW_WORKSPACE — Variant of detachment used in specific internal flows.
• GET_AW_WORKSPACE_NAME — Resolves the name of the analytic workspace associated with the current context.
• COMMIT_AW and COMMIT_AW_MULTI — Commit changes to a single workspace or to multiple workspaces, releasing the tracked locks as part of the operation.
• CREATE_WORKSPACE and DROP_WORKSPACE — Create and remove analytic workspaces.
• CREATE_DEFAULT_ELEMENTS — Populates the default elements required when a read/write lock is established.
• EXEC_WORKSPACE_SETTINGS — Applies workspace-level settings.
• SET_HASH_PARTITION_DIM — Configures the hash partition dimension for the workspace.
• SAVE_LOCK_SET, LOCK_LOCK_SET, and COMMIT_LOCK_SET — Manage persistent lock sets, allowing a related group of objects to be locked, saved, and committed together.
• UPDATE_AW — Refreshes or updates workspace contents.
• INIT_ALL — Initialization routine used when the package is first loaded.

Tables Accessed

The package does not manipulate OLAP data through conventional application tables. Its documented object references are DBMS_SQL and PLITBLM. DBMS_SQL supplies the dynamic SQL and PL/SQL table types (notably DBMS_SQL.VARCHAR2_TABLE) used to pass the list of objects to be locked, which is central to the object-list locking strategy. PLITBLM is the standard EBS PL/SQL table type package used for in-memory collections. Analytic workspace contents themselves reside in the OLAP AW schema and are reached through the AW attach/detach interface rather than through SQL DML.

Usage Notes

BSC_AW_MANAGEMENT is an internal infrastructure package rather than an end-user API. It is invoked by BSC adapter and loader programs, by Balanced Scorecard forms and concurrent programs that read or write analytic workspaces, and by other PL/SQL packages — the ETRM metadata records nine packages that reference it. The typical sequence is: call GET_WORKSPACE_LOCK to register the objects the session intends to modify, call ATTACH_WORKSPACE, perform the workspace operations, then call COMMIT_AW (or COMMIT_AW_MULTI, or the lock-set commit routines) so that tracked locks are released in step with the transaction commit. Because the package handles the database-version-dependent locking logic internally, callers should not attempt to acquire exclusive AW locks themselves; doing so would bypass the g_locked_objects bookkeeping that makes commit-time release reliable. The package is not supported for direct customer modification and is subject to change between EBS releases.