In Part X of this blog series, we discussed identifying EBS products or features that rely on deprecated technologies and migrating to the latest supported alternatives.

As you prepare your Oracle E-Business Suite Release 12.2 environment for the Next Generation Technology Stack, it is also important to review your customizations.

The Next Generation Technology Stack updates several underlying technology components. Most of the EBS 12.2 code recompiled successfully with the later technology stack updates with little to no modification. Similarly, your customizations that depend on the existing EBS Classic Technology Stack should be identified, reviewed for compatibility, remediated as necessary and tested on Next Generation Technology Stack.

What Can I Do Now?

Customizations

Start by running the Next Gen Tech Stack Readiness Checker (Patch 38474509) on your existing EBS 12.2 environment. Next Gen Tech Stack Readiness Checker generates a customizations report, adcustlist.rpt. You can use the report to help identify your customizations and build an inventory of the associated source code.

As part of your review:

  • Identify your customizations and their source code.
  • Identify third-party libraries and vendor dependencies.
  • Review dependencies on Classic Technology Stack components.
  • Review the customization guidance in Section 1.6.9 Next Generation Technology Stack Considerations for Application Tier Customizations in Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (MOS Article KA1068).

Completing this inventory now will give you a better understanding of the customizations to be reviewed when the Next Generation Technology Stack becomes available.

Which Customizations Should I Review?

Database customizations are not affected by the application technology stack update from the Classic Technology Stack to the Next Generation Technology Stack.

The primary customizations areas to review include those developed using Forms, Reports, OA Framework, Java, C/C++/Pro*C and concurrent programs that depend on custom code deployed in the application tier. In most cases, you will be reviewing your customizations for deprecated APIs and obsolete or more strictly validated functionality.

Some key changes include:

  • Forms: Custom Forms and libraries must be recompiled for Forms 14c.
  • Reports: Custom Reports must be recompiled for Reports 14c.
  • Java: Custom Java code must be recompiled with JDK 17.
  • C/C++: Custom programs and libraries must be recompiled in 64-bit mode on Oracle Linux 8 (or Red Hat Enterprise Linux 8).

Remediate and Test

When the Next Generation Tech Stack is available, use a development environment that has already been updated to the Next Generation Technology Stack and, where necessary, remediate your customizations.

Compile your custom code, test the business flows that exercise it, and package the updated customizations for deployment to your test and production environments.

Key Takeaways

There is work you can begin today:

  • Run the Next Gen Tech Stack Readiness Checker now.
  • Build a complete inventory of your customizations and source code based upon your previous inventory of customizations and the adcustlist.rpt report.
  • Review technology-specific compatibility requirements and identify dependencies on Classic Technology.
  • Recompile and, where necessary, remediate, and test your customizations before your production update when the Next Generation Tech Stack is available.

Starting this work early will help you understand the scope of your customization changes and reduce the work when the Next Generation Technology Stack is available.

What’s Next

In Part XII of this blog series, we’ll discuss the importance of starting your Next Gen Tech Stack readiness activities now and reassessing your Oracle E-Business Suite environment after you’ve completed the applicable prerequisites.

References

Related Articles