Results for “attr_code”

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

Overview

PV_ATTRIBUTE_CODES_B is a base table in the Partner Management (PV) product module within Oracle E-Business Suite, owning schema PV. Its documented purpose is to store partner attribute identifiers — that is, the individual code values that populate the partner attributes used to qualify, classify, and segment partners, leads, and related channel entities. The table functions as the transactional base of an attribute-code structure that is completed by a translation table (PV_ATTRIBUTE_CODES_TL) and anchored to a parent attribute definition table (PV_ATTRIBUTES_B) through the ATTRIBUTE_ID foreign key.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table carries a single-column surrogate primary key (ATTR_CODE_ID) and no foreign keys implying an associative role, so it resembles a business hub for the attribute-code entity, with its descriptive and effective-dating columns playing the role of satellite attributes. This is a heuristic suggestion only; the physical design remains a fully normalized third-normal-form EBS table with standard WHO audit columns and editioning support via ZD_EDITION_NAME.

Key Information Stored

The table contains fifteen documented columns. Among these, the most significant are:

• ATTR_CODE_ID — the surrogate primary key, enforced by PV_ATTRIBUTE_CODES_B_PK and also the leading column of the PV_ATTRIBUTE_CODES_B_U1 unique index alongside ZD_EDITION_NAME.
• ATTRIBUTE_ID — foreign key to PV_ATTRIBUTES_B, identifying the parent attribute to which the code belongs.
• ATTR_CODE — the business-meaningful code value; combined with ATTRIBUTE_ID and ZD_EDITION_NAME it forms the business-key candidate captured in the PV_ATTRIBUTE_CODES_B_U2 unique index.
• ENABLED_FLAG — controls whether the code is selectable on partner attribute entry and update screens.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating columns that bound the period during which the code is valid for assignment.
• AUTO_ASSIGN_FLAG — indicates whether the code is applied automatically during attribute processing rather than by manual selection.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Oracle Application Object Library security grouping.
• OBJECT_VERSION_NUMBER — the optimistic-locking token used by the framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit trail.
• ZD_EDITION_NAME — the editioning discriminator that allows multiple attribute-code definitions to coexist across editions.

Common Use Cases and Queries

The table is most commonly queried to resolve the set of valid attribute codes for a given attribute, typically filtered by enabled status and current effective dates. A representative reporting pattern joins the base table to its translation table to return a display name:

• SELECT b.attr_code_id, b.attr_code, t.description FROM pv_attribute_codes_b b, pv_attribute_codes_tl t WHERE b.attr_code_id = t.attr_code_id AND t.language = USERENV('LANG') AND b.enabled_flag = 'Y' AND SYSDATE BETWEEN b.start_date_active AND NVL(b.end_date_active, SYSDATE);
• Attribute code listings for a specific parent attribute: constrain on b.attribute_id = :attribute_id.
• Effective-dating audit reports that identify codes active as of a historical date.
• Downstream usage analysis by joining to PV_LEAD_PSS_LINES on ATTR_CODE_ID to find where a code has been consumed on lead records.
• Auto-assignment review queries filtering on AUTO_ASSIGN_FLAG = 'Y'.

Related Objects

The following objects are documented as directly related to PV_ATTRIBUTE_CODES_B:

• PV_ATTRIBUTES_B — parent attribute definitions; joined on ATTRIBUTE_ID.
• PV_ATTRIBUTE_CODES_TL — translations keyed by ATTR_CODE_ID.
• PV_LEAD_PSS_LINES — lead line records that reference an attribute code through ATTR_CODE_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
• PV_ATTRIBUTE_CODES_B_PK, PV_ATTRIBUTE_CODES_B_U1, and PV_ATTRIBUTE_CODES_B_U2 — the primary key and unique indexes that govern access paths and enforce uniqueness of attribute codes within an attribute and edition.