Search Results pv_itype_attr_maps_uk1

Overview

The table PV_ITYPE_ATTR_MAPS is a core data entity within the Oracle E-Business Suite Partner Management (PV) module. It serves as a mapping or junction table that establishes a formal relationship between Interest Types, defined in the Application Foundation (AS) layer, and specific Attribute Codes within the Partner Management system. This mapping is fundamental for configuring and managing partner profiles, as it dictates which custom attributes are applicable and can be captured for a given partner interest classification. The table's existence enables a flexible and extensible data model where attributes are not hard-coded to interest types but are instead managed through configurable associations.

Key Information Stored

The table's primary purpose is to store the unique associations between an Interest Type and an Attribute Code. Its structure is defined by two key foreign key columns and a system-generated primary key. The column INTEREST_TYPE_ID references a valid interest type from the AS_INTEREST_TYPES_B table. The column ATTR_CODE_ID references a specific attribute definition stored in the PV_ATTRIBUTE_CODES table. The system uses the ITYPE_MAP_ID column as the primary key (PV_ITYPE_ATTR_MAPS_PK) to uniquely identify each mapping record. The uniqueness of the ATTR_CODE_ID is enforced by the alternate key constraint PV_ITYPE_ATTR_MAPS_UK1, indicating that a given attribute code can typically be mapped to only one interest type.

Common Use Cases and Queries

This table is central to operations involving the setup and validation of partner interest attributes. A primary use case is during the configuration of partner profiles, where administrators define which attributes (e.g., "Annual Revenue Band," "Target Industry") are available for a partner categorized with a specific interest type like "Reseller" or "Technology Partner." For reporting and data validation, common SQL queries involve joining this map to the related master tables to list all attributes for a type or to validate data entry. A typical query pattern would be:

• SELECT it.interest_type_name, ac.attr_code, ac.description
• FROM pv_itype_attr_maps map,
• as_interest_types_b it,
• pv_attribute_codes ac
• WHERE map.interest_type_id = it.interest_type_id
• AND map.attr_code_id = ac.attr_code_id
• AND it.interest_type_name = 'Reseller';

Related Objects

PV_ITYPE_ATTR_MAPS is a dependent object that sits at the intersection of two key master tables, forming critical foreign key relationships. It directly references the AS_INTEREST_TYPES_B table via the column INTEREST_TYPE_ID. This links partner management functionality to the foundational interest type taxonomy used across EBS. Secondly, it references the PV_ATTRIBUTE_CODES table via the column ATTR_CODE_ID. This ties the mapping to the specific library of configurable attributes within the Partner Management module. These relationships ensure referential integrity, meaning an attribute cannot be mapped to a non-existent interest type or attribute code.