Search Results g_custom_redo_tbl

Overview

AK_CUSTOM2_PVT is a private PL/SQL package body in the APPS schema that belongs to the Oracle Application Framework/Application Object Library "AK" family of customization utilities. It complements the public customization interfaces (AK_CUSTOM_PUB, AK_CUSTOM_PVT, and AK_ON_OBJECTS_PUB) by providing the internal implementation logic used to upload customization definitions into the E-Business Suite repository. The "CUSTOM2" designation distinguishes it as a secondary or extended upload handler, typically invoked by the customization upload process to persist the second phase of a customization load. Because it is a private (PVT) package, it is not intended to be called directly from forms or concurrent programs; instead it is consumed by the public customization APIs and the FND_LOAD_UTIL bulk-loading infrastructure. In EBS 12.1.1 and 12.2.2 the object remains VALID and is catalogued under the ETRM (E-Business Suite Technical Reference Manual) as an internal dependency of the customization framework.

Key Procedures and Functions

The ETRM metadata documents two procedures within this package body:

• UPLOAD_CUSTOM — The primary upload routine. It drives the insertion and update of customization records, coordinating the parent customization header, its translated (TL) rows, the associated regions, and region items. It calls supporting logic in AK_CUSTOM_PVT and AK_ON_OBJECTS_PVT to resolve object references before persisting the customization definition.
• UPLOAD_CUSTOM_SECOND — A secondary or follow-up upload routine. It handles the second stage of the customization load, typically completing records that depend on references created by UPLOAD_CUSTOM, such as region items, criteria, or translated descriptions that require the parent identifiers to already exist.

No parameter lists are exposed in the documented metadata; both procedures are private helpers whose signatures are internal to the customization upload API. Their existence confirms a two-pass upload strategy, where the first pass establishes headers and the second resolves and attaches dependent detail rows.

Tables Accessed

The package operates against the core customization repository tables and their translation counterparts, referenced through APPS synonyms:

• AK_CUSTOMIZATIONS and AK_CUSTOMIZATIONS_TL — the customization header and its language-specific descriptions.
• AK_CUSTOM_REGIONS and AK_CUSTOM_REGIONS_TL — customization regions and their translated names.
• AK_CUSTOM_REGION_ITEMS and AK_CUSTOM_REGION_ITEMS_TL — individual items within a region, with translated labels.
• AK_CRITERIA — criteria definitions used to scope or select the customization.
• PLITBLM — the standard PL/SQL integer table type used for bulk-bind arrays during multi-row DML, indicating set-based processing of customization rows.

Reads and writes against these tables populate the metadata that the AK runtime engine uses to render and apply customizations.

Usage Notes

AK_CUSTOM2_PVT is not invoked directly by end users. It is called from the public customization APIs and from the customization upload process, frequently exercised during patching, customization migration, or FNDLOAD-style bulk uploads of personalization and customization definitions. The package relies on FND_API, FND_MSG_PUB, and FND_LOAD_UTIL for error handling and message stacking, consistent with standard EBS API conventions. Because it is not referenced by any other database object, it represents a terminal internal layer within the AK customization stack. Developers implementing custom upload utilities should call the public API layer rather than this private package.