Results for “pv_enty_attr_values_v”

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

Overview

PV_ENTY_ATTR_VALUES_V is a view owned by the APPS schema within the PV (Partner Management) product family of Oracle E-Business Suite. It presents entity attribute values that describe and score parties tracked by the partner management subsystem. The view exposes the full set of attribute assignments associated with partner entities, together with scoring information and enabled/disabled status indicators. In the context of Oracle EBS 12.1.1 and 12.2.2, the object is registered in the ETRM as a VALID view, indicating that it is a supported reference object for reporting and integration purposes.

Because the view is defined directly over a single base entity rather than a join of multiple tables, it functions as a denormalized presentation layer that shields consumers from the underlying storage. It is commonly used in partner qualification, attribute-based scoring, and entity enrichment scenarios, and it is frequently referenced by concurrent programs, OBIEE/BI Publisher reports, and custom integrations that need to read partner attribute values without touching the base table directly.

Underlying Base Objects

The view is defined exclusively over the synonym PV_ENTY_ATTR_VALUES, which resolves to the base table of the same name in the APPS schema. The documented view text is a straight projection:

• SELECT ENTY_ATTR_VAL_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, ENTITY, ATTRIBUTE_ID, PARTY_ID, ATTR_VALUE, SCORE, ENABLED_FLAG, ENTITY_ID FROM PV_ENTY_ATTR_VALUES

No joins, filters, or aggregations are applied. As a result, row cardinality in the view is identical to that of the base table, and all DML performed on the base table is immediately visible through the view. The naming convention with the _V suffix reflects Oracle's standard practice of exposing a read-oriented view over a base entity, and the presence of OBJECT_VERSION_NUMBER and the WHO audit columns confirms that the underlying table participates in Oracle's standard concurrent and audit framework.

Key Columns

• ENTY_ATTR_VAL_ID — Primary key surrogate for each entity attribute value record. This is the identifier users typically search for when tracing a specific attribute assignment.
• ENTITY — The entity type or classification the attribute value belongs to, distinguishing groups of partner attributes.
• ENTITY_ID — Identifier of the specific entity instance to which the attribute value applies.
• ATTRIBUTE_ID — Foreign reference to the attribute definition being populated.
• PARTY_ID — The trading partner or party associated with the attribute value, linking the record to the TCA party model.
• ATTR_VALUE — The actual value captured for the attribute.
• SCORE — Numeric score assigned to the attribute value, used in partner ranking and qualification logic.
• ENABLED_FLAG — Indicates whether the record is currently active.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard Oracle who-column auditing and optimistic locking support.

Common Use Cases and Queries

The view supports partner attribute lookups, scoring analysis, and data extraction feeds. A typical retrieval by identifier is:

• SELECT enty_attr_val_id, entity, entity_id, party_id, attribute_id, attr_value, score, enabled_flag FROM apps.pv_enty_attr_values_v WHERE enty_attr_val_id = :p_id;

To list all active attribute values for a given party:

• SELECT attribute_id, attr_value, score FROM apps.pv_enty_attr_values_v WHERE party_id = :p_party_id AND enabled_flag = 'Y' ORDER BY score DESC;

For scoring analysis across entities:

• SELECT entity, entity_id, SUM(score) total_score FROM apps.pv_enty_attr_values_v WHERE enabled_flag = 'Y' GROUP BY entity, entity_id ORDER BY total_score DESC;

Because the view carries audit and version columns, it is also suitable for incremental extraction into downstream data warehouses, using LAST_UPDATE_DATE as the high-water mark. All queries should be executed against the APPS schema or a synonym owned by the connecting schema, honoring the standard EBS access and responsibility model.