Search Results pv_attribute_codes_b




Overview
Explore in AI Chat

Overview

The PV_ATTRIBUTE_CODES_B table is a core data object within the Oracle E-Business Suite Partner Management (PV) module, specifically in versions 12.1.1 and 12.2.2. It functions as the master repository for partner attribute codes, which are the discrete, valid values for classifying and segmenting partner entities. This table is integral to the system's partner profiling and qualification framework, enabling the definition of standardized, reusable codes for attributes such as partner tiers, certification levels, or geographic designations. Its role is to maintain the integrity and consistency of partner data by providing a controlled list of permissible values that can be assigned to partners through the related attributes structure.

Key Information Stored

The table's primary purpose is to store the unique identifiers and essential metadata for each attribute code. The key column is ATTR_CODE_ID, which serves as the system-generated primary key for each code record. A critical foreign key column is ATTRIBUTE_ID, which links the code to its parent attribute definition in the PV_ATTRIBUTES_B table, establishing which broader characteristic the code belongs to (e.g., a code of "GOLD" belongs to an attribute "TIER_LEVEL"). While the provided metadata does not list all columns, typical supporting columns in such a base table would include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY for auditing, and potentially columns like SEQUENCE_NUMBER for ordering codes and ENABLED_FLAG to control active status.

Common Use Cases and Queries

This table is central to operations involving the setup, maintenance, and reporting of partner classifications. Administrators use it to define and manage the list of available codes for partner attributes. Common reporting use cases include generating lists of all valid codes for a specific attribute to validate data entry or populate LOVs in application forms. A typical query involves joining with the translation table (PV_ATTRIBUTE_CODES_TL) to retrieve user-friendly names and with PV_ATTRIBUTES_B to understand the attribute context.

Sample SQL Pattern:
SELECT ac.ATTR_CODE_ID, ac.ATTRIBUTE_ID, act.NAME, act.DESCRIPTION
FROM PV_ATTRIBUTE_CODES_B ac,
PV_ATTRIBUTE_CODES_TL act
WHERE ac.ATTR_CODE_ID = act.ATTR_CODE_ID
AND act.LANGUAGE = USERENV('LANG')
AND ac.ATTRIBUTE_ID = :p_attribute_id;
-- This retrieves the code values and their translated meanings for a given attribute.

Related Objects

The table maintains defined relationships with several other key objects in the Partner Management schema, as documented in the ETRM metadata.

  • References (Foreign Key): The table references PV_ATTRIBUTES_B via the ATTRIBUTE_ID column. This defines the hierarchical relationship where an attribute contains multiple codes.
  • Referenced By (Primary Key):
    • PV_ATTRIBUTE_CODES_TL: Referenced via ATTR_CODE_ID. This is the translation table that stores the language-specific names and descriptions for each code stored in the base table.
    • PV_LEAD_PSS_LINES: Referenced via ATTR_CODE_ID. This indicates that attribute codes are used to classify or qualify data within the partner lead and partner sales specialist (PSS) functionality, linking partner profile data to specific business opportunities or processes.