Search Results date_default

Overview

OKC_LAUNCH_WFRESP_ATTR_V is a documented Oracle E-Business Suite view owned by the APPS schema and defined in the OKC (Contracts Core) product. It exposes the full set of message attributes associated with Workflow notifications generated by the Contracts Launch process, resolving both the notification-specific attribute values (held in WF_NOTIFICATION_ATTRIBUTES) and the message-level attribute definitions (held in WF_MESSAGE_ATTRIBUTES and its translatable counterpart WF_MESSAGE_ATTRIBUTES_TL). The view has a status of VALID in ETRM and is available across EBS 12.1.1 and 12.2.2.

Because it joins the notification, notification-attribute, message-attribute, and translated-message-attribute entities in one query, the view can serve as a convenient reporting surface. It is frequently relevant when investigating the contents of a workflow message raised during contract launch, particularly when the message name is registered in WF_MESSAGE_ATTRIBUTES and a translated display name must be obtained. The user query wf_message_attributes_tl points directly to the translation table referenced by this view, confirming the intended interpretive context.

Underlying Base Objects

The view is defined over four documented objects, all referenced via APPS synonyms:

• WF_MESSAGE_ATTRIBUTES (SYNONYM) — message attribute definitions for a given message type/name and attribute name.
• WF_MESSAGE_ATTRIBUTES_TL (SYNONYM) — translatable text (e.g., display names) for the message attributes, joined on message type, message name, and attribute name.
• WF_NOTIFICATIONS (SYNONYM) — the actual notification instance, providing NOTIFICATION_ID, MESSAGE_TYPE, and MESSAGE_NAME.
• WF_NOTIFICATION_ATTRIBUTES (SYNONYM) — the per-notification attribute values entered at runtime, joined on NOTIFICATION_ID and NAME.

The join path is: WF_NOTIFICATIONS to WF_NOTIFICATION_ATTRIBUTES on NOTIFICATION_ID; from there to WF_MESSAGE_ATTRIBUTES on MESSAGE_TYPE, MESSAGE_NAME, and NAME; and finally to WF_MESSAGE_ATTRIBUTES_TL using the same three attribute keys. This structure is documented explicitly in the view text as amended under APPS.

Key Columns

The view exposes the following columns as documented in the ETRM metadata:

• NOTIFICATION_ID — identifier of the workflow notification instance.
• MESSAGE_TYPE, MESSAGE_NAME — the workflow message definition identifiers.
• NAME — the internal attribute name (from WF_NOTIFICATION_ATTRIBUTES.NAME).
• DISPLAY_NAME — the translatable, human-readable label of the attribute (from WF_MESSAGE_ATTRIBUTES_TL).
• TYPE, SUBTYPE — the data type and any subtype of the attribute definition.
• FORMAT — the attribute format (also aliased as ENTERED_VALUE in the view text).
• TEXT_DEFAULT, NUMBER_DEFAULT, DATE_DEFAULT — the default values defined for text, number, and date attributes respectively.
• ENTERED_VALUE — the runtime value entered for the notification attribute (implemented as an alias of FORMAT in the documented view text).

Common Use Cases and Queries

Typical usage includes auditing the attributes carried by a Contracts Launch workflow response, verifying that message-attribute definitions align with what the notification supplies, and producing localized reports that display attribute labels in the session language. A representative query follows:

SELECT NOTIFICATION_ID,
       MESSAGE_TYPE,
       MESSAGE_NAME,
       NAME,
       DISPLAY_NAME,
       TYPE,
       ENTERED_VALUE
FROM   APPS.OKC_LAUNCH_WFRESP_ATTR_V
WHERE  NOTIFICATION_ID = :p_notification_id
ORDER  BY NAME;

A second pattern joins back to WF_NOTIFICATIONS to scope results to a specific contract-launch message name:

SELECT v.NAME,
       v.DISPLAY_NAME,
       v.ENTERED_VALUE
FROM   APPS.OKC_LAUNCH_WFRESP_ATTR_V v
WHERE  v.MESSAGE_NAME = :p_message_name
AND    v.MESSAGE_TYPE = :p_message_type;

Because the view depends on WF_MESSAGE_ATTRIBUTES_TL, results honor the translation row available for the requested attribute, which is the reason callers searching on wf_message_attributes_tl arrive at this view. All access should be granted through the APPS synonym in accordance with standard EBS schema conventions.