Results for “attribute_id”

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

Overview

PV_ENTITY_ATTR_VAL_V is a read-only database view owned by the APPS schema within the PV (Partner Management) product family of Oracle E-Business Suite. It presents attribute values assigned to partner entities, joining stored attribute-value records to the attribute definitions that describe them. The view exposes both the technical attribute identifier and the corresponding descriptive name and description, which is why it is frequently referenced in searches for "attr_description" and related descriptive metadata.

In the ETRM documentation for release 12.2.2, the object is registered with a status of VALID under the APPS schema. Its primary role is to supply partner attribute assignments in a denormalized, reporting-friendly form for SQL-based inquiry, concurrent programs, and integration extracts without requiring callers to join the value and definition tables themselves. Because it surfaces the human-readable attribute descriptions alongside the values, the view is well suited to operational reporting and troubleshooting of partner configuration data.

Underlying Base Objects

The view is defined over two documented objects:

• PV_ENTY_ATTR_VALUES (SYNONYM) — the transactional store of attribute values linked to a specific partner entity.
• PV_ATTRIBUTES_VL (VIEW) — the attribute definition view supplying names and descriptions in the session language.

The relationship is a simple equijoin on ATTRIBUTE_ID, so each row of the underlying attribute-value record is combined with the matching attribute definition. In the view text, table aliases A and B refer to PV_ENTY_ATTR_VALUES and PV_ATTRIBUTES_VL respectively. Because PV_ATTRIBUTES_VL is itself a view, attribute name and description columns are resolved through its translated (VL) structure, which means descriptive text returned by this view is language-sensitive.

Key Columns

• ENTY_ATTR_VAL_ID — unique identifier for the attribute-value row.
• ENTITY / ENTITY_ID — the partner entity type and its identifier, identifying the party to which the attribute value is attached.
• ATTRIBUTE_ID — foreign key to the attribute definition.
• ATTR_NAME — the attribute's name, sourced from PV_ATTRIBUTES_VL (column NAME in the underlying definition).
• ATTR_DESCRIPTION — the descriptive text of the attribute, sourced from PV_ATTRIBUTES_VL. This is the column most often sought when users search for "attr_description."
• ENABLED_FLAG — indicates whether the attribute value is active.
• SCORE — a numeric weighting or scoring value associated with the attribute-value record.
• ATTR_VALUE — the stored attribute value itself.

Common Use Cases and Queries

Typical uses include reporting all attributes and their descriptions for a given partner, filtering to enabled values, or extracting scored attribute values for integration. A representative query follows:

• SELECT enty_attr_val_id, entity, entity_id, attr_name, attr_description, attr_value, score FROM apps.pv_entity_attr_val_v WHERE entity_id = :entity_id AND enabled_flag = 'Y' ORDER BY attr_name;
• SELECT attr_name, attr_description, COUNT(*) FROM apps.pv_entity_attr_val_v GROUP BY attr_name, attr_description; — to inventory attribute usage.

Because the view is owned by APPS, callers should reference it as APPS.PV_ENTITY_ATTR_VAL_V or rely on the standard APPS synonym, and should be mindful that descriptive columns reflect the session language through PV_ATTRIBUTES_VL.