As Oracle E-Business Suite 12.2 customers prepare for the Next Generation Technology Stack, one of the most important activities is to understand both the environment readiness and the existing customization footprint.
A useful starting point is the TSUA Readiness Check, which validates the EBS environment and, at the end of the process, gathers information about customizations.
TSUA Readiness Check
Oracle provides the p38474509_R12_GENERIC package for the TSUA readiness check.
One important point for EBS administrators:
This is not a patch that needs to be applied using OPatch or ADOP.
The package can simply be extracted, and the readiness check can be executed directly.
After extracting the package, run:
./tsua readiness
The command starts validating the EBS environment against the prerequisites required for the Next Generation Technology Stack.
The readiness process checks several important components of the environment, including the operating system, database, EBS patch levels, AD, TXK, ATG_PF and System Schema Migration status.
For example, the readiness output may identify issues such as:
ERRORMSG: OS release check.
Minimum OS release required is Oracle Linux 8.7.
ERRORMSG: Minimum Database version of 19.31 or 23.26.2 is required.
ERRORMSG: EBS CPU version check.
Minimum EBS CPU Version required is April 2026 (2026.04).
ERRORMSG: AD version check.
Minimum AD version required is delta.18.
ERRORMSG: TXK version check.
Minimum TXK version required is delta.18.
ERRORMSG: ATG_PF version check.
Minimum ATG_PF version required is Delta.14.
ERRORMSG: EBS System Schema Migration Completion Patch Check.
EBS System Schema Migration is not complete.
These messages provide a clear picture of what needs to be addressed before proceeding.
For example, the environment may need:
An operating system upgrade
Database patching
Application of the required EBS CPU
AD and TXK updates
ATG_PF updates
Completion of EBS System Schema Migration
The Important Part
The tsua readiness process does more than just validate the environment.
At the end of the readiness process, TSUA gathers information about EBS customizations and generates adcustlist.rpt.
This makes the same readiness exercise useful for both technology-stack prerequisite validation and customization discovery.
Understanding adcustlist.rpt
The adcustlist.rpt report provides visibility into the customization footprint of the EBS environment.
It categorizes the identified customizations into five sections:
SECTION-1: C Customizations
SECTION-2: Java Customizations
SECTION-3: Jsp Customizations
SECTION-4: Forms Customizations
SECTION-5: Reports Customizations
This is particularly valuable for long-running EBS environments where customizations may have accumulated over several years.
Recommended Preparation Steps
The next steps should focus on understanding the customization impact and preparing well before the production update.
Step 1 – Run the Next Gen Tech Stack Readiness Checker Now
Do not wait until the actual technology-stack migration window.
Run:
./tsua readiness
Review all readiness errors and identify the prerequisite updates required for your environment.
Step 2 – Build a Complete Customization Inventory
Build a complete inventory of your customizations and source code based on:
Your existing customization inventory
The information provided in
adcustlist.rpt
This is particularly important for older EBS environments where customizations may have been developed by different teams over many years.
Step 3 – Review Technology-Specific Compatibility
Review the compatibility requirements for each technology area and identify dependencies on the Classic Technology Stack.
Pay particular attention to:
C customizations
Java customizations
JSP customizations
Forms customizations
Reports customizations
Third-party libraries and dependencies
Step 4 – Recompile, Remediate and Test
Before the production update, recompile and, where necessary, remediate and test your customizations.
The objective should be to complete as much of this work as possible before the Next Generation Technology Stack becomes the production platform.
Why Start Early?
Starting this work early gives you time to understand the actual scope of your customization changes.
Instead of discovering a compatibility issue during the production technology-stack update, you can identify it earlier, obtain the required source code, remediate the customization, and complete functional testing.
This can significantly reduce the amount of work remaining when the Next Generation Technology Stack becomes available.
Final Takeaway
The preparation can be summarised simply:
Run TSUA → Review Readiness → Review adcustlist.rpt → Inventory Customizations → Check Compatibility → Recompile/Remediate → Test → Prepare for Production
The important point is that technology-stack readiness is not only about checking Oracle components and patch levels.
Your customization readiness is equally important.
Start early, understand what you have, identify what needs to change, and complete the remediation and testing before the production update.
The more you prepare today, the fewer surprises you will have during the Next Generation Technology Stack transition.
