Search Results create_attribute_code

Overview

PV_ATTRIBUTE_CODE_PVT is a private PL/SQL package in the APPS schema that encapsulates the business logic for managing attribute codes within the Oracle E-Business Suite Partner/Vendor (PV) module — the channel and partner management foundation used by Oracle Channel Revenue Management (formerly Oracle Trade Management). Attribute codes are the configurable, user-defined classifications that describe partner programs, partner enrollments, and related entities. By centralizing create, update, delete, lock, and validation operations in a single private package, the PV module enforces consistent data rules across every entry point — Oracle Forms, concurrent programs, and the public API layer.

As a Private (PVT) API, the package is not intended for direct use by external or customer-written code; instead it is invoked by its public wrappers (PV_ATTRIBUTE_CODE_PVT_W and PV_ATTRIBUTE_PVT) and internal callers. This layering follows the standard EBS API architecture: the PVT package holds the unguarded implementation, while the _W wrapper exposes a versioned public interface with standardized exception handling and message tokens.

Key Procedures and Functions

The package exposes seven documented entry points:

• CREATE_ATTRIBUTE_CODE — Inserts a new attribute code definition, including its descriptive flexfield and multi-lingual (MLS) translated rows, into the base and translation tables.
• UPDATE_ATTRIBUTE_CODE — Modifies an existing attribute code's descriptive attributes, status, or associated values in the _B/_S tables.
• DELETE_ATTRIBUTE_CODE — Logically or physically removes an attribute code, after verifying that no referential dependencies (usages, selected values, or entity attribute values) remain.
• LOCK_ATTRIBUTE_CODE — Obtains a concurrency lock on the attribute code record (typically via SELECT ... FOR UPDATE) to serialize conflicting create/update/delete operations.
• VALIDATE_ATTRIBUTE_CODE — Performs the mandatory-column and business-rule validation that must pass before a create or update commits, raising standard API errors on failure.
• CHECK_ATTR_CODE_ITEMS — Tests whether an attribute code currently has associated items (usages or values) that would block deletion or that dictate dependent processing.
• VALIDATE_ATTR_CODE_REC — Validates an entire attribute code record structure, invoked as a reusable validation routine by the wrapper and by PV_ATTRIBUTE_PVT.

Tables Accessed

The package reads and writes the following tables and synonyms:

• PV_ATTRIBUTE_CODES_B / PV_ATTRIBUTE_CODES_S — Base and translation tables that store the attribute code definitions themselves.
• PV_ATTRIBUTE_USAGES — Tracks where each attribute code is applied, used for dependency checks in delete and lock logic.
• PV_ENTY_ATTR_VALUES and PV_SELECTED_ATTR_VALUES — Entity-level and selected attribute values populated from the code definitions.
• PV_ENTY_SELECT_CRITERIA — Selection criteria that drive which attribute values are auto-populated.
• PV_PARTNER_PROGRAM_TYPE_B and PV_PROGRAM_PARTNER_TYPES — Relationship tables associating attribute codes with partner and program types.
• DUAL — Used for PL/SQL initialization and simple existence checks.

Usage Notes

Because PV_ATTRIBUTE_CODE_PVT is a private API, it is normally invoked indirectly. The public wrapper PV_ATTRIBUTE_CODE_PVT_W exposes the supported interface, while PV_ATTRIBUTE_PVT and other PV packages call the PVT procedures directly to share core validation and persistence logic. Typical invocation paths include:

• Oracle EBS Forms in the Partner/Channel Management responsibilities, which call the _W wrapper when users define or maintain attribute codes.
• Concurrent programs and data-conversion routines that bulk-load attribute code data during implementation.
• Internal PV package code (for example, PV_ATTRIBUTE_PVT) that creates or validates codes as part of enrollment and program setup.

Custom code should always call the _W wrapper rather than this private package to preserve upgrade compatibility and standard error handling. Direct calls risk breakage if internal signatures change between EBS 12.1.1 and 12.2.2 maintenance levels.