Search Results create_attribute_usage

Overview

PV_ATTRIBUTE_USAGE_PVT is a private PL/SQL API package owned by the APPS schema within the Oracle E-Business Suite Product Variability (PV) product family. It encapsulates the business logic that governs attribute usage records, which associate a specific attribute with the object types, contexts, or functional areas in which it is permitted to be used. Attribute usages are the mechanism by which the variability model constrains where a given attribute may be attached or applied, forming part of the validation layer for configuration and attribute assignment in Oracle EBS 12.1.1 and 12.2.2.

The package is classified as PVT, indicating that it is a private package intended to be called by other PL/SQL constructs rather than invoked directly by end users or external integrations. As declared with AUTHID CURRENT_USER, it executes with the privileges of the calling user, relying on APPS synonyms for object resolution. A record type, attribute_usage_rec_type, mirrors the columns of the underlying table and initializes every attribute to the FND_API.G_MISS_* sentinel values, so that omitted fields are treated as "not supplied" during API processing.

Key Procedures and Functions

The package exposes seven documented procedures and functions that together provide a complete maintenance and validation lifecycle for attribute usage data:

• CREATE_ATTRIBUTE_USAGE — Inserts a new attribute usage record, applying the standard create validations and populating audit columns.
• UPDATE_ATTRIBUTE_USAGE — Modifies an existing attribute usage record, typically including optimistic locking through the object version number.
• DELETE_ATTRIBUTE_USAGE — Removes an attribute usage record, subject to any dependency checks.
• LOCK_ATTRIBUTE_USAGE — Acquires a row-level lock on the attribute usage to serialize concurrent modifications.
• VALIDATE_ATTRIBUTE_USAGE — Performs validation of the supplied attribute usage data before create or update operations.
• CHECK_ATTR_USAGE_ITEMS — Checks items associated with the attribute usage, supporting integrity verification against dependent records.
• VALIDATE_ATTR_USAGE_REC — Validates the entire attribute usage record structure, including mandatory columns and referential expectations.

The presence of separate lower-level validation routines alongside the primary DML procedures reflects the standard Oracle EBS API pattern, in which validation and locking are factored out for reuse by internal and dependent APIs.

Tables Accessed

The package operates against the following documented objects, resolved through APPS synonyms:

• PV_ATTRIBUTE_USAGES — The primary transactional table holding attribute usage records; this is the target of the create, update, and delete procedures and the source for validation and locking queries.
• PV_ATTRIBUTE_USAGES_S — The corresponding sequence or shadow table used in the standard EBS API model to support identifier generation and audit tracking.
• DUAL — Used for single-row evaluations, typically for validation logic, sequencing, or environment checks.

The package's record type confirms that the primary table includes columns such as attribute_usage_id, attribute_usage_type, attribute_usage_code, attribute_id, enabled_flag, security_group_id, and the standard audit and concurrency columns (object_version_number, request_id, program_id, and program update date).

Usage Notes

Because PV_Attribute_Usage_PVT is classified as PVT, it is not intended as a public integration interface. It is invoked indirectly, most commonly from the forms and concurrent programs that maintain attribute usage definitions in the Product Variability setup, and from other PL/SQL packages that need to create, validate, or lock attribute usage records as part of a larger transaction. The metadata identifies two other packages that reference it, confirming that it participates in a layered API stack.

Custom code should generally prefer the public API layer over this private package. Where direct invocation is required, callers must set up the record type with G_MISS sentinels for any unspecified fields, observe the standard EBS error and message handling conventions, and perform all DML within the calling transaction so that validation and locking remain consistent. Callers should also supply all audit and program context columns to preserve traceability and work with the object version number for concurrent update protection.