Search Results validate_attribute_usage

Overview

The APPS.PV_ATTRIBUTE_USAGE_PVT package body is a private Application Programming Interface (API) within the Oracle E-Business Suite Process Manufacturing (OPM) product family. Its classification as a PVT package (private) indicates that it is not intended to be called directly by external custom code. Instead, it serves as the internal implementation layer for the attribute usage entity, which governs how product and quality attributes are applied and associated across OPM business objects. Attribute usages define the relationships between attribute definitions and the records that consume them, and this package encapsulates the transactional logic required to create, maintain, validate, and lock those associations. Being a private body, it is typically invoked through a public wrapper or an entity handler rather than from a form directly. The object is documented as VALID in both the 12.1.1 and 12.2.2 releases of the ETRM metadata.

Key Procedures and Functions

The package exposes seven documented procedures and functions that collectively implement the lifecycle of an attribute usage record:

• CREATE_ATTRIBUTE_USAGE — Inserts a new attribute usage association, initializing the record with the supplied attribute relationship details.
• UPDATE_ATTRIBUTE_USAGE — Modifies an existing attribute usage record, applying changes to its maintained columns.
• DELETE_ATTRIBUTE_USAGE — Removes an attribute usage, either physically or logically depending on the underlying entity configuration.
• LOCK_ATTRIBUTE_USAGE — Places a lock on the record, preventing concurrent modification during transactional processing.
• VALIDATE_ATTRIBUTE_USAGE — Performs entity-level validation to confirm that the usage record is internally consistent and permissible.
• CHECK_ATTR_USAGE_ITEMS — Verifies the individual item components or child rows that make up an attribute usage, returning or acting on the result.
• VALIDATE_ATTR_USAGE_REC — Validates a complete attribute usage record, likely aggregating checks prior to a commit operation.

As private procedures, these routines are consumed by the OPM attribute usage entity infrastructure and are not part of the supported public API surface.

Tables Accessed

The package operates against the following documented objects:

• PV_ATTRIBUTE_USAGES — The primary transactional table holding attribute usage records; the create, update, delete, and lock routines read and write here.
• PV_ATTRIBUTE_USAGES_S — The corresponding translated/secure (TL-style) table, accessed for language-dependent or secured attribute usage content.
• DUAL — Used for single-row expressions and simple value evaluations within the PL/SQL logic.

Access is performed through APPS synonyms. The package body also depends on utility and framework packages including FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, JTF_PLSQL_API, and PVX_UTILITY_PVT, which provide error handling, message stacking, environment context, and OPM utility services.

Usage Notes

Because PV_ATTRIBUTE_USAGE_PVT is a private package body, it is not invoked directly by forms, concurrent programs, or custom integrations. Its documented dependency list shows it is referenced by two other packages, which act as the public-facing callers. Customization or extension should therefore target the referencing public APIs rather than this private body, since Oracle may change private signatures without notice between 12.1.1 and 12.2.2. The package is invoked whenever attribute usage data is maintained through the OPM attribute management flows, including validation and locking stages that occur before a database commit. Developers researching this object are typically diagnosing errors surfaced through FND_MSG_PUB message stacks or tracing how attribute usage validations are enforced within the OPM data model. Direct calls should be avoided in custom code to preserve upgrade safety.