Results for “wf_attr_value_id”

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

Overview

JTF_BRM_WF_ATTR_VALUES_V is an APPS-owned database view in the JTF – CRM Foundation product, delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the Business Rule Workbench form, the configuration UI within CRM Foundation that lets administrators bind workflow process attributes to business rule conditions and actions. Rather than exposing a raw transactional table, the view presents a read-optimised, resolved picture of Workflow attribute values: it joins stored attribute value rows to the current definition of the corresponding activity attribute in the Workflow catalogue, applies display formatting, and unions in attribute definitions that have no stored value yet. This makes it a form-support view rather than a general-purpose reporting view, but it is frequently queried in EBS environments for diagnostics, migration verification and custom extensions of the Business Rule Workbench.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over four referenced objects:

• JTF_BRM_WF_ATTR_VALUES (synonym to the APPS base table) — supplies the stored attribute value rows (TEXT_VALUE, NUMBER_VALUE, DATE_VALUE) and the process/attribute keys.
• WF_ACTIVITY_ATTRIBUTES_VL (Workflow view) — supplies the attribute definition metadata: item type, activity name, version, attribute name, display name, description, type and format, together with the defaults TEXT_DEFAULT, NUMBER_DEFAULT and DATE_DEFAULT.
• FND_LOOKUP_VALUES (synonym) — filters eligible Workflow item types through the lookup type JTF_BRM_WF_ITEM_TYPE, restricted to the session language via USERENV('LANG').
• JTF_BRM_UTILITY_PVT (package) — its ATTRIBUTE_FORMAT function resolves the effective display value, preferring the stored value and falling back to the attribute default for the relevant data type.

The view text also nests a correlated subquery against WF_ACTIVITY_ATTRIBUTES_VL to select only the maximum ACTIVITY_VERSION for each item type and activity name, so that the latest attribute definition is always used. A UNION ALL branch then adds attribute definitions for which no JTF_BRM_WF_ATTR_VALUES row exists.

Key Columns

• ROW_ID — ROWID of the underlying attribute value row; used by the Workbench form for DML against the base table.
• WF_ATTR_VALUE_ID, WF_PROCESS_ID — primary key of the stored value record and the owning business rule process.
• WF_ITEM_TYPE, WF_PROCESS_NAME, WF_PROCESS_VERSION — the Workflow item type, activity name and activity version the attribute belongs to.
• WF_ATTRIBUTE_NAME, WF_ATTRIBUTE_DISPLAY_NAME, WF_ATTRIBUTE_DESCRIPTION — internal name and user-facing labels for the attribute.
• WF_ATTRIBUTE_TYPE, WF_ATTRIBUTE_FORMAT — the attribute's data type and format mask, which drive conditional display logic.
• WF_ATTRIBUTE_VALUE — the formatted, resolved value returned by JTF_BRM_UTILITY_PVT.ATTRIBUTE_FORMAT.
• TEXT_VALUE, NUMBER_VALUE, DATE_VALUE — the raw stored values by data type; DATE_VALUE is the column relevant to searches such as "date_default".

Common Use Cases and Queries

Typical uses include auditing which business rule processes reference Workflow attributes, identifying attributes that still rely on defaults rather than explicitly stored values, and validating date-typed attributes and their DATE_DEFAULT handling after an upgrade from 12.1.1 to 12.2.2.

List all attribute values for a given item type:

SELECT wf_process_name, wf_attribute_name, wf_attribute_type,
       wf_attribute_format, wf_attribute_value
FROM   apps.jtf_brm_wf_attr_values_v
WHERE  wf_item_type = :item_type
ORDER  BY wf_process_name, wf_attribute_name;

Identify date-typed attributes and inspect stored versus default values:

SELECT wf_process_name, wf_attribute_name,
       date_value, wf_attribute_value
FROM   apps.jtf_brm_wf_attr_values_v
WHERE  wf_attribute_type = 'DATE';

Find attributes with no stored value (rows contributed by the second UNION ALL branch):

SELECT wf_item_type, wf_process_name, wf_attribute_name
FROM   apps.jtf_brm_wf_attr_values_v
WHERE  wf_attr_value_id IS NULL;

Because the view performs formatting and version-resolution work in SQL, ad-hoc queries should always filter on WF_ITEM_TYPE or WF_ATTRIBUTE_TYPE to avoid a full scan of the Workflow attribute catalog.