Customisation's and various tables will be affected and Oracle Seeded data entered as part of the Upgrade. Take a look at ConfigSnapshot for use throughout the Upgrade and beyond for business as usual activities, patching etc. especially the Customisation Identification and Impact Analysis. The tool will also identify new fields and functionality being introduced or being make obsolete as part of the Upgrade so you can plan and act accordingly.
Please note you can run the ConfigSnapshot Customisation Identification and Impact Analysis against your R12.1.3 environment before even starting the Upgrade as it is an essential part of Upgrade planning and you do not have to stand up and R12.2.9 environment to do this.www.ConfigSnapshpt.com
I hope this helps.
Kind regardsMartin Jenkinson
Hi Alfredo,As you know you are already licensed for API Wizard, so if you do need to recreate the templates and forms, you may as well just use API Wizard to replace the templates since it would be free since you are already licensed, and that would also help you in the future when this situation arises again as API Wizard loaders are immune to upgrades and patches so you'll have a much more seamless upgrade path. Let me know what processes you need and we can talk outside of this forum and get you the loaders you need. Thanks!Sarah
Happy to add a little detail for this question as we're seeing many customers upgrading to 12.2.x (whether or not they plan to go Oracle SaaS):
Custom Forms. Has the upgrade caused any problems with custom forms and are any additional steps needed other than needing to recompile them?
One of the key changes in R12.2 is in the patching mechanism, which relies on database editioning. As part of this change Oracle requires that customizations only reference objects in the APPS schema and not the underlying tables. As this restriction was not in place prior to 12.2 it is possible that some customizations do reference underlying tables. If the specific schema name is not included before the object name then the customization should use the synonym with that name, which should reference the correct APPS object. However, if a schema other than APPS is referenced in the customization it should be changed so that the customization refers to the APPS object. Once this is done recompile the custom object and migrate to the system accordingly. WebADI Templates. Will WebADI templates from 12.1.3 work in 12.2.9 or do they need to be re-created?
Templates itself will not have an issue. We need to make sure the APPS schema is referenced in the custom packages/views used by the WEBADI instead of standard schema names.
When we upgraded from 12.1.3 to 12.2.6, we had to reapply all of our customs to the 12.2.6 version of the forms. If you use personalizations, those are persistent and just need to be tested for applicability.
If you have not already done so, I would recommend making sure all customizations (forms, extensions, bolt-ons, etc) reference the apps synonym for any tables rather than going directly to the product table. This will save a lot of issues when it comes to on-line patching.
After we upgraded to 12.2.6 and 12.2.9, Web ADI templates needed to be recreated. We still have an open 12.2.9 SR with Oracle on the LOV for a DFF stating no value in accounting date even though the date exists. There is a workaround for that but we are still waiting for a patch.
Oracle ERP Project Lead
Financial Systems - 10742
Sandia National Laboratories
The Oracle Applications & Technology Users Group (OATUG), formerly the Oracle Applications Users Group (OAUG), is the world’s largest education, networking and advocacy forum for Oracle Applications & Technology users.
Copyright © 2021 Oracle Applications & Technology Users Group. | All Rights Reserved. | OATUG PoliciesAll material, files, logos, and trademarks within this site are properties of their respective organizations.