Search Results pv_enty_attr_values_u1

Overview

PV.PV_ENTY_ATTR_VALUES is a transactional table in the Oracle E-Business Suite Channel Revenue Management (formerly Trade Management) schema, PV. Its documented purpose is to store transaction-level partner and lead additional attribute information — that is, the extended, often customer-defined descriptive values attached to a partner or lead entity within a trade management transaction. The table resides in the APPS_TS_TX_DATA tablespace, which is the standard transactional data tablespace for EBS, confirming its role as a high-volume operational data store rather than a setup or reference table.

In Oracle EBS 12.1.1 and 12.2.2, the object is documented as VALID with FND Design Data registration under PV.PV_ENTY_ATTR_VALUES. The ETRM metadata classifies this object heuristically as a link in a Data Vault modeling sense. This classification reflects the table's structural role: it connects independent hubs (attributes, entities, validations, security groups) through foreign keys while also carrying descriptive, versioned payload columns such as ATTR_VALUE, SCORE, and ATTR_VALUE_EXTN. In practice, this means it can be modeled either as a link with attached descriptive attributes or as a link-and-satellite pair, depending on whether the attribute values are treated as immutable business keys or as time-variant descriptive data. The presence of VERSION, LATEST_FLAG, and OBJECT_VERSION_NUMBER strongly supports the satellite interpretation for the descriptive columns.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• ENTY_ATTR_VAL_ID — NUMBER(15), the surrogate primary key and the column behind the unique index PV_ENTY_ATTR_VALUES_U1. This is the only documented business-key candidate and the primary join key for child references.
• ENTITY — VARCHAR2(50), the entity type discriminator that determines whether the row applies to a partner or a lead.
• ENTITY_ID — NUMBER(15), the identifier of the partner or lead, depending on ENTITY. It is the principal business foreign key to both HZ_PARTIES and AS_LEADS_ALL.
• ATTRIBUTE_ID — NUMBER(15), the attribute definition being populated, linking to PV_ATTRIBUTES_B.
• ATTR_VALUE — VARCHAR2(2000), the partner expertise or attribute value itself, the primary descriptive payload.
• ATTR_VALUE_EXTN — VARCHAR2(4000), overflow storage for attribute values that exceed the base column.
• SCORE — VARCHAR2(30), a score measuring partner expertise associated with the value.
• VALIDATION_ID — NUMBER(15), the validation rule applied, referencing PV_ENTY_ATTR_VALIDATIONS.
• VERSION and LATEST_FLAG — versioning controls; LATEST_FLAG holds 'Y' when the row is the current value.
• ENABLED_FLAG — indicates whether the partner attribute value is active.
• SECURITY_GROUP_ID — the security group that owns the row, referencing FND_SECURITY_GROUPS.
• PARTY_ID — NUMBER(15), documented as obsolete; retained for backward compatibility only.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, plus OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

The dominant access pattern is retrieval of the current enabled attribute values for a given partner or lead. A typical query filters on ENTITY, ENTITY_ID, and LATEST_FLAG:

• SELECT attribute_id, attr_value, attr_value_extn, score FROM pv.pv_enty_attr_values WHERE entity = :entity AND entity_id = :id AND latest_flag = 'Y' AND enabled_flag = 'Y';
• Joining to PV_ATTRIBUTES_B to resolve attribute names for reporting: SELECT a.attribute_name, v.attr_value FROM pv.pv_enty_attr_values v, pv.pv_attributes_b a WHERE v.attribute_id = a.attribute_id AND v.entity_id = :id.
• Version history inspection using the VERSION column ordered descending for a given entity and attribute pair.
• Validation-driven reporting by grouping on VALIDATION_ID to identify attribute values that passed or failed specific rules.

The nonunique indexes N1 through N4 (on PARTY_ID, ATTRIBUTE_ID, ENTITY_ID plus ATTRIBUTE_ID plus ENTITY, and VALIDATION_ID respectively) map directly to these access paths and should be considered when tuning extracts or concurrent program queries.

Related Objects

The table participates in the following documented relationships:

• PV_ATTRIBUTES_B — referenced via ATTRIBUTE_ID; supplies the attribute definition and metadata.
• PV_ENTY_ATTR_VALIDATIONS — referenced via VALIDATION_ID; defines the validation rules applied to values.
• HZ_PARTIES — referenced via ENTITY_ID for partner-typed rows; provides party master data.
• AS_LEADS_ALL — referenced via ENTITY_ID for lead-typed rows; provides lead master data.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for multi-org security partitioning.
• PV_ENTY_ATTR_VALUES_U1 — the unique index on ENTY_ATTR_VAL_ID that enforces the surrogate key and supports direct row lookups.