It's been a version or two since I dba'd a financials database, but you can tell that different (non-communicating?) development teams handled the different modules. Very frustrating to guess which of _nbr, _number, and _num various keys used. ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Srinivas Chintamani Sent: Wednesday, March 03, 2010 4:53 PM To: niall.litchfield@xxxxxxxxx Cc: Jared Still; kjped1313@xxxxxxxxx; john.kanagaraj@xxxxxxxxx; j_akins@xxxxxxxxx; oracle Freelists Subject: Re: Oracle Financials WOW! that was good response ! On Wed, Mar 3, 2010 at 11:25 AM, Niall Litchfield <niall.litchfield@xxxxxxxxx> wrote: Before we go too far down this route it's worth considering how one would design an application back in the days when customers didn't have access to declarative referential integrity, PL/SQL was new and the cutting edge version of the database was marketed with an added cost "transaction processing option". Queries were 'optimized' using a set of rules and the number of concurrent users was frequently less than 20. Even the decision not to normalize when normalization meant you had to do your own data integrity wasn't as terrible as it might have been. None of the above should of course excuse SOA :) Niall On Wed, Mar 3, 2010 at 3:26 PM, Jared Still <jkstill@xxxxxxxxx> wrote: On Wed, Mar 3, 2010 at 7:17 AM, Kellyn Pedersen <kjped1313@xxxxxxxxx> wrote: ... "build us a financial application" but forgot to let them in on the 10 commandmants of Oracle, (i.e. thou shalt not build complex views upon complex views, though shalt not index every column in a table,....:)) thou shalt not forget the purpose of normalization Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com <http://jkstill.blogspot.com/> Home Page: http://jaredstill.com <http://jaredstill.com/> -- Niall Litchfield Oracle DBA http://www.orawin.info -- Regards, Srinivas Chintamani