Search Results gl_bis_reports_pkg

Overview

APPS.GL_BIS_REPORTS_PKG is a utility package in the Oracle E-Business Suite General Ledger module whose stated purpose is to contain "various BIS reports utilities." BIS denotes the Business Intelligence System layer historically bundled with Oracle EBS, and this package provides the supporting PL/SQL infrastructure used by GL-related BIS reporting components. The package was created on 13-JUL-1999 by K Chang and carries a header revision marker of 120.2 dated 2005/05/05, indicating that it has remained largely stable across the 11i through 12.1.1 and 12.2.2 releases. It is declared with AUTHID CURRENT_USER, meaning that its SQL executes under the privileges of the invoking session rather than the package owner, a convention that allows the package to be shared by multiple callers while relying on APPS synonym resolution for underlying data access.

Key Procedures and Functions

The package exposes a deliberately small public interface consisting of two documented members. Both were present in the original 1999 creation and have not been expanded in the documented metadata.

• INITIALIZE — A procedure that accepts a Set of Book identifier and stores it in the package's global state. Its documented purpose is to "initialize set of book id." Because GL reporting logic is always scoped to a ledger or Set of Books, this routine establishes the reporting context before any BIS report utility is used. It corresponds directly to the global variable G_SOB_ID, which is initialized to NULL at package instantiation.
• GET_SOB_ID — A function that returns a NUMBER. Its documented purpose is simply to "get the Set of book ID." It provides read access to the value set by INITIALIZE, allowing callers and internal routines to retrieve the current reporting ledger without re-querying session context.

Together these two members implement a minimal set/get pattern over a single package-level global, G_SOB_ID. No other procedures, functions, or overloads are documented for this package.

Tables Accessed

The documented metadata lists no tables referenced via APPS synonyms. This is consistent with the package's design: it is a state-holding utility rather than a data access layer. No SQL against GL tables such as GL_SETS_OF_BOOKS, GL_JE_HEADERS, or GL_BALANCES is attributed to it. Any persistence or retrieval of Set of Book information is the responsibility of the calling program, which passes the identifier into INITIALIZE and later retrieves it through GET_SOB_ID.

Usage Notes

Because GL_BIS_REPORTS_PKG is classified as OTHER rather than as a public API, and because it is referenced by zero other packages according to the documented metadata, it should be treated as an internal support routine. Typical invocation occurs from BIS reporting code paths and legacy GL reporting utilities, where a caller first executes GL_BIS_REPORTS_PKG.INITIALIZE with the active Set of Book identifier and subsequently calls GET_SOB_ID whenever that identifier is needed during report generation. The pattern is well suited to concurrent program and server-side PL/SQL contexts, where a single database session processes a report for one ledger.

Custom developers who find the package through a dependency search should note several practical cautions. First, the package holds state in a global variable, so the value of G_SOB_ID persists for the life of the session and can be overwritten by any subsequent INITIALIZE call; callers must re-initialize whenever the reporting ledger changes. Second, because the package uses AUTHID CURRENT_USER, execute privileges and synonym resolution depend on the invoking schema. Third, Oracle does not document this package as a supported extension point, so custom code that depends on it risks breakage during patching or upgrade. Where possible, new development should determine the current ledger through supported GL APIs and views rather than through this legacy utility.