I have a similar question to that of Jan's and I was hoping you or someone can help me with this. Do you have an idea of how long it takes to upgrade from 11.5.10 to R12.1. If you could give me an idea of the below that would be much appreciated.
• Timescales of upgrading
• Resources required . e.g. DBA
• Steps to upgrade e.g. database, then patches, moving accross customisations, then functional set up etc..
Appreciate any help you could give
Thanks in advance
This will be seriously client-dependent. There is no one-size fits all approach to an upgrade.
It will depend upon which ERP modules you use, what sort of level of customisations you have in place etc.
The pedant in me would answer by saying the upgrade process itself would probably take only a couple of days to do. However do read on, as to get to the point where you press the "GO" button on the upgrade could take a serious amount of time...
You will need at least 1 competent APPS DBA! Depending on the size of your client, you are likely to need a project plan and a team.
As an example; from 1 client i work with who recently went from 11.5.10 to 12.1.3, they performed the following tasks...
- Analysed new features in R12
- to see what new functionality could be utilised
- to see what customisations (if any) can now be replaced by new functionaliy
- to take advantage of new features to enhance existing processes
- full impact assessment of all custom code, including reports
- to identify what items required changes to get working in R12
- to identify what items were being made redundant / obselete
- to assess changes in performance
- full impact assessment of configuration
- full impact assessment of overall system performance (for SLA's etc)
- full system regression test of all existing business processes
- full payroll comparison test
- full downstream/upstream interfaces test (including EDI/BACS)
This list is by no means exhaustive!
THere were many iterations of the upgrade process carried out over a period of 16 months (yes this is how long it took to plan from inception to go-live).
During this time the existing production service still required support and an enhancements programme was still taking place (ie no steady state!). Plus they had to factor in statutory patches (EOY etc) and a desktop upgrade (Java versions).
My client team ran to approx 4 full-time DBA's, a project manager, functional & design support team of 6, a custom support team of 4, and a testing team of roughly the same again. For the full duration of the project.
Obviously not all clients will be on this scale, but hopefully you get the point. This is something that should not be tackled as just another "patching" exercise.