Results for “fnd_new_messages”

50+ results




Overview
Explore in AI Chat

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

Overview

FND_NEW_MESSAGES is a core Application Object Library (FND) table in Oracle E-Business Suite, owned by the APPLSYS schema. It stores the application messages delivered and displayed to users in GUI (Forms-based) mode. Each row represents a single translatable message definition, keyed by the application that owns it, the message name used to reference it in code, and the language in which the message text is stored. Because Oracle EBS is fully multilingual, an identical logical message is typically represented once per installed language code, making this table the central repository for runtime message resolution across the E-Business Suite.

From a dimensional or Data Vault modeling perspective, the metadata classification for this object is heuristic and "satellite-leaning." In practice this reflects the table's role as a descriptive attribute store: the true business identity of a message is carried by the composite key (application plus message name), while the surrounding columns (text, type, severity, description) are descriptive payload. A Data Vault model would therefore treat FND_NEW_MESSAGES as a satellite attached to a hub or link defined on APPLICATION_ID and MESSAGE_NAME.

Key Information Stored

The documented physical schema exposes 17 columns. The most significant are:

  • APPLICATION_ID — identifies the owning application; part of the primary key and a foreign key to FND_APPLICATION.
  • MESSAGE_NAME — the programmatic identifier used by forms and PL/SQL to retrieve the message; part of the primary key.
  • LANGUAGE_CODE — the language of the stored text; part of the primary key and a foreign key to FND_LANGUAGES.
  • MESSAGE_TEXT — the actual message string displayed to the user; the principal descriptive attribute.
  • MESSAGE_NUMBER — an optional numeric identifier associated with the message.
  • DESCRIPTION — developer-facing explanation of the message's purpose.
  • TYPE — the message classification (for example, warning, error, or note).
  • MAX_LENGTH — the maximum permitted length of the message text.
  • CATEGORY — a grouping attribute for organizing messages.
  • SEVERITY and FND_LOG_SEVERITY — severity indicators used for display and for integration with FND logging.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • ZD_EDITION_NAME — the editioning column present in 12.2 online patching architecture.

The surrogate primary key is FND_NEW_MESSAGES_PK, defined over APPLICATION_ID, MESSAGE_NAME, and LANGUAGE_CODE. In the 12.2.2 documented schema, the unique index additionally includes ZD_EDITION_NAME, reflecting edition-based redefinition. The true business-key candidates are therefore APPLICATION_ID, MESSAGE_NAME, and LANGUAGE_CODE (plus edition), not a single generated surrogate.

Common Use Cases and Queries

FND_NEW_MESSAGES is queried primarily for message administration, translation verification, and diagnostics. Typical patterns include retrieving the text for a known message, checking for missing translations, and auditing message severity.

  • Look up a message by name and language: SELECT MESSAGE_TEXT FROM FND_NEW_MESSAGES WHERE APPLICATION_ID = :app AND MESSAGE_NAME = :name AND LANGUAGE_CODE = 'US';
  • Identify messages without a translation for a given language by comparing row counts per LANGUAGE_CODE.
  • Report on all messages of a specific TYPE or SEVERITY for a given application.
  • Validate that MAX_LENGTH is consistent with actual MESSAGE_TEXT lengths.
  • Join to FND_APPLICATION to display the owning application name alongside messages.

Related Objects

The table participates in several documented relationships:

These relationships confirm FND_NEW_MESSAGES as a foundational, referenced lookup source for message text consumed by both core and module-specific functionality.