Search Results update_attribute_navigation

Overview

AK_OBJECT3_PVT is a private PL/SQL package in the APPS schema that forms part of the Oracle Application Object Library (AK) metadata repository infrastructure. The AK product family stores the definitions of application objects — such as tables, views, and their associated attributes, unique keys, and foreign keys — that drive the Oracle EBS "Diagnostics" and extensibility framework, including the Attribute Management and object definition facilities used by forms-based personalization and descriptive flexfield registration. The suffix "PVT" indicates that this is a private implementation package: it is not part of a published, externally supported API surface, but instead contains the internal logic invoked by the public and sibling packages that manipulate object definitions. AK_OBJECT3_PVT is primarily concerned with the mutation of object metadata: updating object headers, updating individual attributes and their values, and uploading complete object definitions into the AK tables. It is tightly coupled with AK_ON_OBJECTS_PUB and FND_API, the latter supplying the standard EBS API error-handling and message conventions, and it is referenced by AK_OBJECT2_PVT, AK_OBJECT_GRP, and AK_ON_OBJECTS_PVT, confirming its position as a lower-level worker package within the AK object-definition stack.

Key Procedures and Functions

The ETRM documentation records five procedures or functions in this package. Their names and purposes are as follows:

• UPDATE_OBJECT — Updates the definition of an object stored in the AK object repository, writing changes to the object header tables and their translation tables.
• UPDATE_ATTRIBUTE — Updates the definition of an individual attribute belonging to an object, modifying the attribute metadata held in the object attribute tables.
• UPDATE_ATTRIBUTE_VALUE — Updates the value associated with an attribute, supporting the storage of attribute-level data used by the object definition framework.
• UPDATE_ATTRIBUTE_NAVIGATION — Maintains attribute navigation information, which governs how attributes are traversed or linked across related objects.
• UPLOAD_OBJECT — Performs a bulk load of an object definition, inserting or refreshing the object, its attributes, keys, and related metadata as a single operation.

These routines accept parameters for the target object and attribute identifiers and rely on FND_API conventions for success and error reporting. Parameter lists are not reproduced here; callers should derive signatures from the package specification and the published AK_ON_OBJECTS_PUB interface.

Tables Accessed

The package reads and writes the core AK metadata tables through APPS synonyms. Object header data resides in AK_OBJECTS and its translated counterpart AK_OBJECTS_TL. Attribute definitions are held in AK_OBJECT_ATTRIBUTES and AK_OBJECT_ATTRIBUTES_TL, with attribute navigation stored in AK_OBJECT_ATTRIBUTE_NAVIGATION. Key metadata is maintained in AK_UNIQUE_KEYS, AK_UNIQUE_KEY_COLUMNS, AK_FOREIGN_KEYS, AK_FOREIGN_KEYS_TL, and AK_FOREIGN_KEY_COLUMNS. DBMS_SQL is referenced for dynamic SQL construction, which allows the package to build statements against object definitions that are not known at compile time. DUAL supports simple expression evaluation, and PLITBLM provides the standard EBS PL/SQL table and indexed-table types used for array processing and parameter passing.

Usage Notes

AK_OBJECT3_PVT is an internal package and is not intended for direct invocation by customer extensions. In normal EBS operation it is called indirectly through the public object-definition APIs, notably AK_ON_OBJECTS_PUB, and through its sibling private package AK_OBJECT2_PVT, both of which appear in the dependency chain. The documented dependency listing shows the package referenced by AK_OBJECT2_PVT, AK_OBJECT_GRP, AK_ON_OBJECTS_PVT, and by itself, reflecting internal recursion and reuse across the AK object family. Because the package manipulates base repository metadata, any indirect use through supported APIs should be performed only by users with the privileges required to register or modify application object definitions, and only in environments where the AK schema is not concurrently undergoing an upgrade. Custom code should depend on the public AK_ON_OBJECTS_PUB interface rather than on AK_OBJECT3_PVT directly, since the private package is subject to change without notice between EBS 12.1.1 and 12.2.2 releases.