Results for “pon_custom_messages”

4 results




Overview
Explore in AI Chat

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

Overview

PON_CUSTOM_MESSAGES is a Sourcing (PON) module table that stores application messages which have been customized. In the Oracle E-Business Suite architecture, Oracle Sourcing relies on the Oracle Application Object Library (FND) message framework to deliver user-facing text for validation errors, workflow notifications, negotiation status prompts, and other runtime feedback. The FND_NEW_MESSAGES table holds the base, seeded message repository shipped with the application. PON_CUSTOM_MESSAGES provides a Sourcing-specific layer where messages can be overridden or extended, allowing an implementation to tailor message text without modifying Oracle-owned seed data.

From a data modeling perspective, the metadata's heuristic Data Vault classification identifies this table as a link. This is a useful modeling suggestion: the table does not own a natural business entity so much as it associates three reference dimensions — an application, a language, and a message name — while carrying the customized message payload. In Data Vault terms it behaves as a relationship or link construct connecting the FND application and language hubs to the message definition.

Notably, the ETRM metadata records this table as "Not implemented in this database." That indicator reflects the specific environment inventoried at documentation time, not a universal condition. Many production 12.1.1 and 12.2.2 instances will not contain this table because Oracle does not create every optional or customer-populated object in every schema. The presence of the object definition in the data model documentation, however, confirms its role as the intended customization store when the feature is used.

Key Information Stored

The primary key PON_CUSTOM_MESSAGES_PK is a composite of three columns, all of which are also business-key candidates rather than a system-generated surrogate:

  • APPLICATION_ID — Identifies the owning FND application (for Sourcing, the PON application identifier). Part of the primary key.
  • LANGUAGE_CODE — The language in which the customized message is expressed, enabling language-specific overrides. Part of the primary key.
  • MESSAGE_NAME — The FND message name being customized; the logical identifier that ties the row back to the base message definition. Part of the primary key.

Because the key is composed entirely of these three columns, uniqueness is enforced at the granularity of one customized message per application, per language, per message name. The table is therefore a narrow, key-heavy structure with minimal descriptive columns in the documented metadata; any customized message text itself is carried as the value payload associated with this composite key.

Common Use Cases and Queries

The principal use case is message customization auditing — determining which Sourcing messages an implementation has overridden and in which languages. A representative query joins to the base message table to compare customized against seeded content:

  • List all customized Sourcing messages: SELECT message_name, language_code FROM pon_custom_messages WHERE application_id = :pon_app_id;
  • Identify overrides for a specific language: SELECT message_name FROM pon_custom_messages WHERE language_code = 'US';
  • Confirm coverage across languages by grouping on LANGUAGE_CODE and counting MESSAGE_NAME values.
  • Reconcile customized entries against FND_NEW_MESSAGES to find messages that have been customized but whose base definition has since changed.
  • Support migration or clone validation by extracting the full customized message inventory before and after an environment refresh.

Reporting use cases include translation readiness checks, localization audits, and release impact analysis when Oracle patches alter seeded message text.

Related Objects

The foreign key metadata establishes the following documented relationships, each joined on the columns shown:

  • FND_NEW_MESSAGES — joined via PON_CUSTOM_MESSAGES.APPLICATION_ID and MESSAGE_NAME (and LANGUAGE_CODE); supplies the base message definitions being customized.
  • FND_APPLICATION — joined via PON_CUSTOM_MESSAGES.APPLICATION_ID; resolves the owning application name and short name.
  • FND_LANGUAGES — joined via PON_CUSTOM_MESSAGES.LANGUAGE_CODE; provides installed language context.

Beyond these documented references, Sourcing message consumption flows through the standard FND message APIs, so impact analysis should also consider FND_MESSAGE and the Oracle Sourcing negotiation and notification components that emit the affected messages.