Oracle periodically certifies newer releases of application technology stack components to provide improved security, supportability, and access to new features. In a previous blog post, we introduced the roadmap for updating Oracle E-Business Suite (EBS) Release 12.2 to the Next Generation Technology Stack.

This is the fifth article in a series of blog articles to review and introduce new terminology and concepts for updating the Oracle E-Business Suite 12.2 Application Technology Stack to the Next Generation Technology Stack.

What is the Manifest File for the Next Gen Tech Stack for EBS 12.2?

The manifest file is an inventory of your EBS Release 12.2 environment that you plan to update from the Classic Tech Stack to the Next Gen Tech Stack. Creating the manifest file for the technology stack update is similar to the process used to create a manifest when performing EBS platform migrations. For more information, see KA1125, Application Tier Platform Migration with Oracle E-Business Suite Release 12.2.

The manifest file includes information about the files and codelevels in your EBS environment. You generate the manifest file by running the manifest utility, adgentsu.pl. After it is generated, you upload the manifest file to My Oracle Support. Oracle uses the information in your manifest file to create a Next Gen Tech Stack migration patch that is specific to your EBS environment.

For additional information, see: FAQ: Oracle E-Business Suite Next Generation Technology Stack (MOS Article KA1014)

What’s Next in this Blog Series?

The sixth article in this series explains the migration patch that Oracle creates specifically for your EBS environment. You’ll also learn how the migration patch is applied during the update to the Next Generation Technology Stack.

References

Related Articles