Search Results ak_on_objects_pvt




Overview
Explore in AI Chat

Overview

AK_ON_OBJECTS_PVT is an internal (PVT) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It operates within the Application Object Library / Application Kit (AK) product family, which provides the metadata-driven infrastructure used by Oracle Forms-based and HTML-based applications for loading, downloading, uploading, and validating object definitions. The package serves as the private implementation layer behind the public AK_ON_OBJECTS_PUB interface, supporting bulk object import and export utilities, token-based parsing of loader files, and validation of reference data such as application identifiers, lookup codes, and Yes/No flags.

The ETRM metadata classifies the object as an API of type PVT, and confirms its status as VALID. It is documented with fourteen procedures and functions and is referenced by twenty-seven other packages, indicating that it is a foundational helper unit invoked across the AK object-management toolchain rather than a directly consumable public API.

Key Procedures and Functions

  • APPEND_BUFFER_TABLES — Appends buffered loader data into the in-memory table structures used during the upload and download process.
  • DOWNLOAD_HEADER — Writes the header portion of a downloaded object definition file.
  • GET_TOKEN — Retrieves the next token from a loader line during parsing of upload and download files.
  • READ_LINE — Reads a line from the loader file or buffer for subsequent tokenization.
  • REPLACE_SPECIAL_CHAR — Substitutes special or reserved characters so that data survives file round-tripping.
  • SET_WHO — Populates the standard WHO audit columns (created by, creation date, last updated by, last update date) on records being inserted or updated.
  • IS_UPDATEABLE — Determines whether a given object or record is eligible for update, guarding the upload logic.
  • UPLOAD — Executes the core upload of object definitions from loader files into the AK object tables.
  • VALID_APPLICATION_ID — Validates that a supplied application identifier exists and is active.
  • VALID_LOOKUP_CODE — Validates a lookup code against the AK lookup repository.
  • VALID_YES_NO — Validates that a value conforms to the standard Yes/No domain.
  • WRITE_FILE — Writes the generated object definition content to an output file.
  • WRITE_LOG_FILE — Writes diagnostic and error messages to the loader log file.
  • WRITE_TO_TABLE — Persists parsed records into the target AK staging or definition tables.

Tables Accessed

The package accesses AK_LOADER_TEMP for temporary storage of records during upload and download processing, and AK_LOOKUP_CODES when validating lookup values. FND_APPLICATION and the FND_APPLICATION_VL view are queried by the application-validation routines, while DUAL serves as the standard single-row source for syntactic validations. PLITBLM is used as the PL/SQL table type backing the buffered line collections, and V$PARAMETER is consulted for database-level configuration. The dependency listing additionally shows compile-time references to FND_API, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, FND_LOAD_UTIL, and AD_ZD_SEED, as well as the sibling AK packages AK_AMPARAM_REGISTRY_PVT, AK_ATTRIBUTE_PVT, AK_CUSTOM2_PVT, AK_DOWNLOAD_GRP, AK_FLOW2_PVT, AK_OBJECT2_PVT, AK_OBJECT3_PVT, AK_ON_OBJECTS_PUB, AK_QUERYOBJ_PVT, AK_REGION2_PVT, AK_SECURITY_PVT, and AK_UPLOAD_GRP.

Usage Notes

AK_ON_OBJECTS_PVT is not intended to be called directly by end users or customer extensions; it is invoked indirectly through AK_ON_OBJECTS_PUB and the AK object download/upload infrastructure, typically driven from the Application Object Library administration forms or the corresponding concurrent programs that generate and load object definition files. Because the package writes to loader files and staging tables and relies on FND_MSG_PUB for error propagation, any custom invocation must follow the standard FND_API error-handling pattern. Oracle's documented dependency information confirms that no database object references this package directly, underscoring its role as an internal implementation detail of the AK object management subsystem in both EBS 12.1.1 and 12.2.2.