Results for “number_default”

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

Overview

WF_MESSAGE_ATTRIBUTES is a core Oracle Workflow repository table owned by the APPLSYS schema and delivered under the FND (Application Object Library) product in Oracle EBS 12.1.1 and 12.2.2. It stores the individual attribute definitions that belong to each message defined in the Workflow message dictionary. Every Workflow message, such as a notification or an error message, is composed of one or more named attributes; this table persists the metadata that governs those attributes, including their sequence, type, default values, and access controls.

From a Data Vault modeling perspective, the documented foreign key structure classifies this object as satellite-leaning. Its composite key of MESSAGE_TYPE, MESSAGE_NAME, and NAME positions the row as a dependent descriptor of a parent message rather than as an independent business entity, so the table is best modelled as a satellite hanging off the WF_MESSAGES hub and the message-attribute link, with the sequence and formatting columns acting as non-key descriptive payload. Note that the status of this object is VALID, confirming it is an active, supported dictionary table.

Key Information Stored

Each row describes a single attribute of a single message. The documented physical schema in 12.2.2 contains 18 columns. The most significant are:

• MESSAGE_TYPE – the message type that owns the attribute; part of the primary key and the foreign key to WF_MESSAGES.
• MESSAGE_NAME – the specific message within that type; also part of the primary key.
• NAME – the attribute name; the third component of the primary key and the token replaced in message text.
• SEQUENCE – ordering position of the attribute, used as a business-key candidate in WF_MESSAGE_ATTRIBUTES_U2.
• TYPE and SUBTYPE – the attribute's declared data type and further sub-typing.
• VALUE_TYPE – the value domain semantics of the attribute.
• PROTECT_LEVEL and CUSTOM_LEVEL – protection and customization control levels governing whether customers may override the definition.
• FORMAT – the display format applied when the attribute value is rendered.
• TEXT_DEFAULT, NUMBER_DEFAULT, and DATE_DEFAULT – type-specific default values used when no runtime value is supplied.
• ATTACH, RENDER, and SECURITY_GROUP_ID – attachment handling, rendering behavior, and the security group scoping the attribute.
• CUSTOMIZATION_LEVEL and ZD_EDITION_NAME – customization tracking and the edition name used for editioning support in 12.2.2.

The surrogate primary key is WF_MESSAGE_ATTRIBUTES_PK over MESSAGE_TYPE, MESSAGE_NAME, and NAME (with ZD_EDITION_NAME in the editioned index). The documented business-key candidate WF_MESSAGE_ATTRIBUTES_U2 covers MESSAGE_TYPE, MESSAGE_NAME, SEQUENCE, and ZD_EDITION_NAME, enforcing a unique ordering per message.

Common Use Cases and Queries

Because the user searched on wf_message_attributes_pk, the most common query pattern is a direct lookup by full primary key to retrieve the definition of a single attribute:

• SELECT name, sequence, type, value_type, format, text_default, number_default FROM wf_message_attributes WHERE message_type = :p_type AND message_name = :p_name ORDER BY sequence;
• Reporting all attributes that have a non-null default, to audit default value provisioning.
• Identifying attributes whose PROTECT_LEVEL or CUSTOM_LEVEL permit customer customization, supporting upgrade impact analysis.
• Joining to WF_MESSAGE_ATTRIBUTES_TL on MESSAGE_TYPE, MESSAGE_NAME, and NAME to obtain translated attribute text.

Related Objects

• WF_MESSAGES – joined on MESSAGE_TYPE and MESSAGE_NAME; the parent message definition.
• WF_MESSAGE_ATTRIBUTES_TL – the translation table, joined on MESSAGE_TYPE, MESSAGE_NAME, and NAME.
• FND_SECURITY_GROUPS – joined via SECURITY_GROUP_ID to scope attribute visibility.
• WF_MESSAGE_ATTRIBUTES_PK – the primary key index supporting point lookups.
• WF_MESSAGE_ATTRIBUTES_U2 – the unique business-key index enforcing sequence ordering.