Results for “jtf_brm_wf_attr_v”

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

Overview

The APPS.JTF_BRM_WF_ATTR_V view is a CRM Foundation (JTF) database object exposed under the APPS schema. Its documented purpose is to support the Business Rule Workbench form, presenting workflow activity attribute definitions alongside any configured attribute values so that the form can render and maintain business rule parameters. The view joins workflow attribute metadata from the Oracle Workflow dictionary with CRM-specific value rows, producing a denormalized, form-friendly result set.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view functions primarily as a presentation and integration layer rather than a transactional store. It is not intended for high-volume reporting but is frequently encountered by technical consultants when investigating how Business Rule Workbench (BRM) configurations map to underlying Workflow activity attributes such as ACTIVITY_ITEM_TYPE. Because the object name exposes ACTIVITY_ITEM_TYPE as a key column, it is a common target for searches attempting to trace how an item type participates in business rule processing.

Underlying Base Objects

The ETRM metadata documents four referenced objects. WF_ACTIVITY_ATTRIBUTES_VL is the Workflow dictionary view supplying activity attribute definitions; the inline subquery restricts it to the maximum ACTIVITY_VERSION per ACTIVITY_ITEM_TYPE and ACTIVITY_NAME, so only the latest attribute definitions are returned. JTF_BRM_WF_ATTR_VALUES is a synonym holding the CRM-side attribute value rows. FND_LOOKUP_VALUES is joined through the lookup type JTF_BRM_WF_ITEM_TYPE, filtered by USERENV('LANG'), ensuring only valid item types are exposed. JTF_BRM_UTILITY_PVT is a PL/SQL package whose ATTRIBUTE_FORMAT function formats the resolved value for display.

The view text is a UNION ALL: the first branch returns attributes that have saved value rows; the second returns attribute definitions with NULL value identifiers, representing attributes not yet configured. This union guarantees the form shows every attribute, whether or not a value exists.

Key Columns

• ROW_ID — the underlying ROWID of the attribute definition, used by the form for row identification.
• WF_ATTR_VALUE_ID and WF_PROCESS_ID — identifiers for the saved value and its process; both NULL in the unconfigured branch.
• WF_ITEM_TYPE — populated from WAL.ACTIVITY_ITEM_TYPE, the workflow item type.
• WF_PROCESS_NAME and WF_PROCESS_VERSION — the activity name and its version.
• WF_ATTRIBUTE_NAME, WF_ATTRIBUTE_DISPLAY_NAME, WF_ATTRIBUTE_DESCRIPTION — attribute identity and labels.
• WF_ATTRIBUTE_TYPE and WF_ATTRIBUTE_FORMAT — the datatype and formatting directive.
• WF_ATTRIBUTE_VALUE — the formatted value derived via JTF_BRM_UTILITY_PVT.ATTRIBUTE_FORMAT, falling back to the type-appropriate default when no stored value exists.
• TEXT_VALUE, NUMBER_VALUE, DATE_VALUE — the raw typed values.

Common Use Cases and Queries

Typical uses include diagnosing why a Business Rule Workbench attribute renders with a default rather than a stored value, and auditing which attributes are configured for a given item type. The following query lists attributes for a specific item type:

• SELECT WF_ITEM_TYPE, WF_PROCESS_NAME, WF_ATTRIBUTE_NAME, WF_ATTRIBUTE_VALUE FROM APPS.JTF_BRM_WF_ATTR_V WHERE WF_ITEM_TYPE = :item_type ORDER BY WF_PROCESS_NAME, WF_ATTRIBUTE_NAME;
• SELECT WF_ITEM_TYPE, WF_ATTRIBUTE_NAME FROM APPS.JTF_BRM_WF_ATTR_V WHERE WF_ATTR_VALUE_ID IS NULL; — isolates unconfigured attributes (the UNION ALL second branch).

Because the view already restricts to the maximum activity version and validates item types against JTF_BRM_WF_ITEM_TYPE, it should be preferred over direct queries against WF_ACTIVITY_ATTRIBUTES_VL when reproducing Workbench behavior.