Search Results pv_attribute_code_pvt_w




Overview
Explore in AI Chat

Overview

PV_ATTRIBUTE_CODE_PVT_W is the companion package body to the private API specification PV_ATTRIBUTE_CODE_PVT in the APPS schema. It belongs to the Oracle E-Business Suite Product Information Management / Item Master attribute framework, where "PV" denotes the product attribute value (attribute code) layer used by attribute groups, item catalog descriptive elements, and value-set driven validation. The "_W" suffix follows the standard EBS private API naming convention indicating a wrapper package that translates a generic or bulk (table-based) call interface into the single-record private API calls exposed by PV_ATTRIBUTE_CODE_PVT.

The package implements the server-side business logic required to create, update, and validate attribute codes — the discrete permissible values that populate an attribute group's value set. Its classification in ETRM is OTHER rather than a public API, which confirms that it is intended for internal invocation by the attribute framework rather than for direct customer use.

Key Procedures and Functions

  • CREATE_ATTRIBUTE_CODE — Inserts a new attribute code value, applying the framework's validation rules and defaulting logic before persistence.
  • UPDATE_ATTRIBUTE_CODE — Modifies an existing attribute code, enforcing the same validation and concurrency checks as creation.
  • VALIDATE_ATTRIBUTE_CODE — Performs the record-level validation of attribute code data prior to insert or update, returning errors through the standard FND_API error table mechanism.
  • VALIDATE_ATTR_CODE_REC — Executes the detailed validation of a single attribute code record, applying the attribute group's governing rules.
  • CHECK_ATTR_CODE_ITEMS — Determines whether an attribute code is referenced by or assigned to items, providing the referential check that controls deletion and update eligibility.
  • ROSETTA_TABLE_COPY_IN_P2 — Implements the inbound half of the Rosetta bulk data-copy pattern, mapping an externally supplied JTF collection table into the private API's working structure (the "_P2" suffix denotes the second pass of the conversion).
  • ROSETTA_TABLE_COPY_OUT_P2 — Implements the outbound half, mapping processed results back into the JTF collection tables so bulk callers receive per-row status and messages.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM, the PL/SQL identifier table used by the PL/SQL compiler and by dynamic SQL routines. Its appearance indicates that the package builds or accepts PL/SQL identifier strings — consistent with the Rosetta copy routines, which exchange data through generic structures. The remaining data structures are the JTF collection types (JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_300, JTF_NUMBER_TABLE, and JTF_DATE_TABLE) and the FND_API error/status tables, all of which are PL/SQL or API-layer objects rather than application tables. Underlying attribute code storage is handled by PV_ATTRIBUTE_CODE_PVT, which this wrapper delegates to.

Usage Notes

PV_ATTRIBUTE_CODE_PVT_W is not referenced by any other database object, confirming its role as a leaf-level implementation package. It is normally invoked indirectly: the Product Information Management attribute setup forms and the bulk attribute maintenance concurrent programs call the private API, which in turn routes through this wrapper. The Rosetta procedures support high-volume maintenance tasks where attribute codes are loaded or exported in bulk; they are invoked only by the framework's bulk-processing routines. Because ETRM classifies the package as OTHER, direct calls from custom code are unsupported and should be replaced by the corresponding public or private API entry points. The package body is schema-resident in APPS, is marked VALID, and depends on STANDARD, FND_API, and PV_ATTRIBUTE_CODE_PVT, so any customization must preserve those dependencies. In 12.1.1 and 12.2.2 the implementation is identical in structure; behavior differences arise only from changes in the underlying attribute framework.