Hi,
can anyone confirm that when you update from 11.5.10 database to R12 that some or all customisations will not work. I am led to believe that there are problems with Customisations/CEMLI's when you upgrade, is this correct.

Jam

It sort of will depend upon the Customisation I guess! For instance within Finance any reports that key off the PO_VENDORS_ALL table will no longer work as the table does not exist (it has been re-named to AP_SUPPLIERS_ALL I believe!).

We are looking at all teh Customisations now, with an eye on what will and will not work in R12, we have really got to the point where it is just a case of trying the CEMLI and seeing if it still works; if not find a freindly techie and get them to take a look!

The NHS have just undergone the upgrade from 11i to R12.
The whole project took approx 12 months in planning, testing etc, but a lot of this was down to analysis of new functionality, performing cycle testing and regression testing etc

They have a very very large amount of custom code; from interfaces through to personalisations and custom forms etc.
From memory, from all of the custom objects in use we only needed to do remedial work on 20-30 items - probably about 5% of total lines of code. Which in the grand scheme of things is very minor indeed.
A lot of this was due to the fact that the customisations (by and large) observed Oracle's conventions of naming and placing of custom objects within the e-Business Suite.

Main points we had to attend to were (in no particular order)

• Self-service forms - personalisations and some custom extensions to View Objects and Controllers, which required to be re-applied to newer R12 versions
• performance tuning of the new R12 baseline (performance is a big big factor with the NHS project)
• minor changes to cater for underlying table and API changes
• customisations being made redundant by new R12 functionality

I think i have gone on about this in greater detail elsewhere on this site.
The key issue is to test out the upgrade again and again. Dont expect to be able to do it all in a weekend. Take time and plan the upgrade project carefully. Dont skimp on testing resources. Get a good EBS DBA.

Prior planning etc...

Hi,
do you know what minor changes were required to the underlying tables and to what API's?. Obviously various business area's have different customisations? but do you know what customisations did not work??

One other question for you, do you know of any problems iro what windows platform R12 is run on. I have been informed in order for R12 to work correctly in has to be on a windows platform higher than XP, doe you know if this is correct?

Jan

Hi Jan

Where i am working currently, it is predominantly running XP desktops without any issues.
For my home development machines, i have a mix of XP and Linux machines - and bizzarely i have more issues with the Linux desktops than i do with the XP machines (as Linux is not an Oracle certified desktop).

regards

Barry

Oh.
The biggest custom issue we had when going to R12 was with Self-service customisations - either with form personalisations or with customisations to the underlying code (View objects, controllers etc). Which is to be expected as Oracle happily warns us all the time about such custom work

I also recall some API's now enforcing stricter data validation and referential integrity - but do not have specifics to hand at present.