The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

Preparing Your Customizations for EBS 12.2

Steven Chan
Senior Director

EBS 12.2 comes with Online Patching, a fresh new user interface, updated EBS product modules, and new mobile apps.  If you've customized your EBS environment or are using third-party extensions from other vendors, you'll need to ensure that they work with EBS 12.2.

EBS 12.2 New Home Page screenshot

Review the updated development standards

Coding standards, OA Framework capabilities, and, of course, database object development standards  have all been updated in EBS 12.2.  Making your extensions and customizations work with Online Patching is crucial.  Check this comprehensive guide:

Also, if you're interested in taking advantage of the latest user interface (UI) enhancements in EBS 12.2.4, check this Note:

Check your file, data model, and seed data dependencies

The following tools generate detailed reports of the differences between a specific EBS release for files, tables, and seed data. You can drill into the E-Business Suite Technical Reference Manual (eTRM) for details on the database model, database objects, and their relationships, too.

Verify your third-party extensions and tools

Contact your third-party software providers to confirm whether they have updated their EBS extensions or tools to be compatible with EBS 12.2.  This is critical for extensions or tools that are tightly-coupled with the E-Business Suite, i.e. those extensions that modify EBS tables directly. 

Another option is to check whether your Oracle partner has put their software through the Oracle Validated Integration program for EBS 12.2.

Review Guidance for Integrating Custom and Third-Party Products With Oracle E-Business Suite Release 12.2 (Note 1916149.1).  

Related Articles


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.