Search Results ad_patch_driver_langs_s

Overview

AD_PATCH_HIST_MIGR_PKG is an Oracle Applications (APPS) PL/SQL package body that supports the migration and loading of Oracle E-Business Suite patch history data into the AD patch history repository tables. Its central role is to move patch metadata — drivers, driver languages, minipacks, comprising patches, patch runs, and applied patches — from staging or legacy structures into the normalized AD dictionary tables used by AutoPatch and the patching infrastructure. The package is classified as OTHER in the ETRM 12.2.2 metadata and carries a VALID status in the APPS schema. Its scope is administrative and internal to the AD patch management layer rather than a general-purpose business API.

Key Procedures and Functions

The documented package exposes six procedures. Each is oriented toward loading a specific patch history entity or refreshing a derived view:

• LOAD_PATCH_DRIVER — Populates driver-level patch records, populating AD_PATCH_DRIVERS and its shadow table from the migration source.
• LOAD_PATCH_DRIVER_MINIPK — Loads minipack-level patch data, targeting AD_PATCH_DRIVER_MINIPKS and its shadow table.
• LOAD_PATCH_DRIVER_LANG — Loads driver language translation rows into AD_PATCH_DRIVER_LANGS and its shadow table.
• LOAD_COMPRISING_PATCH — Loads comprising patch relationships, which describe how a parent patch aggregates child patches, into AD_COMPRISING_PATCHES and its shadow table.
• LOAD_PATCH_RUN — Loads patch run execution records into AD_PATCH_RUNS and its shadow table.
• UPDATE_CURRENT_VIEW_SNAPSHOT — Refreshes the current view snapshot, likely via AD_FILE_SYS_SNAPSHOTS_PKG, to maintain currency of the patch history view layer used during migration.

Tables Accessed

The package reads and writes a broad set of AD dictionary tables through APPS synonyms. The primary targets, each with a corresponding _S shadow table for the run editions, include AD_APPLIED_PATCHES, AD_COMPRISING_PATCHES, AD_PATCH_DRIVERS, AD_PATCH_DRIVER_LANGS, AD_PATCH_DRIVER_MINIPKS, and AD_PATCH_RUNS. Supporting reference tables include AD_APPL_TOPS (applications top information), AD_BUGS (bug metadata associated with patches), and AD_RELEASES (release context), with the AD_RELEASES_PVT package invoked for release-processing logic. The staging table AD_PTCH_HST_EXE_COP_TMP serves as an intermediate work area for execution copy data. AD_FILE_SYS_SNAPSHOTS_PKG is called for the snapshot update. FND_CONCURRENT_REQUESTS_S is referenced — the shadow table of the concurrent requests repository — indicating the package records or correlates migration work against concurrent program submissions. FND_PRODUCT_GROUPS supplies product group context, and DUAL, STANDARD, and DBMS_STANDARD are used for PL/SQL plumbing. AD_PATCH_HIST_MIGR_PKG is not referenced by any other database object, confirming it is a top-level entry point rather than a subordinate library.

Usage Notes

AD_PATCH_HIST_MIGR_PKG is invoked as part of the AD patch history migration process, typically driven by AD Administration or an equivalent concurrent program that coordinates patch metadata consolidation. The reference to FND_CONCURRENT_REQUESTS_S is significant: it implies the package may be executed within a concurrent request context, allowing migration activity to be tracked alongside other concurrent jobs. It is not intended to be called directly by end users or by ordinary forms-based flows; it serves the patching subsystem. Custom code should not invoke these procedures independently, because the AD patch history tables are tightly coupled to AutoPatch and AD Administration semantics, and improper loading can corrupt the patch repository. DBAs and EBS administrators should treat this package as internal maintenance infrastructure, invoked during upgrade or migration cycles under the coordination of the AD patch management tooling.