Search Results check_attr_code_items

Overview

PV_ATTRIBUTE_CODE_PVT_W is a private PL/SQL wrapper package belonging to the APPS schema that supports the attribute code infrastructure of Oracle Product Lifecycle Management / Product Data Management (formerly part of the Advanced Product Catalog and Product Information Management family). Attribute codes represent the extensible descriptive elements defined against product catalog items, and this package provides the programmatic interface through which those attribute code definitions are created, validated, and maintained. The object is classified as an "OTHER" API within the ETRM repository, indicating that it is an internal implementation package rather than a publicly published interface. The "_PVT_W" suffix follows the Oracle EBS convention for a private wrapper layer that sits between the public API surface and the underlying PL/SQL business logic, and it typically performs the thin "Rosetta" table conversion work required by the Java/TCA integration layers that expose these procedures as web services or concurrent batch operations.

Key Procedures and Functions

ETRM documents seven procedures in this package.

• ROSETTA_TABLE_COPY_IN_P2 — Converts a set of parallel JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_300 collections into a single PL/SQL parameter of type pv_attribute_code_pvt.attribute_code_tbl_type. This is the inbound half of the Java-to-PL/SQL collection marshalling mechanism used by the EBS integration framework.
• ROSETTA_TABLE_COPY_OUT_P2 — Performs the inverse operation, unpacking the attribute_code_tbl_type record structure back into the individual JTF typed collection arrays so that calling layers can consume the results as scalar table types.
• CREATE_ATTRIBUTE_CODE — The primary creation routine. It accepts the standard Oracle API preamble (API version, message list initialization, commit flag, validation level) and returns the standard return status, message count, and message data, together with the newly generated attribute code identifier. A trailing series of attribute-specific parameters carries the individual column values, defaulting to the standard FND_API.G_MISS constants when not supplied.
• UPDATE_ATTRIBUTE_CODE — The counterpart to creation, following the identical Oracle API parameter convention and updating an existing attribute code definition.
• VALIDATE_ATTRIBUTE_CODE — Validates a single attribute code record against the business rules governing attribute code definitions before persistence.
• CHECK_ATTR_CODE_ITEMS — The procedure associated with the user's search term. It performs the item-level check associated with an attribute code, verifying the relationship between the attribute code and the item assignments that reference it. This is typically used to guard against the deletion or modification of an attribute code that is still in use by catalog items, or to confirm that the items attached to the code satisfy the required validation conditions.
• VALIDATE_ATTR_CODE_REC — Performs record-level validation of an attribute code row, providing the lower-level validation invoked by the create and update routines.

Tables Accessed

The only table documented in the ETRM metadata as referenced through an APPS synonym is PLITBLM, an EBS technical infrastructure table used by the Multi-Lingual / translated-attribute support framework. Access to this table supports the translation and item-description integration aspects of attribute code processing. The attribute code data itself is persisted through the underlying pv_attribute_code_pvt layer, which this wrapper delegates to.

Usage Notes

Because this is a private wrapper (_PVT_W) rather than a public API, it is not intended for direct invocation by customer extensions. It is called by the generated Java entity/bean layer that exposes attribute code maintenance to the Product Information Management and Product Workbench forms, and by concurrent or batch processes that load attribute code definitions. The Rosetta copy procedures are invoked exclusively by the framework's table-conversion machinery. Custom code requiring attribute code creation or validation should call the public attribute code API rather than this package. ETRM records zero dependent packages, reinforcing its role as a leaf-level wrapper. The package is present in both EBS 12.1.1 and 12.2.2; the 12.2.2 online patching model does not alter its interface but requires that any custom invocation be edition-aware.