Results for “max_value_flag”

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

Overview

PV_ATTRIBUTES_B is the base table in the Oracle E-Business Suite Partner Management (PV) module that stores partner attribute identifier definitions. It holds the master list of configurable attributes that can be assigned to partners, partner entities, and related partner structures. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the definitional anchor for the attribute framework used throughout Partner Management, controlling how partner data elements are typed, validated, displayed, and exposed to external partner systems.

From a Data Vault modeling perspective, the metadata classifies PV_ATTRIBUTES_B as hub-leaning. This classification is a heuristic suggestion derived from its foreign key structure: the table carries its own surrogate primary key (ATTRIBUTE_ID) and is referenced by numerous dependent tables, while itself referencing only a security group table. Such a position is characteristic of a hub entity—a stable, business-independent list of attribute keys—though the presence of descriptive columns such as ATTRIBUTE_TYPE, DISPLAY_STYLE, and SEEDED_FLAG means it also carries satellite-like descriptive content.

Key Information Stored

The table contains 26 documented columns. The most significant are:

• ATTRIBUTE_ID — The surrogate primary key (PV_ATTRIBUTES_B_PK) that uniquely identifies each partner attribute.
• ATTRIBUTE_TYPE — Defines the data type or classification of the attribute, governing how values are interpreted.
• ATTRIBUTE_CATEGORY — Groups attributes into logical categories for organization and filtering.
• ENABLED_FLAG — Indicates whether the attribute is active and available for use.
• SEEDED_FLAG — Distinguishes Oracle-seeded attributes from customer-defined ones.
• LOV_FUNCTION_NAME — Identifies the list-of-values function used to populate selectable values.
• RETURN_TYPE and VALUE_EXTN_RETURN_TYPE — Control the value returned for the attribute and its extensibility behavior.
• DISPLAY_STYLE — Dictates how the attribute is rendered in the user interface.
• EXPOSE_TO_PARTNER_FLAG — Determines whether the attribute is visible to external partners.
• ENABLE_MATCHING_FLAG — Governs whether the attribute participates in matching logic.
• CHARACTER_WIDTH, DECIMAL_POINTS, NO_OF_LINES, MAX_VALUE_FLAG — Define formatting and sizing constraints.
• PERFORMANCE_FLAG and ADDITIVE_FLAG — Support measurement and aggregation semantics.
• SEQUENCE_NUMBER — Controls ordering of attributes.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org security.

The unique index PV_ATTRIBUTES_B_U1 spans ATTRIBUTE_ID and ZD_EDITION_NAME, making the pair a business-key candidate and confirming the table supports edition-based redefinition in 12.2.x.

Common Use Cases and Queries

Typical usage centers on listing, filtering, and validating partner attribute definitions. A common query retrieves all enabled attributes in a given category:

SELECT attribute_id, attribute_type, display_style FROM pv.pv_attributes_b WHERE enabled_flag = 'Y' AND attribute_category = :cat;

Reporting scenarios include identifying attributes exposed to partners (EXPOSE_TO_PARTNER_FLAG = 'Y') and auditing seeded versus custom attributes. Developers frequently join to the translation table for display names:

SELECT b.attribute_id, t.name FROM pv_attributes_b b JOIN pv_attributes_tl t ON b.attribute_id = t.attribute_id WHERE t.language = USERENV('LANG');

Matching configuration reports and value-set validation both rely on this table as the master reference.

Related Objects

• PV_ATTRIBUTES_TL — Translation table joining on ATTRIBUTE_ID; supplies language-specific names and descriptions.
• PV_ATTRIBUTE_CODES_B / PV_ATTRIBUTE_CODES — Define permitted code values per attribute via ATTRIBUTE_ID.
• PV_ENTITY_ATTRS — Associates attributes with partner entities on ATTRIBUTE_ID.
• PV_ENTITY_ATTR_MAPPINGS — Maps source and target attributes through SOURCE_ATTR_ID and TARGET_ATTR_ID.
• PV_ENTY_ATTR_VALUES — Stores captured attribute values keyed by ATTRIBUTE_ID.
• PV_ATTRIB_RESP_MAPPINGS — Links attributes to responsibilities via ATTRIBUTE_ID.
• PV_ENTY_SELECT_CRITERIA and PV_SEARCH_ATTR_VALUES — Support selection and search filtering on ATTRIBUTE_ID.
• PV_ATTRIBUTE_USAGES and PV_ENTITY_ATTR_TRENDS — Track attribute usage and trend data.