R12 Upgrade – Top Ten Pitfalls

If you were doing an Oracle R12 Upgrade, what Top Ten would you watch out for?

1. An R12 is a lot bigger than R11.5.x to R11.5.10. It will take considerably more time and money

2. Watch out for Oracle Payables; its had some major structural changes that have affected the stability overall. In 12.0.4 major functionality works but the accounting can still cause issues. It’s a very hard module to get through a UAT.

3. Watch out Payments; its completely new. Accounts Payable Payments functionality is now covered by this. It’s entirely in OA Framework and very, very different. All the formats will need to be redone. Basically a re-implementation so needs a lot of time and extensive user training.

4. Any customizations in Mod*PLSQL? If so, none of these will work. They will need to be upgraded to OA Framework

5. Watch out for new modules; E*Biz Tax and Subledger Accounting. These need to be configured and tested.

6. If you have customizations on General Ledger, 66% are probably going to need some re-work as Sets of Books heads to Ledgers. Minor work, but hits most customizations, custom value sets, etc.

7. Major areas such as Purchasing, HRMS, General Ledger, Payroll, Accounts Receivable are generally stable in 12.0.4. This is one you don’t need to worry quite so much on, so it’s not all bad news…….

8. In 11.5.5 to 11.5.10, 8% of our customizations failed. From 11.5.10 (CU1) to 12.0.4, 24% failed. Again give more time for the upgrade of customizations. There are some fairly large structural changes especially in Accounts Payable and General Ledger.

9. Banks – very different and there appears to still be a bug that creates duplicate banks that give an error in 12.0.4. Be prepared to spend time cleaning up your Bank Accounts. It all moves into TCA. New Rules means the Bank Number becomes mandatory for certain countries.

10. Give plenty of time to your UAT. It will take considerably longer.

So what’s your Top Ten Pitfalls?

Advertisements

Tags: , , , ,

6 Responses to “R12 Upgrade – Top Ten Pitfalls”

  1. Alvin Says:

    Hi, I just stumbled upon your blog. Would it be okay to ask newbie questions to you? Thanks!

    • irroberts Says:

      Sure, fire away and I’ll try my best to answer, based on our progress so far.

      • Alvin Says:

        Thanks! I’m an Oracle DBA/PL/SQL developer. I’m interested to break into Oracle ERP. Maybe a technical consultant since I don’t have any functional backgroun. Where do you think I should start? I know I have a long way to go.

  2. Bill Vanderveen Says:

    I agree with your warnings about AP and Payments. This seems to have stabilized quite a bit in 12.0.6, but it was a big headache, whereas before, this was a pretty basic module.

    Especially doing the AP check (excuse me, now it is a “Payment Instruction Format”) in XML Publisher. Quite a few bugs got in the way of doing this smoothly.

  3. Bruce Hartwell Says:

    How far along is your upgrade? We have been in the process of implementing R12.6 (full suite) along with Siebel, OTM, OPM, Demantra and ASCP for the better part of a year. We have one division up and running and four more to go.

    I can tell you from experience, putting in an Oracle footprint is no easy task. We moved from a AS/400 platform and custom code to Oracle’s tools and technology; what a change. Oracle can do some cool stuff, but it does not come easy – one might think that for the cost of the product it would work, of course in the case of Oracle “working”is defined somewhat loosely. Anyway, I have a blog that chronicles the last year or so of us trying to get this beast up and running, take a look if your interested.

    • irroberts Says:

      We’re actually now live on 12.0.4 RUP5 (CPC March) and a pile of patches up to July that finally got us past our UAT.

      We went live on 3rd August 2009 and so far it’s been very good.

      I totally agree. R12 is incredibly hard to upgrade too. On implementations even more so (especially as it sounds like you are doing a lot of modules). It’s a big move from Legacy to Oracle and quite a change in mind-set.

      Do persevere though – putting Oracle in is really difficult, but the rewards are certainly there for the future.

      Please do share your chronicles URL – would certainly like to read.

      (For info we are in the midst of a four year effort to decommission our IBM Legacy (ADABAS) and yes, it’s a long struggle but we are slowly getting there.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: