Search Results pv_attribute_pvt




Overview
Explore in AI Chat

Overview

PV_ATTRIBUTE_PVT is the private application programming interface for attribute definitions within the Oracle EBS Product Lifecycle Management (PLM) schema, specifically the PV (Product Vision/Product Information Management) product family. The package encapsulates the business logic governing the creation, maintenance, validation, and deletion of attribute records stored in the PV_ATTRIBUTES_B, PV_ATTRIBUTES_B_S, and PV_ATTRIBUTES_TL tables. These attributes describe the configurable data elements used throughout product information management, including catalog attributes, search criteria attributes, and attributes exposed to trading partners.

The package follows Oracle's canonical PL/SQL API architecture: the _PVT (Private) classification indicates that the procedures are intended to be wrapped by a corresponding public API, typically PV_ATTRIBUTE_PUB. The header comment records a version stamp of pvxvatss.pls 120.0, dated 2005/05/27, indicating the object originated in the 11i codebase and was carried forward into 12.1.1 and 12.2.2 without structural change. A package-level constant, G_DEFAULT_NUM_REC_FETCH, set to 30, controls the default bulk-fetch size for record retrieval operations.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within the package. Their purposes are as follows:

  • CREATE_ATTRIBUTE — Inserts a new attribute definition, populating the base table, the translation table where applicable, and any dependent mapping rows.
  • UPDATE_ATTRIBUTE — Modifies an existing attribute definition and propagates changes to related tables and reference entities.
  • DELETE_ATTRIBUTE — Removes an attribute definition, subject to the package's internal integrity checks against usages and entity associations.
  • LOCK_ATTRIBUTE — Acquires a row-level lock on an attribute record to serialize concurrent modification attempts.
  • VALIDATE_ATTRIBUTE — Verifies that a supplied attribute record satisfies the business rules required for creation or update, including required fields, data types, and category validity.
  • CHECK_ATTRIBUTE_ITEMS — Validates the dependent child items associated with an attribute, such as usage rows and entity attribute mappings.
  • VALIDATE_ATTRIBUTE_REC — Performs record-level validation directly against the attribute_rec_type structure.

The attribute_rec_type Record

The searched term, attribute_rec_type, refers to the package-defined PL/SQL record that mirrors the columns of PV_ATTRIBUTES_B. The header comment enumerates its fields, including attribute_id, the audit columns (last_update_date, last_updated_by, creation_date, created_by, last_update_login, object_version_number), and functional columns such as enabled_flag, attribute_type, attribute_category, seeded_flag, lov_function_name, return_type, max_value_flag, name, description, short_name, display_style, character_width, decimal_points, no_of_lines, expose_to_partner_flag, value_extn_return_type, enable_matching_flag, performance_flag, additive_flag, and sequence_number. Every field is initialized to the corresponding FND_API.G_MISS_* sentinel, implementing the standard Oracle API convention that distinguishes "not supplied" from "set to null."

Tables Accessed

  • PV_ATTRIBUTES_B / _B_S — The base and secondary (surrogate-key or language-independent) tables holding core attribute definitions.
  • PV_ATTRIBUTES_TL — The translation table for language-specific name, description, and short_name values.
  • PV_ATTRIBUTE_USAGES — Records the contexts in which an attribute is used; consulted during validation and delete checks.
  • PV_ATTRIB_RESP_MAPPINGS — Maps attributes to responsibilities for access control.
  • PV_ENTITY_ATTRS and PV_ENTY_ATTR_VALUES — Link attributes to product entities and hold entity-specific attribute values.
  • PV_ENTY_SELECT_CRITERIA — Stores search criteria definitions that reference attributes.
  • DUAL — Used for single-row queries such as sequence and default retrieval.

Usage Notes

PV_ATTRIBUTE_PVT is not intended for direct invocation by customer code. It is called by the public wrapper PV_ATTRIBUTE_PUB, by attribute administration forms in the Product Information Management responsibility, and by concurrent programs that seed or migrate attribute definitions. One other documented package references it. Customizations that must create or modify attributes should invoke the public API so that validation, locking, and translation handling remain consistent across 12.1.1 and 12.2.2.