Search Results empty_blob

Overview

APPS.BSC_SYS_IMAGES_PKG is a PL/SQL package body in the Oracle E-Business Suite Balanced Scorecard (BSC) product family that provides the programmatic interface for maintaining records in the BSC_SYS_IMAGES table. This table stores the metadata and binary content associated with system-supplied images used by the Balanced Scorecard application, including the image file name, description, display dimensions, MIME type, and the binary large object that holds the image payload itself. The package therefore serves as the primary API through which the BSC schema registers, updates, and re-loads image resources referenced by scorecard dashboards, strategy maps, and related visualization components.

The package is classified in ETRM as an OTHER API, meaning it is not a public, supported extension interface but an internal utility invoked by other BSC components. Its structure — a thin overloaded wrapper around a single UPDATE statement — confirms that it was designed for internal, low-level maintenance of image metadata rather than for customer extension.

Key Procedures and Functions

The package exposes four documented program units, all of which are procedures (no functions are documented).

• UPDATE_ROW — The core maintenance routine for existing image records. Two overloads exist. The first overload accepts the file name, description, width, height, and audit columns, and delegates to the second overload by supplying an empty string for the MIME type. The second, primary overload (added under Bug#4028672 to introduce MIME_TYPE support) updates DESCRIPTION, WIDTH, HEIGHT, MIME_TYPE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN on the matching row, and explicitly resets FILE_BODY to EMPTY_BLOB(). The WHERE clause matches on FILE_NAME and guards against lost updates by requiring that the stored LAST_UPDATE_DATE be less than or equal to the supplied last-update date. Commented-out code shows that a prior design loaded the image from a database directory via BFILENAME and DBMS_LOB.LOADFROMFILE against the OA_MEDIA directory; this logic is disabled in the current source.
• INSERT_ROW — Inserts a new image record, accepting the image identifier, file name, description, dimensions, and associated attributes. It is the counterpart to UPDATE_ROW for creating entries in BSC_SYS_IMAGES.

The overloaded signature of UPDATE_ROW preserves backward compatibility for existing callers that do not supply a MIME type, while allowing newer callers to specify it explicitly.

Tables Accessed

The package operates exclusively on a single documented table, BSC_SYS_IMAGES, accessed through its APPS synonym. Columns touched include FILE_NAME, DESCRIPTION, WIDTH, HEIGHT, MIME_TYPE, FILE_BODY, and the standard WHO audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The FILE_BODY column is the BLOB that physically contains the image; the mention of "file_body" in the search term aligns directly with this column's manipulation inside UPDATE_ROW.

Usage Notes

Because the package is flagged OTHER and carries a "noship" (not shipped) header, it is intended for internal BSC application use and is not published as a supported customer API. It is referenced by three other BSC packages, which supply the orchestration — likely invoked during patching, image synchronisation, or administrative maintenance of scorecard image assets. Developers extending Balanced Scorecard functionality should treat BSC_SYS_IMAGES_PKG as an internal dependency rather than a stable integration point, and should avoid calling it directly where a supported alternative exists.