Search Results bsc_security




Overview
Explore in AI Chat

Overview

APPS.BSC_SECURITY is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is part of the Balanced Scorecard (BSC) application family and is classified under the generic API category (OTHER) in the ETRM repository. Its status is VALID in the documented environment.

The package functions as the internal security and concurrency-control utility for the Balanced Scorecard module. It governs session-level locking across the BSC subsystem, resolves user identity and preference information from the EBS session model, and determines whether performance-management or metadata-driven operations may proceed at a given point in time. Rather than exposing a formal public business API, it supplies low-level primitives consumed by other BSC packages — most notably BSC_LOCKS_PUB and by itself through internal recursion. Because of this role, it is best understood as a background control layer rather than an end-user-facing component.

Key Procedures and Functions

The documented package exposes eleven procedures and functions. The principal routines include:

  • GET_USER_INFO — Retrieves user-related information, typically resolving the current EBS user context into BSC user attributes used by downstream security checks.
  • CHECK_SYSTEM_LOCK — Determines whether a system-wide BSC lock is currently held, preventing conflicting operations.
  • REFRESH_SYSTEM_LOCK — Re-issues or extends the system lock so that a long-running operation retains exclusive control of the BSC subsystem.
  • CHECK_SOURCE_SYSTEM_LOCK — Verifies whether a lock is held against a specific source system, allowing per-source serialization separate from the global lock.
  • USER_HAS_LOCK — Reports whether the calling user owns the lock in question, used to authorize release or override actions.
  • DELETE_BSC_SESSION and DELETE_BSC_SESSION_ICX — Remove stale or terminated session records from the BSC session tracking tables; the ICX variant specifically reconciles against the Oracle iCX/Applications session framework.
  • CAN_META_RUN — Evaluates whether a metadata-related BSC process is permitted to execute given current locking and session state.
  • IS_META_INSIDE — Indicates whether execution is occurring inside a metadata operation, allowing callers to branch behavior accordingly.

Parameter lists are not documented in the ETRM extract and should be confirmed against the package specification in the target instance.

Tables Accessed

The package reads and writes several tables through APPS synonyms:

  • BSC_CURRENT_SESSIONS — the core session registry used to track active BSC users and support the delete-session routines.
  • BSC_MESSAGE_LOGS — logs diagnostic or error messages generated during locking and security evaluation.
  • BSC_USER_INFO — stores per-user BSC attributes returned by GET_USER_INFO.
  • ICX_SESSIONS — the EBS session table used to validate session identity and age.
  • DBMS_SQL, DUAL, USER_OBJECTS, V$SESSION, V$SESSION_WAIT — dynamic SQL, object existence checks, and v$ views used to detect blocking or waiting sessions.

Usage Notes

BSC_SECURITY is invoked internally by BSC_LOCKS_PUB and by other routines within the package itself; it is not intended for direct invocation from Oracle Forms or concurrent programs. Customizations should avoid calling it directly, since lock state semantics are managed cooperatively by the BSC lock framework. Where integration is required, the documented dependency surface — BSC_LOCKS_PUB — should be preferred as the entry point.