Results for “attr_value”

14 results




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

Overview

PV_SEARCH_ATTR_VALUES is a Partner Management (PV) module table that stores the free-text and coded attribute values captured against trading partners during partner profile creation, qualification, and search configuration. Its documented description, "Partner Attribute Text," reflects its purpose as the repository for the attribute values that Partner Management uses to describe and match partners. Each row associates a specific partner with a specific partner attribute definition and records the value assigned to that attribute.

Under the heuristic Data Vault classification mined from its foreign key structure, PV_SEARCH_ATTR_VALUES is best modeled as a link table. The classification follows from the fact that the table resolves associations between independent entities rather than acting as a standalone hub: the PARTY_ID column points to HZ_PARTIES (the partner), and ATTRIBUTE_ID points to PV_ATTRIBUTES_B (the attribute definition). Rows therefore represent relationships between a party and an attribute, carrying descriptive text alongside the association.

Key Information Stored

The table is owned by the PV schema and comprises 13 documented columns. The most significant are:

The distinction between the surrogate key (SEARCH_ATTR_VALUES_ID) and the business-key candidates (SEARCH_ATTR_VALUES_ID in U1, and UPPER(ATTR_TEXT) in the U2/U3 unique indexes) is important for integrations and data migrations, because the case-insensitive uniqueness on ATTR_TEXT implies duplicate text values are restricted where those indexes apply.

Common Use Cases and Queries

Typical usage centers on retrieving and validating partner attribute values for search, qualification, and reporting. A common query resolves attribute values to their definitions and parties:

  • Joining PV_SEARCH_ATTR_VALUES to PV_ATTRIBUTES_B on ATTRIBUTE_ID to obtain the attribute name and description for a given value.
  • Joining to HZ_PARTIES on PARTY_ID to present attribute values alongside partner identity and organization details.
  • Filtering by UPPER(ATTR_TEXT) to perform case-insensitive lookups against the indexed business key.
  • Restricting results by SECURITY_GROUP_ID when running under a specific operating unit or security context, consistent with the FND_SECURITY_GROUPS foreign key.
  • Detecting duplicate attributes per partner by grouping on PARTY_ID and ATTRIBUTE_ID.

Reporting scenarios include partner profile reports, attribute coverage analysis (which partners have values for which attributes), and data-quality audits on missing or inconsistent ATTR_TEXT values.

Related Objects

  • HZ_PARTIES — joined on PV_SEARCH_ATTR_VALUES.PARTY_ID = HZ_PARTIES.PARTY_ID; supplies the partner identity.
  • PV_ATTRIBUTES_B — joined on PV_SEARCH_ATTR_VALUES.ATTRIBUTE_ID = PV_ATTRIBUTES_B.ATTRIBUTE_ID; supplies the attribute definition.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs record-level security.
  • PV_ATTRIBUTES_TL — the translation table for PV_ATTRIBUTES_B, providing language-specific attribute names in multilingual deployments.
  • PV_SEARCH_ATTR_VALUES_PK / _U1 / _U2 / _U3 — the primary key constraint and unique indexes that enforce identity and case-insensitive uniqueness of ATTR_TEXT.

Together these objects place PV_SEARCH_ATTR_VALUES at the intersection of partner identity and attribute configuration, making it a central, if compact, link table in Partner Management data models.