Search Results update_row_seed

Overview

PV_ATTRIBUTE_CODE_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It provides the application programming interface for the attribute code entity used by Oracle Product Lifecycle Management and related Product Information Management modules. Attribute codes represent the discrete permissible values associated with an attribute definition, and the package encapsulates the insert, update, delete, lock, translation, and bulk loading operations required to maintain them. The package header carries the identifier pvxtatcs.pls 120.2, dated 2005/07/05, and is classified as an OTHER API under ETRM. It follows the standard Oracle EBS multi-language table pattern, pairing a base table with a translation table and exposing seed-data entry points alongside the runtime row handlers.

Key Procedures and Functions

The package exposes nine documented entry points, each with a defined role in the attribute code lifecycle:

• INSERT_ROW — Creates a new attribute code record. It accepts the identifier and object version number as IN OUT NOCOPY parameters so the caller receives generated values back, and accepts the attribute code, audit columns, parent attribute identifier, enabled flag, and description.
• UPDATE_ROW — Modifies an existing attribute code. Creation audit parameters default to FND_API.g_miss_date and FND_API.g_miss_num, signalling that untouched creation metadata should be preserved.
• UPDATE_ROW_SEED — The seed-data variant of UPDATE_ROW, used when applying seed rows rather than end-user updates. This is the procedure most frequently referenced in support and troubleshooting searches, because it is invoked during patching and seed data synchronization rather than through normal form activity.
• DELETE_ROW — Removes an attribute code identified by its primary key.
• LOCK_ROW — Performs the standard EBS optimistic locking check, validating that the supplied column values still match the persisted row so concurrent modifications are detected.
• ADD_LANGUAGE — Registers or refreshes the translation-language rows for the entity, following the common EBS language installation routine.
• TRANSLATE_ROW — Writes a translated description for an existing attribute code in a specific language.
• LOAD_ROW — Bulk loads a single attribute code row, typically for data migration or seed population.
• LOAD_SEED_ROW — Bulk loads a seed attribute code row, the companion to UPDATE_ROW_SEED.

Tables Accessed

The package operates against three tables referenced through APPS synonyms:

• PV_ATTRIBUTE_CODES_B — The base table holding the attribute code identifier, code, parent attribute, enabled flag, description, and standard WHO audit and object version columns. This is the primary insert, update, delete, and lock target.
• PV_ATTRIBUTE_CODES_TL — The translation table storing language-specific description text, written by TRANSLATE_ROW, ADD_LANGUAGE, and the seed loading routines.
• FND_LANGUAGES — The Oracle Application Object Library language repository, consulted during language installation and translation processing to validate installed and active languages.

Usage Notes

PV_ATTRIBUTE_CODE_PKG is an internal API rather than a public, supported integration surface. It is invoked by the Oracle Forms-based attribute code maintenance screens, by concurrent programs and patch drivers that load or refresh seed data, and by the single package documented as referencing it. Because it is classified as OTHER and is not published as a public API, custom code should avoid calling it directly; supported extension paths in EBS 12.1.1 and 12.2.2 are the open interfaces and business events exposed for the surrounding Product Information Management flows. When diagnosing failures such as an error raised from UPDATE_ROW_SEED, the practical guidance is to confirm that the referenced attribute code identifier exists in PV_ATTRIBUTE_CODES_B, that the row is not locked by a competing session, and that the object version number supplied matches the stored value. The absence of version-specific overrides for 12.2.2 indicates the package's behavior is consistent across both releases.