Search Results pv_attribute_codes




Overview
Explore in AI Chat

Overview

The PV_ATTRIBUTE_CODES table is a legacy data object within the Oracle E-Business Suite (EBS) Partner Management (PV) module. Its primary historical role was to store the discrete, predefined values or codes associated with specific partner attributes, enabling standardized data entry and validation for partner profiles. This table functioned as a child table to PV_ATTRIBUTES_B, which defined the attributes themselves. Critically, the provided ETRM documentation explicitly states that this table was obsoleted for release 11.5.6 and is not implemented in the database for versions 12.1.1 and 12.2.2. Therefore, in the context of Oracle EBS 12.x, this table is a documented artifact of a prior data model and is not present or functional within the application's schema.

Key Information Stored

Based on its structure and relationships, the table was designed to hold the master list of valid values for coded partner attributes. The key columns, as indicated by the primary and foreign key definitions, would have included:

  • ATTR_CODE_ID: The primary key column, uniquely identifying each discrete attribute value record.
  • ATTRIBUTE_ID: A foreign key column linking to PV_ATTRIBUTES_B.ATTRIBUTE_ID, identifying the parent attribute for which this record is a valid code.
  • Additional columns (not specified in the provided metadata but typical for such structures) would likely have included the code value itself (e.g., CODE, VALUE), a meaning or description, and columns for enabling/disabling and ordering the codes.

Common Use Cases and Queries

As the table is obsoleted and not implemented in EBS 12.x, there are no active use cases or operational queries. In historical versions prior to 11.5.6, it would have been used to populate list-of-values (LOV) for partner attribute entry and validation. Sample query patterns from that era would have involved joining to PV_ATTRIBUTES_B to retrieve valid codes for a specific attribute name. For reporting, it would have been used to decode stored attribute code IDs into their human-readable meanings. In contemporary EBS 12.x implementations, any functionality for managing coded partner attribute values is handled through successor data models and application interfaces, not through this table.

Related Objects

The ETRM metadata defines specific relationships for this obsolete table, illustrating its intended place in the old data model:

  • Parent Table (Foreign Key Reference): PV_ATTRIBUTE_CODES.ATTRIBUTE_ID references PV_ATTRIBUTES_B. This established the link from a specific code to its governing attribute definition.
  • Child Table (Referenced by Foreign Key): PV_ITYPE_ATTR_MAPS.ATTR_CODE_ID references PV_ATTRIBUTE_CODES. This relationship suggests the codes were used to map specific attribute values to partner interaction types (ITYPE).

These relationships confirm the table's role as a central lookup or validation table within the obsolete partner attribute framework.