Search Results validate_attr_usage_rec

Overview

APPS.PV_ATTRIBUTE_USAGE_PVT_W is the public wrapper package for the attribute usage private API layer in Oracle EBS. It belongs to the Product Information Management / Advanced Product Catalog family of modules (the "PV" namespace) and exists to expose the attribute usage private business logic to external callers. In Oracle EBS, the "_PVT_W" suffix denotes a public wrapper around an internal private package (in this case PV_ATTRIBUTE_USAGE_PVT). The wrapper pattern separates the stable public interface from the private implementation, allowing Oracle to evolve internal logic without breaking callers that depend on the documented signature.

The package governs the lifecycle of attribute usage records, which join attributes to the entities that consume them (such as item catalogs, categories, or structures). It provides the standard PL/SQL API envelope — API version, initialization of the message list, commit control, and validation level — and follows the OAF/BC4J "Rosetta" table-copy convention used throughout EBS for passing tabular data between Java middle-tier code and PL/SQL.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P2 / ROSETTA_TABLE_COPY_OUT_P2 — Bulk data marshalling routines. These convert between a PL/SQL collection type (attribute_usage_tbl_type, defined in PV_ATTRIBUTE_USAGE_PVT) and the JTF_*_TABLE types used by the Java/OAF layer. The "in" variant unpacks JTF tables into the private record structure; the "out" variant performs the reverse. Both are typically invoked by the framework, not by end users.
• CREATE_ATTRIBUTE_USAGE — Creates a new attribute usage record, returning the generated ID and standard return status, message count, and message data outputs.
• UPDATE_ATTRIBUTE_USAGE — Modifies an existing attribute usage record.
• VALIDATE_ATTRIBUTE_USAGE — Performs entity-level validation of an attribute usage record prior to insert or update.
• CHECK_ATTR_USAGE_ITEMS — Checks the item-level associations tied to an attribute usage record.
• VALIDATE_ATTR_USAGE_REC — The record-level validation routine most commonly referenced by developers; it validates a single attribute usage record and populates the message stack on failure.

All business methods follow the EBS API standard: p_api_version_number, p_init_msg_list, p_commit, p_validation_level, x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

The documented table reference is via the APPS synonym PLITBLM, an EBS internal table used in the context of item and attribute processing. Attribute usage records themselves are held in the PV attribute usage base table accessed through the private package. Direct DML is confined to the private layer; the wrapper delegates all persistence through PV_ATTRIBUTE_USAGE_PVT.

Usage Notes

This package is invoked indirectly. It is not called by any other documented package (referenced by 0 packages), which indicates it is a leaf-level API reached from the OAF/BC4J middle tier or from custom PL/SQL that follows the EBS API conventions. Typical triggers include the attribute administration UI in the Advanced Product Catalog setup, bulk attribute maintenance, and custom inbound interfaces that create or amend attribute usage assignments. Developers calling it must initialize the message list, check x_return_status after every call, and release the message stack with FND_MSG_PUB when x_msg_count exceeds zero. Because it is a public wrapper, callers should treat the signature as stable across 12.1.1 and 12.2.2, while avoiding reliance on the underlying private package.