Search Results ak_object_pvt




Overview
Explore in AI Chat

Overview

APPS.AK_OBJECT_PUB is a public API package within the Oracle Application Object Library (AK) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The AK schema objects collectively implement the extensible attributes and descriptive flexfield metadata registry that underpins the EBS "object" model — the internal representation of application entities that may carry flexfield definitions, region assignments, and attribute groupings. AK_OBJECT_PUB is classified as a public (PUB) API in the ETRM metadata, indicating that its procedures are intended for invocation by other AK packages and, potentially, by customer-written extensions that need to interact with the object registry in a supported manner.

In the context of the search term "ak_object_grp," AK_OBJECT_PUB is most relevant as a dependency: the dashboard documentation records that AK_OBJECT_PUB is referenced by AK_OBJECT_GRP, the object-group maintenance package, as well as by AK_OBJECT2_PVT, AK_OBJECT3_PVT, AK_OBJECT_PVT, AK_REGION_PVT, AK_DELETE_GRP, and AK_DOWNLOAD_GRP. This dependency graph places AK_OBJECT_PUB at the foundation of the object definition and grouping infrastructure, with the object-group packages consuming its services rather than the reverse.

Key Procedures and Functions

The documented ETRM metadata for this package lists zero published procedures or functions. The repository entry contains only the package specification and package body references with no enumerated subprograms, which means no individual API signatures are formally catalogued for this release. Because no parameter lists are documented, no signatures are reproduced here. Based on the naming convention and the referencing packages, AK_OBJECT_PUB would be expected to expose routines for object-level insert, update, delete, and validation operations consumed by the AK_OBJECT_PVT and AK_OBJECT_GRP layers. Any custom development should treat the actual package specification in the target instance as authoritative and should not assume a stable interface, since PUB classification in AK does not imply the same support commitment as an Oracle-standard open interface.

Tables Accessed

The documented dependency information for AK_OBJECT_PUB shows only a reference to SYS.STANDARD, the Oracle-supplied PL/SQL standard package that provides core language constructs such as TO_CHAR and TO_DATE. No application tables are enumerated in the ETRM extract, and no APPS synonyms are recorded as directly referenced by this package. In practice, the AK object registry is persisted in tables such as AK_OBJECTS and its related attribute and region-assignment tables, but because the metadata does not confirm any specific table dependency, the precise set of tables read or written by AK_OBJECT_PUB cannot be asserted from the documentation alone. DBAs and developers should confirm actual table usage through ALL_DEPENDENCIES or by reviewing the package body source in the target environment.

Usage Notes

AK_OBJECT_PUB is not exposed as a standalone concurrent program or form-level entry point. It is invoked indirectly through the AK packages that depend on it. When an administrator or a setup routine creates, modifies, or removes an object grouping — for example via AK_OBJECT_GRP or the delete and download utilities AK_DELETE_GRP and AK_DOWNLOAD_GRP — the call chain passes through AK_OBJECT_PUB. Similarly, the private object-layer packages AK_OBJECT_PVT, AK_OBJECT2_PVT, and AK_OBJECT3_PVT, together with AK_REGION_PVT, rely on it during normal processing of object and region metadata.

  • Direct calls from custom code should be avoided unless the package specification has been reviewed in the specific release; behavior may differ between 12.1.1 and 12.2.2.
  • Because the package is referenced by core AK internals, changes to its signature would have a broad blast radius across object maintenance, deletion, and download flows.
  • For troubleshooting object-group defects, review the dependency chain from AK_OBJECT_GRP downward rather than attempting to invoke AK_OBJECT_PUB in isolation.
  • Always validate against the live data dictionary, since ETRM documents this package with only dependency-level detail and no published subprogram inventory.