Search Results delete_entity_attr

Overview

PV_ENTITY_ATTRIBUTE_PVT is a private PL/SQL package in the Oracle EBS Applications schema (APPS) that underpins the entity attribute framework used by Oracle's Product Visibility (PV) modules, including Quality/Questionnaire functionality. The package encapsulates the validation and maintenance logic for records stored in the PV_ENTITY_ATTRS entity attribute definitions. Entity attributes in this context describe configurable metadata about objects — the entity to which the attribute belongs, the data type (attr_data_type), the SQL text used to derive values, LOV definitions (lov_string), and behavioural flags such as enabled_flag, display_flag, locator_flag, and security_group_id. Collectively these definitions drive dynamic value resolution and list-of-values behaviour in dependent PV forms and processes.

Classified as a PVT (private) package per the ETRM metadata, it is not an officially supported public API. Its procedures and functions are intended for internal use by other PV packages and by the runtime that manages entity attribute records. The header comments (revision 120.1, dated 30-JUN-2005) confirm a long-standing, largely stable design retained through 12.1.1 and 12.2.2. The entity_attr_rec_type record mirrors the columns of PV_ENTITY_ATTRS, using Fnd_Api.G_MISS_NUM, G_MISS_DATE, and G_MISS_CHAR as sentinel defaults so callers can distinguish unspecified values from intentional NULLs — a standard Oracle API design pattern.

Key Procedures and Functions

The package exposes nine documented program units. Each addresses a specific stage of the entity attribute lifecycle:

• CREATE_ENTITY_ATTR — Inserts a new entity attribute definition, populating the audit columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login, object_version_number) and validating the supplied values before persistence.
• UPDATE_ENTITY_ATTR — Modifies an existing entity attribute record, enforcing optimistic locking via object_version_number and updating the standard WHO columns.
• DELETE_ENTITY_ATTR — Removes an entity attribute definition from the base table.
• LOCK_ENTITY_ATTR — Acquires a row-level lock on the attribute record, typically invoked before update or delete to prevent concurrent modification.
• VALIDATE_ENTITY_ATTR — Performs parameter-level validation for a single entity attribute, checking required values and business rules.
• CHECK_ENTITY_ATTR_ITEMS — Verifies the existence and integrity of dependent child items associated with an entity attribute.
• VALIDATE_ENTITY_ATTR_REC — Validates a complete record structure passed in as entity_attr_rec_type, complementing the parameter-level VALIDATE_ENTITY_ATTR.
• VALIDATE_SQL_TEXT — Confirms that the SQL text stored for an attribute (sql_text) is syntactically valid and executable; the package references DBMS_SQL for this dynamic validation.
• VALIDATE_LOV_STRING — Validates the list-of-values definition stored in lov_string, ensuring the LOV specification is well-formed before it is used by dependent forms.

Tables Accessed

The package operates against the PV schema's entity attribute tables through APPS synonyms:

• PV_ENTITY_ATTRS — The primary base table holding entity attribute definitions; the target of CREATE, UPDATE, and DELETE operations and the source for LOCK and VALIDATE routines.
• PV_ENTITY_ATTRS_S — The corresponding translation/seed table, typically accessed during validation to confirm attribute existence.
• PV_ENTY_ATTR_VALUES — Stores the values resolved for entity attributes; referenced by CHECK_ENTITY_ATTR_ITEMS and validation logic to assess dependencies before deletion or modification.
• PV_GE_QSNR_ELEMENTS_B — The base table linking questionnaire elements to entity attributes, checked to ensure attributes are not removed while referenced by questionnaire definitions.
• DBMS_SQL and DUAL — Used for dynamic SQL validation (VALIDATE_SQL_TEXT) and for lightweight existence or sequence checks.

Usage Notes

Because PV_ENTITY_ATTRIBUTE_PVT is a private package, it should not be called directly from customer extensions; the ETRM metadata records that it is referenced by two other APPS packages, which serve as the internal callers. In practice, entity attribute maintenance is invoked through the Product Visibility setup forms (for example, questionnaire and quality setup screens) where users create or modify attribute definitions, and the form's underlying library or PL/SQL calls these procedures. Batch or concurrent processes that import or synchronise attribute definitions may also invoke the package indirectly.

For custom development on 12.1.1 or 12.2.2, the recommended approach is to use the public APIs of the calling packages rather than PV_ENTITY_ATTRIBUTE_PVT, since the private package signature may change without notice. Developers tracing the "create_entity_attr" operation should follow the call stack upward from this package to the supported entry point, and should preserve the G_MISS sentinel conventions and object_version_number handling when passing record structures.