Oracle Apps Training Testing Environments
|In every implementation, there are always more than one environments in Oracle Apps.|
The rule of thumb states that below environment are a must:-
1. Development environment, where developers usually have System Administrator responsibility and also the apps password. If not System Administrator then at least they should have access to "Application Developer" responsibility.
2. Testing environment
Developers usually do not and must not have apps password to this environment . This is where users sign-off customizations or even setup changes.
3. Production environment
This is where the business runs
Conference room pilot environment is where usually implementation team gets buying to their product offering from user community, during implementation. This environment is usually used for sign off during new implementations.
This is where all new Oracle Patches are sanity tested.
This environment is exclusive to support staff. This environment is usually the most frequently cloned environment in Oracle Apps site that has gone live. Frequent cloning helps the Oracle Applications support staff to reproduce production issues
This is where repeated data migration can take place before migration code gets frozen and ready for UAT.
User Training Environment
Some clients mix this with the CRP itself. But post-goLive of APPS, when rolling out new module, an environment like this comes handy.
You as a developer do not need to worry about these environments, as your focus will be on Development Environment only.
Now some notes:-
1. There can be more than one development environment at any implementation site, when different big modules are being implemented, all having different timelines. However, the changes to each environment are UAT'ed on a common Test environment.
2. The development to production cycle is.... Developer does development & unit testing on Development Environment, and their code gets promoted to User Testing environment. Following this, the changes get applied to Production environment.
3. The changes done to "development environment" must be scripted in all cases where possible. As a thumb rule, everything except for Functional Configuration can be scripted. You may be intersted in FNDLOAD Link