Search Results bis_collection_utilities




Overview
Explore in AI Chat

Overview

BIS_COLLECTION_UTILITIES is an APPS-owned PL/SQL package body classified under the Oracle EBS Business Intelligence System (BIS) schema family. Its principal business function is to support the collection and refresh infrastructure that governs how BIS-derived data marts and summary objects are populated from E-Business Suite transactional sources. In practical terms, the package provides the shared utility layer used by BIS collection programs to establish session context (SETUP/WRAPUP), record refresh telemetry and failures, retrieve prior refresh periods and dates, log diagnostic and debug information, and emit rate- and contract-related exception records used during collections.

It is a heavily consumed dependency rather than an entry point: it is referenced by 20 other database objects, while itself depending on foundational EBS services such as FND_CONCURRENT, FND_GLOBAL, FND_PROFILE, FND_MESSAGE, FND_LOG, FND_FILE, and FND_DATE, as well as BIS-specific reference tables. This dependency footprint confirms the package performs no business data processing in isolation — it standardizes bookkeeping, logging, and helper operations for the broader BIS collection suite. The metadata designation of OTHER further indicates it is an internal, non-public API not subject to the same compatibility guarantees as documented public interfaces.

Key Procedures and Functions

The documented interface exposes 27 procedures and functions. The most prominent include:

  • SETUP and WRAPUP — establish and tear down the execution context for a collection or refresh run, initializing session state and releasing resources on completion.
  • WRITE_BIS_REFRESH_LOG — persists a refresh event record, forming the audit trail for collection activity.
  • GET_LAST_FAILURE_PERIOD, GET_LAST_REFRESH_PERIOD, and GET_LAST_REFRESH_DATES — retrieve the prior failure window, the last successful refresh period, and associated date boundaries, enabling incremental collection logic.
  • GET_LAST_USER_ATTRIBUTES — returns previously stored user-defined collection attributes.
  • LOG, DEBUG, and OUT — provide tiered diagnostic output channels.
  • PUT_NAMES, PUT_LINE, and PUT_LINE_OUT — buffer and emit formatted output lines to the active output destination.
  • WRITEMISSINGRATEHEADER, GETMISSINGRATEHEADER, WRITEMISSINGRATE, and WRITEMISSINGCONTRACT — manage records describing missing exchange rates and contracts encountered during collection, supporting currency conversion diagnostics.
  • DELETELOGFOROBJECT — purges log entries associated with a given object, supporting log maintenance.
  • ENABLEPARALLELDML and DISABLEPARALLELDML — toggle parallel DML execution, allowing large collection writes to be parallelized and then restored to the default state.

Tables Accessed

Access is performed through APPS synonyms. BIS_REFRESH_LOG stores refresh event history written by WRITE_BIS_REFRESH_LOG and queried for prior period and date information. BIS_SYSTEM_DATE defines the collection system date framework used to determine periods. FND_CONCURRENT_PROGRAMS is read to validate or identify the concurrent program context. GL_DAILY_CONVERSION_TYPES supplies currency conversion type reference data underpinning the missing-rate routines. V$PARAMETER and DBA_TABLESPACES are consulted for instance and storage-level configuration, while PLITBLM and DBMS_SQL support dynamic SQL and PL/SQL table operations. FND_FILE, FND_LOG, FND_MESSAGE, FND_GLOBAL, FND_PROFILE, and FND_DATE are invoked as service-level dependencies rather than data tables.

Usage Notes

BIS_COLLECTION_UTILITIES is not intended for direct end-user invocation. It is called from within BIS collection and refresh concurrent programs, which use SETUP and WRAPUP to bracket execution and the logging and refresh-period routines to maintain continuity across runs. Custom collection code extending the BIS framework may safely call the diagnostic and refresh-log helpers, but the parallel DML toggles and missing-rate writers should be used only in the sequence the standard programs employ. Because it is referenced by 20 other packages and is not referenced by any database object itself, it functions as a leaf-level utility within the collection dependency graph; changes to its behavior can propagate broadly across the BIS collection suite in both 12.1.1 and 12.2.2 environments.