Results for “pv_entity_attrs_u2”

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

Overview

PV_ENTITY_ATTRS is a Partner Management (PV) module table that stores the definition of entity attributes used within the Oracle E-Business Suite 12.1.1 and 12.2.2 partner and channel management data model. Each row associates a configurable attribute with a specific business entity, describing how that attribute is sourced, displayed, validated, and refreshed. The table therefore acts as a metadata catalog that drives dynamic attribute capture and questionnaire behavior across partner-related entities, rather than holding transactional partner data itself.

From a heuristic Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification. The table carries a surrogate primary key, descriptive and behavioral attributes, and foreign keys pointing to shared reference structures such as PV_ATTRIBUTES_B, which is characteristic of a satellite attached to a parent hub or link rather than a hub or link in its own right.

Key Information Stored

The table contains 31 documented columns. Its surrogate primary key is ENTITY_ATTR_ID, enforced by the PV_ENTITY_ATTRS_PK constraint. Two unique indexes act as business-key candidates: PV_ENTITY_ATTRS_U1 covers (ENTITY_ATTR_ID, ZD_EDITION_NAME), and PV_ENTITY_ATTRS_U2 covers (ATTRIBUTE_ID, ENTITY, ZD_EDITION_NAME). The most significant columns include:

• ENTITY_ATTR_ID — surrogate primary key for each entity attribute definition.
• ATTRIBUTE_ID — foreign key to PV_ATTRIBUTES_B, linking to the underlying attribute definition.
• ENTITY and ENTITY_TYPE — identify the business entity and its category to which the attribute applies.
• SRC_TABLE_NAME and SRC_PKCOL_NAME — the source table and primary-key column from which values are drawn.
• SQL_TEXT and BATCH_SQL_TEXT — SQL used for runtime and batch value derivation.
• ATTR_DATA_TYPE, LOV_STRING, ITEM_STYLE, and SELECTION_TYPE — control data type, list-of-values rendering, and UI item behavior.
• ENABLED_FLAG, DISPLAY_FLAG, LOCATOR_FLAG, AUTO_ASSIGN_FLAG, REQUIRE_VALIDATION_FLAG, and DISPLAY_EXTERNAL_VALUE_FLAG — behavioral switches governing availability, display, and validation.
• RANK — ordering of the attribute in displays.
• REFRESH_FREQUENCY, REFRESH_FREQUENCY_UOM, and LAST_REFRESH_DATE — govern scheduled refresh of derived values.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for multi-org/security partitioning (12.1.1); in 12.2.2 the ZD_EDITION_NAME column supports edition-based redefinition.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) provide audit and optimistic-locking support.

Common Use Cases and Queries

This table is commonly queried to drive dynamic attribute rendering on partner and channel UI pages, to troubleshoot why an attribute is not appearing, and to report on attribute configuration. Typical patterns include joining to PV_ATTRIBUTES_B to resolve attribute names, and filtering by ENTITY and ENABLED_FLAG to retrieve active definitions:

SELECT ea.entity_attr_id, a.attribute_name, ea.entity, ea.attr_data_type FROM pv_entity_attrs ea, pv_attributes_b a WHERE ea.attribute_id = a.attribute_id AND ea.entity = :entity AND ea.enabled_flag = 'Y' ORDER BY ea.rank;

A second frequent pattern examines refreshed attributes whose refresh interval has elapsed, using REFRESH_FREQUENCY and LAST_REFRESH_DATE. Edition-aware queries in 12.2.2 should filter on ZD_EDITION_NAME to isolate the current edition.

Related Objects

• PV_ATTRIBUTES_B — referenced via PV_ENTITY_ATTRS.ATTRIBUTE_ID; the parent attribute definition table.
• PV_GE_QSNR_ELEMENTS_B — references PV_ENTITY_ATTRS.ENTITY_ATTR_ID, binding questionnaire elements to entity attributes.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security partitioning.
• PV_ENTITY_ATTRS_PK, PV_ENTITY_ATTRS_U1, and PV_ENTITY_ATTRS_U2 — the primary-key and unique indexes enforcing integrity on ENTITY_ATTR_ID and the business-key combinations.

These relationships make PV_ENTITY_ATTRS the connective layer between the reusable attribute catalog (PV_ATTRIBUTES_B) and downstream partner questionnaire configuration (PV_GE_QSNR_ELEMENTS_B).