Results for “is_column_in_object”

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

Overview

The PL/SQL package body APPS.BSC_IM_UTILS is a utility library within the Oracle E-Business Suite Balanced Scorecard (BSC) Intelligence/Indicator Management subsystem. It provides a shared set of low-level helper routines that other BSC packages rely upon for tasks such as file and log handling, debug output, dynamic SQL metadata inspection, string parsing, and determination of data-model semantics. The header BSCOLUTB.pls 120.9 indicates the file belongs to the BSC Online Utilities family of database objects. Unlike a business-facing API, BSC_IM_UTILS is an internal infrastructure package: it does not represent a user transaction, but rather supplies reusable primitives that the BSC calculation and materialized-view maintenance logic depends on. The ETRM metadata classifies the package as OTHER, consistent with its role as a technical helper library rather than a formal public API. Its 102 documented procedures and functions are referenced by 11 other packages, confirming its position as a foundational dependency within the Balanced Scorecard schema.

Key Procedures and Functions

Among the 102 documented entry points, the debug and logging routines are among the most frequently cited. WRITE_TO_DEBUG_N, WRITE_TO_DEBUG, WRITE_TO_LOG, WRITE_TO_LOG_FILE, WRITE_TO_LOG_FILE_S and WRITE_TO_LOG_FILE_N write diagnostic or message text to debug and log destinations, with the _N and _S variants distinguishing numeric and string payload handling. Output-file counterparts include WRITE_TO_OUT_FILE, WRITE_TO_OUT_FILE_S and WRITE_TO_OUT_FILE_N. OPEN_FILE initializes a file handle for these writers. Several parsing and inspection utilities are documented: GETPARSEDINDICNUMBER extracts an indicator number from table names of the form BSC_S_3005_0_0_1 or BSC_SB_4885_0_2_1; ISNUMBER validates numeric strings; GET_TIME returns a timestamp; and IS_COLUMN_IN_OBJECT, IN_ARRAY, and SET_GLOBALS provide metadata and session state support. Semantic helpers NEEDS_ZERO_CODE_MV and NEEDS_ZERO_CODE_B_PT determine whether a zero code is required for a materialized view or a base/projection table. GET_DB_USER resolves the database user, and ADD_DISTINCT_VALUES_TO_TABLE augments a target table with distinct values.

Tables Accessed

The package reads configuration and definition metadata from BSC tables including BSC_DB_CALCULATIONS (calculation definitions, calculation types, parameters), BSC_KPI_DATA_TABLES (mapping between indicators and materialized views), BSC_DB_TABLES_RELS (table relationships), and BSC_DB_RESERVED_WORDS. Dictionary and dynamic-SQL support come from ALL_MVIEW_DETAIL_RELATIONS, USER_OBJECTS, USER_SYNONYMS, USER_VIEWS and DUAL, while DBMS_MVIEW, DBMS_SQL, DBMS_UTILITY and PLITBLM supply built-in package functionality. These accesses support metadata lookups and dynamic object inspection rather than transactional data.

Usage Notes

BSC_IM_UTILS is normally invoked indirectly by other BSC packages, concurrent programs that refresh Balanced Scorecard materialized views, and custom extensions that need consistent logging, parsing, or zero-code determination. Developers instrumenting BSC code commonly call WRITE_TO_LOG_FILE and WRITE_TO_DEBUG_N to capture diagnostics. The handling of the search term write_to_debug_n reflects its routine use as a debugging aid when diagnosing indicator and materialized-view processing.