Search Results wf_message_attributes_vl




Overview
Explore in AI Chat

Overview

WF_MESSAGE_ATTRIBUTES_VL is a documented, valid database view owned by the APPS schema within the FND – Application Object Library product of Oracle E-Business Suite. Its purpose is to expose the message attribute definitions that underpin the Oracle Workflow messaging infrastructure, combining the language-independent attribute configuration with its translated, language-specific descriptive text. In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as the primary reporting and integration surface for consumers that require message attribute metadata in the run-time session language, without needing to perform the join between base and translation tables manually. The "_VL" suffix indicates that the view returns a single row per attribute whose translation matches the session language established by USERENV('LANG'), rather than returning all installed languages. Because message attributes define the individual parameters that make up a Workflow message or notification, this view is relevant to administrators, integrators, and developers auditing notification content, validating message definitions, and building metadata-driven utilities that enumerate the attributes belonging to a given message type and message name.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the ETRM metadata: WF_MESSAGE_ATTRIBUTES and WF_MESSAGE_ATTRIBUTES_TL. WF_MESSAGE_ATTRIBUTES stores the language-independent definition of each attribute, including its message type, message name, internal name, sequence, data typing, protection levels, and default values. WF_MESSAGE_ATTRIBUTES_TL is the translation table that stores the display name and description for each attribute in each installed language.

The view text joins these two objects on the composite key MESSAGE_NAME, MESSAGE_TYPE, and NAME, and filters WF_MESSAGE_ATTRIBUTES_TL to the row where LANGUAGE equals USERENV('LANG'). The attribute list of the view also includes B.ROWID exposed as ROW_ID, which provides a unique identifier for the base WF_MESSAGE_ATTRIBUTES row. The view therefore performs a one-to-one, language-filtered projection over the joined data set, presenting a flattened and translatable representation of message attribute configuration.

Key Columns

The view exposes the following columns, each reflecting the attribute configuration and its translated text:

  • ROW_ID — The ROWID of the underlying WF_MESSAGE_ATTRIBUTES row, usable as a unique handle to the base attribute record.
  • MESSAGE_TYPE — The internal name of the message type to which the attribute belongs.
  • MESSAGE_NAME — The internal name of the message that owns the attribute.
  • NAME — The internal name of the attribute itself.
  • SEQUENCE — The ordering position of the attribute within the message.
  • TYPE and SUBTYPE — The primary and secondary data typing of the attribute value.
  • VALUE_TYPE — The value type classification for the attribute.
  • PROTECT_LEVEL and CUSTOM_LEVEL — Protection and customization level indicators that govern whether and how the attribute may be modified by customers and during upgrades.
  • FORMAT — The display format applied to the attribute value.
  • TEXT_DEFAULT, NUMBER_DEFAULT, and DATE_DEFAULT — Type-specific default values used when a value is not explicitly supplied.
  • DISPLAY_NAME and DESCRIPTION — The translated, user-facing label and description of the attribute, sourced from the translation table for the session language.
  • ATTACH — The attachment indicator associated with the attribute.

Common Use Cases and Queries

Typical usage includes auditing the attributes of a specific message, generating documentation of notification content, and validating translated labels across a message. A representative query listing attributes for a given message follows:

  • SELECT MESSAGE_TYPE, MESSAGE_NAME, NAME, SEQUENCE, TYPE, VALUE_TYPE, DISPLAY_NAME, DESCRIPTION FROM APPS.WF_MESSAGE_ATTRIBUTES_VL WHERE MESSAGE_NAME = :p_message_name ORDER BY SEQUENCE;
  • SELECT NAME, DISPLAY_NAME, TEXT_DEFAULT, NUMBER_DEFAULT, DATE_DEFAULT FROM APPS.WF_MESSAGE_ATTRIBUTES_VL WHERE MESSAGE_TYPE = :p_message_type AND MESSAGE_NAME = :p_message_name;
  • SELECT COUNT(*), MESSAGE_NAME FROM APPS.WF_MESSAGE_ATTRIBUTES_VL GROUP BY MESSAGE_NAME ORDER BY 1 DESC;

Because the view filters translations to the session language, queries should be executed with the appropriate NLS language setting to obtain the intended display text.