Search Results upload_custom

Overview

AK_CUSTOM2_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Application Framework customization and personalization infrastructure implemented by the AK (Application Kit) core modules team. Its principal business function is to load customization definitions from a loader file into the EBS database, enabling administrators and developers to migrate personalizations, customizations, and their associated region-level definitions between environments. The package operates as the second-stage loader companion to the public API surface defined in AK_CUSTOM_PUB, and it is deliberately classified as PVT (private), meaning it is intended for invocation only by other AK-owned APIs rather than by customer or third-party code directly.

The header comment confirms that this API should only be called by other APIs owned by the Core Modules Team (AK). It reads customization data—including region items—stored in a loader file currently being processed, parses that data, and applies it to the database with a caller-supplied timestamp. Processing terminates at end-of-file, upon encountering a parse error, or when data for a different business object is read from the loader file. The package declares global constant G_PKG_NAME for messaging routines and several global PL/SQL tables used to hold records requiring a second processing pass during upload.

Key Procedures and Functions

• UPLOAD_CUSTOM — The primary private API for loading customizations from a loader file into the database. It processes customization data and region items from the file identified by an index, parses the content, and writes records using the timestamp passed by the caller. It returns the standard p_return_status indicating Unexpected error, Error, or Success. Parameters include an IN OUT index of the PL/SQL file to be processed, a required IN loader timestamp used when creating or updating records, and an optional IN line number reference.
• UPLOAD_CUSTOM_SECOND — A companion routine that performs the second pass over the records accumulated in the package-level redo tables. Because certain customizations and region items reference rows that must already exist, those records are held in G_CUSTOM_REDO_TBL, G_CUST_REGION_REDO_TBL, G_CUST_REG_ITEM_REDO_TBL, and G_CRITERIA_REDO_TBL during the first pass, with corresponding index pointers, and are resolved during the second pass.

Tables Accessed

The package reads and writes the core AK customization tables through APPS synonyms:

• AK_CUSTOMIZATIONS and AK_CUSTOMIZATIONS_TL — base and translated customization definition rows.
• AK_CUSTOM_REGIONS and AK_CUSTOM_REGIONS_TL — region-level customization metadata and translations.
• AK_CUSTOM_REGION_ITEMS and AK_CUSTOM_REGION_ITEMS_TL — item-level customization metadata and translations.
• AK_CRITERIA — criteria records associated with customizations, managed through the criteria redo table.
• PLITBLM — the PL/SQL file utility buffer used to read and parse the loader file contents.

These accesses support loading, translating, and resolving dependencies among customization definitions during the two-pass upload process.

Usage Notes

AK_CUSTOM2_PVT is not invoked directly from forms or concurrent programs. It is called by the AK public API layer—specifically by one other referenced package—as part of the customization upload workflow triggered when administrators load a personalization or customization loader file. The package's AUTHID CURRENT_USER declaration means it executes with the privileges of the calling schema. The lookup term "upload_custom" corresponds directly to the UPLOAD_CUSTOM procedure, which is the documented entry point most often searched for when diagnosing loader-file import behavior in Oracle EBS 12.1.1 and 12.2.2. Because it is a private package, it should not be invoked from custom code; any diagnostic or functional work should be directed through the owning public APIs.