# Oracle EBS Patch Impact Analysis Checklist

> Source: https://netray.co/tools/oracle-ebs-patch-impact-analysis-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Analyse what an Oracle EBS patch will change, which customizations it touches and how you will test and roll back, before you apply it.

## Category

oracle

## Erp

Oracle E-Business Suite

## Audience

- EBS DBA
- EBS developer
- Change manager

## Tool

**Kind:** checklist

**Groups:**

#### 1. Classify the patch

**Items:**

**Text:** Identify the patch type: one-off, CPU security patch, product family pack, RUP, AD or TXK Delta, or technology stack (database, WebLogic, Forms and Reports home)

**Critical:** true

**Text:** Read the readme for prerequisites, conflicting patches, apply mode and manual steps

**Critical:** true

Check prerequisites are already applied by querying AD_BUGS for the bug numbers listed

Note whether the readme allows hotpatch on 12.2 or requires a full adop cycle

#### 2. Patch Wizard analysis

**Items:**

Patch Wizard preferences set (staging directory and patch information source) in Oracle Applications Manager

**Text:** Run Recommend/Analyze Patches for the patch and review the result

**Critical:** true

Review Patch Impact Analysis: total files, new and changed files, products affected, unapplied prerequisites

Save the impacted file list for comparison with your custom code inventory

#### 3. Customization overlap

**Items:**

**Text:** Compare impacted forms (.fmb), reports (.rdf), PL/SQL packages (.pls), OAF files and workflows (.wft) with your custom code inventory

**Critical:** true

Check CUSTOM.pll events and Forms Personalizations on forms the patch replaces

Check OAF personalizations and extensions on pages and controllers the patch changes

Check customised seeded workflows and modified seeded concurrent program definitions in affected products

List custom PL/SQL that calls seeded packages or APIs the patch replaces

#### 4. Database and online patching effects

**Items:**

Record invalid object counts before the patch to compare afterwards

Note seeded tables with DDL changes; on 12.2 confirm custom objects on editioned tables pass ADZDDBCC.sql

Estimate cutover duration and any data upgrade jobs in the readme

Check whether the patch needs AutoConfig, JAR regeneration or forms compilation afterwards

#### 5. Test plan

**Items:**

**Text:** Business flows touching each affected product identified with key users

**Critical:** true

Custom reports and extracts on affected tables run before and after, outputs compared

Inbound and outbound integrations through affected APIs and interfaces tested

Test results and sign-off recorded with the change request

#### 6. Rollback plan

**Items:**

**Text:** 12.2: an adop cycle can be abandoned with adop phase=abort before cutover, followed by cleanup and fs_clone

**Critical:** true

12.2 after cutover: plan a restore from backup or a corrective patch, because cutover is not reversed by adop

12.1: backups of APPL_TOP, technology homes and the database taken before adpatch

Restore time tested so the rollback fits the change window

**Scoring Note:** Use this before applying the patch. For the apply itself, use the adop patching checklist.

## Content

**Intro:** This checklist assesses what an Oracle E-Business Suite patch will change before you apply it: its type and prerequisites, the Patch Wizard impact analysis, overlap with your customizations, database effects, testing and rollback. It complements the adop execution checklist rather than repeating it.

**Sections:**

#### Types of EBS patches

**Body:** Not every patch carries the same risk. A one-off bug fix usually touches a handful of files in one product. A CPU security patch spans many products but rarely changes behaviour. Product family packs and RUPs change large parts of the code and data model. AD and TXK Delta packs change the patching and configuration tools themselves and go in their own cycle. Technology patches target the database, WebLogic or the Forms and Reports home and are tracked with ETCC. Classify first; the depth of analysis and testing follows from the type.

**Bullets:**

- One-off: narrow, test the fixed flow
- CPU: broad, test logins and key flows
- RUP or family pack: full regression
- AD/TXK: own cycle, patching tools change

#### Using Patch Wizard

**Body:** Patch Wizard is in Oracle Applications Manager under Patching and Utilities. Set its preferences first, including the staging directory and how it gets patch information. Recommend/Analyze Patches then analyses a specific patch against your system, and Patch Impact Analysis shows the files the patch would add or change, the products affected and prerequisites not yet applied. Patch Wizard does not run the patch; it tells you what will change so you can match it against your customizations.

#### Matching impact to your customizations

**Body:** The value of impact analysis comes from comparing the changed file list with a current custom code inventory. Customizations rarely sit inside seeded files on a well-run instance, but they depend on them: Forms Personalizations reference item names, CUSTOM.pll fires on events in seeded forms, OAF personalizations attach to page regions, and custom PL/SQL calls seeded packages. A changed seeded file can break any of these without touching your code. List each overlap and give it a specific test.

#### Rollback on 12.2 versus 12.1

**Body:** On 12.2, adop applies patches to the patch file system and edition, so until cutover you can abandon the cycle with adop phase=abort and clean up. Once cutover completes, there is no adop undo: rollback means a corrective patch or a restore from backup. On 12.1 with adpatch, changes apply directly to the running system, so take APPL_TOP and database backups first and time the restore.

**Cta:** If impact analysis on every patch takes your team days, we can build an on-prem agent that compares patch file lists with your custom code inventory and drafts the test list.

**Faq:**

#### What is Patch Wizard in Oracle EBS?

**Answer:** Patch Wizard is an Oracle Applications Manager tool that recommends and analyses patches against your EBS system. Its Patch Impact Analysis shows files the patch will add or change, affected products and missing prerequisites, so you can assess risk and plan testing before applying the patch.

#### How do I do risk analysis of a patch in Oracle EBS?

**Answer:** Classify the patch type, read the readme, run Patch Wizard impact analysis, compare changed files with your custom code inventory including personalizations, check database effects such as invalid objects and DDL, then define the tests and a rollback plan sized to your change window.

#### What types of patches are there in Oracle EBS?

**Answer:** Common types are one-off patches for specific bugs, Critical Patch Updates for security, product family packs, Release Update Packs such as 12.2.x RUPs, AD and TXK Delta packs for the patching and configuration tools, and technology stack patches for the database and middleware homes.

#### Can an EBS 12.2 patch be rolled back?

**Answer:** Before cutover, yes: adop phase=abort abandons the patching cycle, followed by cleanup and fs_clone. After cutover, adop cannot reverse the patch, so you need a corrective patch or a restore from backup. Plan which option applies and test the restore time beforehand.

## Search terms

oracle ebs patch impact analysis, risk analysis of patch in oracle ebs, oracle ebs patch analysis, oracle ebs patch wizard, types of patches in oracle ebs, ebs patch customization impact

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json