Results for “bsc_messages”

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

Overview

BSC_MESSAGES is a VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the BSC (Balanced Scorecard) product family and is documented in ETRM as a "View of FND_NEW_MESSAGES." The view exists to expose the Oracle Application Object Library (FND) message repository — the standard message dictionary — filtered to the messages owned by the Balanced Scorecard application. In practical terms, BSC_MESSAGES is a localized, application-scoped projection of the FND_NEW_MESSAGES table.

Its role in reporting and integration is narrow but precise. Balanced Scorecard components, including the BSC Administration and Web-based Scorecard interfaces, frequently reference message text for error handling, validation feedback, and user-facing notifications. Rather than querying FND_NEW_MESSAGES directly and filtering manually, developers and report authors can query BSC_MESSAGES to obtain only BSC-owned messages for the currently connected language. This view is therefore primarily a developer and diagnostic aid rather than an end-user reporting source.

Underlying Base Objects

The view is defined over a single documented base object: FND_NEW_MESSAGES, aliased as "B" in the view text. No other base objects are referenced. The defining SQL is straightforward:

SELECT B.APPLICATION_ID, B.LANGUAGE_CODE, B.MESSAGE_NUMBER, B.MESSAGE_NAME, B.MESSAGE_TEXT, B.CREATION_DATE, B.CREATED_BY, B.LAST_UPDATE_DATE, B.LAST_UPDATED_BY, B.LAST_UPDATE_LOGIN, B.DESCRIPTION, B.TYPE, B.MAX_LENGTH FROM FND_NEW_MESSAGES B WHERE B.LANGUAGE_CODE = USERENV('LANG') AND B.APPLICATION_ID = 271

Two predicates define its behavior. First, LANGUAGE_CODE is restricted to USERENV('LANG'), meaning the view returns only messages in the session's current language setting. This is consistent with EBS message dictionary conventions, where translations are stored as separate rows per language. Second, APPLICATION_ID is fixed at 271, the application identifier for Balanced Scorecard. Consequently, the view always returns messages belonging exclusively to BSC, regardless of the connecting user or responsibility.

FND_NEW_MESSAGES is the standard message repository populated by the message dictionary and by the FNDLOAD/AD utility loaders. Changes to message definitions via the Application Developer responsibility propagate to this view immediately, as no materialization or staging is involved.

Key Columns

• APPLICATION_ID — Always 271 for rows returned by this view; the BSC application identifier.
• LANGUAGE_CODE — The language of the message row, equal to the session's USERENV('LANG') value.
• MESSAGE_NUMBER — The numeric identifier of the message, combined with APPLICATION_ID to form the message key.
• MESSAGE_NAME — The symbolic message name used in code, e.g., FND_MSG_PUB calls.
• MESSAGE_TEXT — The translatable, user-facing text, including substitution tokens such as &MSGTOKEN.
• TYPE — Message severity type (for example, error, warning, or information), governing how FND_MSG_PUB handles it.
• MAX_LENGTH — Maximum length permitted for the message text, useful for validation checks.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording who created or last modified the message and when.

Common Use Cases and Queries

A typical use case is confirming that a specific BSC message exists and inspecting its text and severity, which is valuable when diagnosing user-facing errors in Balanced Scorecard functionality.

• Look up a message by name: SELECT MESSAGE_NAME, MESSAGE_TEXT, TYPE FROM APPS.BSC_MESSAGES WHERE MESSAGE_NAME = 'BSC_SOME_MSG';
• Search text for a token: SELECT APPLICATION_ID, MESSAGE_NAME, MESSAGE_TEXT FROM APPS.BSC_MESSAGES WHERE MESSAGE_TEXT LIKE '%&%';
• Audit recent changes: SELECT MESSAGE_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM APPS.BSC_MESSAGES ORDER BY LAST_UPDATE_DATE DESC;

Because the view filters on USERENV('LANG'), results differ by session language; queries intended to enumerate all translations must target FND_NEW_MESSAGES directly. Callers should also grant appropriate privileges, as the view is owned by APPS and rights are not automatically extended to custom schemas.