Finding Application Top ID for EBS 12.2 Patch Check

For multi-node installations, retrieving the correct `appltop_id` requires a specific SQL query . You need to join the `applsys.ad_appl_tops` table (which may contain obsolete entries) with the `applsys.fnd_appl_tops` table (which typically doesn’t have obsolete records) . The suggested query is: `select aat.name, aat.appl_top_id from applsys.ad_appl_tops aat, (select distinct fat.name from applsys.fnd_appl_tops fat) fat where aat.name = fat.name` .

The `DISTINCT` keyword is necessary because in Oracle EBS Release 12.2, the `fnd_appl_tops` table often returns two dual filesystem appl_tops . Using `DISTINCT` ensures that only one entry for each application top name is returned, simplifying the selection for the subsequent join and correct identification of the `appltop_id` .

Yes, for single-node EBS systems, you can simplify the usage of the `ad_patch.is_patch_applied` function by using the constant value `appltop_id=-1` for the second parameter . This bypasses the need to query the application top tables directly .

You modify the improved query version that selects across multiple application nodes and languages . You join `ad_bugs` and `ad_appl_tops`, and use an `IN` clause to filter by your list of patch numbers . The query would contain `where adb.bug_number in (123456, 789012)` and include the join to the filtered `ad_appl_tops` and the function call `ad_patch.is_patch_applied` to check the status for each combination .