Search Results bsc_message




Overview
Explore in AI Chat

Overview

APPS.BSC_MESSAGE is a PL/SQL package body in the Oracle E-Business Suite Balanced Scorecard module. It provides the internal implementation for a lightweight, session-scoped message buffering and logging mechanism used throughout the BSC (Balanced Scorecard) application. The package collects diagnostic, informational, and error messages generated during BSC processing, stores them in memory during the lifetime of a session, and controls when those messages are written to the persistent message log. Because it is a package body rather than an API classified for external invocation, BSC_MESSAGE functions primarily as infrastructure: it supports other BSC packages that need to emit status and error text without managing their own logging logic. The package depends on APPS.BSC_APPS, APPS.BSC_UTILITY, APPS.BSC_MESSAGE_LOGS, and the PUBLIC.PLITBLM PL/SQL table type, and its status is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2.

A distinguishing characteristic is that APPS.BSC_MESSAGE is not referenced by any database object, yet it references numerous BSC components. It therefore sits at the top of the BSC dependency hierarchy as a consumer rather than a provider, and it is itself referenced by 31 other BSC packages that rely on its message-handling capabilities.

Key Procedures and Functions

The package body exposes seven documented program units:

  • INIT — Initializes the internal message buffer and session state. It is normally the first routine called in a processing cycle so that subsequent messages are captured cleanly.
  • RESET — Clears the in-memory message buffer without writing its contents, returning the package to a pristine state for a new processing context.
  • COUNT — Returns the number of messages currently held in the buffer, allowing callers to determine whether any messages are pending.
  • ADD — Appends a message to the in-memory buffer. This is the primary entry point used by other BSC packages to record informational or error text.
  • FLUSH — Persists the buffered messages to the message log table, typically writing accumulated content to BSC_MESSAGE_LOGS.
  • CLEAN — Removes or trims message log entries, supporting housekeeping and retention of the message log table.
  • SHOW — Displays or retrieves buffered or logged messages for user or developer review.

No parameter lists are asserted here because the ETRM metadata documents only the program unit names and their roles.

Tables Accessed

Two tables are documented as being referenced through APPS synonyms:

  • BSC_MESSAGE_LOGS — The persistent repository for messages captured by the package. FLUSH writes buffered content here, CLEAN purges or maintains it, and SHOW may read from it. This table provides the durable audit trail of BSC processing messages.
  • PLITBLM — The Oracle-supplied PL/SQL table type from the PUBLIC schema. BSC_MESSAGE uses a PLITBLM-based structure to hold messages in memory before flushing, which explains why no application table other than BSC_MESSAGE_LOGS is required for buffering.

Usage Notes

BSC_MESSAGE is invoked internally by BSC application logic rather than directly by end users or through a dedicated concurrent program. Its typical lifecycle is INIT, followed by one or more ADD calls during processing, an optional COUNT check, and finally FLUSH to persist the accumulated messages; RESET may be used instead of FLUSH when buffered messages should be discarded. The 31 packages that reference BSC_MESSAGE confirm that it acts as shared logging infrastructure across the Balanced Scorecard module, and administrators or developers diagnosing BSC behavior should inspect BSC_MESSAGE_LOGS to review the output produced through this package.