Results for “attribute_to_value”

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

Overview

PV_SELECTED_ATTR_VALUES is a transactional table in the PV (Partner Management) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It stores the attribute values that are defined for mapping operations within partner management. In the Partner Management data model, mapping definitions determine how incoming partner or entity data is interpreted, matched, or transformed; the rows in PV_SELECTED_ATTR_VALUES hold the concrete attribute values used by those mapping decisions. Each row belongs to a selection criterion, which establishes the context in which the attribute value is applied.

Mined from the foreign key structure, the table exhibits a satellite-leaning Data Vault classification. As a modeling suggestion, this implies the table primarily captures descriptive, time-variant attribute data attached to a parent business entity — here the selection criterion — rather than acting as a hub of unique business keys or a pure link resolving many-to-many relationships. The presence of standard WHO columns, request/program audit columns, and the ZD_EDITION_NAME column reinforces an auditable, descriptive pattern.

Key Information Stored

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

• ATTR_VALUE_ID — the surrogate primary key, defined by the PV_SELECTED_ATTR_VALUES_PK constraint. This is also the leading column of the unique index PV_SELECTED_ATTR_VALUES_U1 (ATTR_VALUE_ID, ZD_EDITION_NAME), which serves as the business-key candidate.
• SELECTION_CRITERIA_ID — the foreign key to PV_ENTY_SELECT_CRITERIA, identifying the selection criterion to which the attribute value belongs. This is the central relationship linking the satellite rows to their parent entity.
• ATTRIBUTE_VALUE — the actual value assigned to the attribute for mapping purposes.
• ATTRIBUTE_TO_VALUE — the target value or mapped destination associated with the attribute.
• ATTRIBUTE_CATEGORY — the descriptive category under which the attribute is classified.
• SCORE — a numeric scoring value used in matching or ranking evaluations.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access control.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF framework for concurrent update control.
• ZD_EDITION_NAME — editioning column supporting Online Patching in 12.2.2.
• The ATTRIBUTE1–ATTRIBUTE15 descriptive flexfield columns, and the audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE for concurrent-program traceability.

Common Use Cases and Queries

Typical reporting retrieves all attribute values for a given selection criterion, or identifies scoring thresholds used in partner matching. A representative query is:

• SELECT s.attribute_value, s.attribute_to_value, s.attribute_category, s.score FROM pv_selected_attr_values s WHERE s.selection_criteria_id = :criteria_id;
• Joining to the parent to see the criterion context: SELECT c.criteria_name, s.attribute_value, s.score FROM pv_selected_attr_values s, pv_enty_select_criteria c WHERE s.selection_criteria_id = c.selection_criteria_id;
• Security-group-filtered extracts restricted via s.security_group_id = :security_group_id.

These queries support partner mapping audits, troubleshooting of match results, and validation of configured attribute-to-value mappings before production deployment.

Related Objects

• PV_ENTY_SELECT_CRITERIA — parent table referenced through PV_SELECTED_ATTR_VALUES.SELECTION_CRITERIA_ID; the primary dependency.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for access control partitioning.
• PV_SELECTED_ATTR_VALUES_PK — primary key constraint on ATTR_VALUE_ID.
• PV_SELECTED_ATTR_VALUES_U1 — unique index on (ATTR_VALUE_ID, ZD_EDITION_NAME), the edition-aware business key.
• Related PV Partner Management mapping and entity-matching tables that consume selection criteria and attribute values operate in the same functional area and are commonly queried alongside this table.