Five best practices for Oracle Application Developers

WORCESTER, Mass. -- Customizing Oracle E-Business Suite applications can be a very risky venture for developers who fail to follow some simple and straightforward best practices, experts say.

Attendees of the New England Oracle Applications Users Group (NEOAUG) conference Monday got a quick refresher on some of those best practices from Sridhar Bogelli, the founder and chief executive officer of Apps Associates, a Southborough, Mass.-based application development consultancy.

Read more details

Demand a dedicated development instance
Yes, we already have a development

Change the default Apps password from 'Apps'
Well, we intentionally change the password to 'apps' in our development instance

Work with a Query-only User in Prod
What we are doing is even better, we have an daily refreshed instance for debug production incidents and for testing urgent data patches.

Maintain version control
Well, although we are using WinCVS, sometimes developers still forgot to commit and pick source from CVS.

Create all custom objects in the custom schema
Yeah, this seems to be a common sense of Oracle Apps Dev manager.

Furthermore, we are doing

A dedicated instance for UAT and yet another dedicated instance for testing Oralce patches. To refresh all these instances from productions, we are not using rapid clone, our DBA wrote their own refreshing scripts. How cool they are!