Friday, June 13, 2008

R12 Best Practices White Paper

I noticed today on Stephen Chan's blog that this White Paper is available on metalink

Best Practices for Adopting Oracle E-Business Suite, Release 12 (Metalink Note 580299.1)

I haven't reviewed the document yet, despite there being a section on AGIS. As soon as I resolve the problem I'm having with my metalink login I will take a look. I understand it was pulled together by Anne Carlson, who I know reads this blog becasue she mailed me just today with a question about it, I'm hoping some of the useful posts from this blog made the cut.

I want to use this opportunity to plug two other guides that are new in R12 and I highly recommend you read if you are looking at upgrading to R12.

Oracle Financials Concepts Guide, Release 12 (Part No. B28873-01

Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12 (Part No. B31543-01)

I discuss them a little more along with a few other resources in this post.

UPDATE (June 16th):

I reviewed the White Paper and the AGIS section is fairly sparse - I will be contacting the author to try and get more detail in there.

However on the whole I think it's a great document and essential reading for anyone looking to implement  or upgrade to R12.  Now if we can just publish that information on a blog, then we'll truly have a living document, I'll ask that question of the document owners.


Bill said...

David, re: FA AGIS and SLA - are you saying that in r12 FA automatically calls AGIS interco setups via SLA without any type of user configuration in SLA? Or does SLA have to be modified in order to get some of the interco accounting to work right?

David Haimes said...


I assume you are referring to the FA post

You are correct that this will happen out of the box and there is also an upgrade of the accounts stored in FA in 11i to the Intercompany Accounts in R12.

Shree said...

I'm a regular visitor to your blog and i really like the way you present your topic.

I have a quation. Currently we have oracle applications 11i ( financials and projects. Currently,In US we have one set of books with multiple operating units.Out of which we want to split one existing ou into multiple OUs for better analysis and reporting. Currently we have 2 major line of business that we operate. We have this line of business also part of our chart of accounts. I need to know the best practices/advantages/disadvantes/limitatons of having different OUs for each line of business compared with running reports fron single OU by line of business segment from the COA.

Thanks for your help,

susan said...

We are faced with a similiar issue as Shree - can you share your solution/insight.

Thank you

David Haimes said...

Apologies - I missed Shree's comment, I posted an answer now.

David Haimes said...

Shree, Susan,

An operating unit (OU) is primarily used to separate out different business operations and has security and ability to define certain set up options by OU and seperate things like supplier sites and bank accounts by OU. If you want the same security and options etc for the two lines of business then I would say segment reporting should be the way to go.

This is just a general opinion and you need to do detailed analysis on your own particular use case to make the decision.

Sridevi K said...

Sridevi Koduru (Senior Oracle Apps Trainer
LinkedIn profile -
Please Contact for One to One Online Training on Oracle Apps Technical, Financials, SCM, SQL, PL/SQL, D2K at | +91 - 9581017828.