Results for “global_names”

33 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.BIS_INIT package body provides the initialization routine for the Business Intelligence System (BIS) and Enterprise Data Warehouse (EDW) components of Oracle E-Business Suite. Its principal role is to detect the configuration of the current database instance and to establish the session-level settings required before EDW extraction, transformation, and load operations can proceed. The package determines whether the instance is acting as an EDW source, an EDW warehouse, or both, and then applies the appropriate session context. This initialization logic is a prerequisite for the correct operation of downstream BIS/EDW programs, which rely on the session state established here.

The package is classified under the API classification OTHER in the ETRM repository for release 12.1.1, and it remains present in 12.2.2. The header comment indicates an origin date of 2005 and references development through bug fixes such as 3871867, which introduced dynamic resolution of the BIS schema name rather than a hard-coded value.

Key Procedures and Functions

The package exposes a single documented procedure:

  • INITIALIZE — The sole documented entry point. It reads the BIS_IMPLEMENTATION_TYPE profile option to determine whether the environment is a pure OLTP instance. When the profile value is OLTP, the procedure performs no further action. Otherwise, it inspects the data dictionary to establish whether the current instance hosts EDW source structures and/or EDW warehouse structures, and then sets the corresponding session state. The procedure also declares an exception handler that captures SQLCODE and SQLERRM values, and the referenced EDW_ERROR_LOG table indicates that failures are logged for diagnostic purposes. All operations are executed as dynamic SQL through EXECUTE IMMEDIATE to accommodate the runtime-resolved schema name.

Tables Accessed

The initialization logic queries the following objects:

  • DBA_TABLES — Read to determine whether the resolved BIS schema contains the marker tables EDW_LOCAL_INSTANCE and EDW_SOURCE_INSTANCES. The presence of the former identifies the instance as an EDW source; the presence of the latter identifies it as an EDW warehouse.
  • EDW_ERROR_LOG — Referenced for recording error information captured in the exception handler, providing an audit trail when initialization fails.

In addition, the procedure issues dynamic queries against EDW_LOCAL_INSTANCE and EDW_SOURCE_INSTANCES to count their rows and confirm instance role. These objects are qualified with the schema returned by FND_INSTALLATION.GET_APP_INFO for the BIS application, defaulting to BIS when that call fails.

Usage Notes

BIS_INIT.INITIALIZE is designed to be invoked at the start of a session that will perform BIS or EDW processing, so that the correct EDW security context is established before any data movement occurs. The package is not referenced by any other documented package in the ETRM repository, which indicates that it is generally called directly by concurrent programs, standalone scripts, or custom code rather than through package-to-package dependencies.

The procedure relies on the BIS_IMPLEMENTATION_TYPE profile option; if that profile is set to OLTP, all EDW-specific initialization is skipped. When the instance is identified as an EDW source, the procedure executes ALTER SESSION SET global_names = false, a setting commonly required in distributed EDW environments where database link naming would otherwise conflict with the GLOBAL_NAMES initialization parameter. When the instance is identified as an EDW warehouse, it invokes EDW_SEC_PKG.SET_CONTEXT to populate the session attributes used by EDW security policies. Administrators should ensure that the executing user has sufficient privileges to read DBA_TABLES and to alter session parameters, and that the BIS schema is correctly registered in FND_INSTALLATION.