Re: Reverse Engineering and selecting specific tables

Hi Hans,

"The biggest benefit of going to the underlying table is to need to check
whether Oracle has changed the table definition or even table purpose -

each and every time they issue a patch."

I respectfully disagree.

1.
In the case I used as an example (HZ_PARTIES) rows in this table are exposed via a number of views.....if we take from the views we must re-integrate that data in the DW should we implement a similar concept of a 'party'.....this takes quite a bit of extra code (a new ETL job per view) and we need to be very careful about how we perform that re-integration......If we take from the underlying table we need only write one job and we can expose the various views of HZ_PARTIES using the same logic as OAP uses...

2. True. Oracle may change underlying tables release to release.....

However, on my last OAP project where we saw the notes written in reports from a change from 10.7 (I think it was) to 11i I saw extensive comments in the sql about how the reports had to be changed due to changes in the views too.

It did not seem to me that the client was spared too much pain by reading through the OAP views. Though I would agree the client would have likely had more pain (how much I would not know) had they written reports directly off tables.

3. (And since I am actually a consultant it would indeed be in my best personal interest to take data from views because that would generate more work during development......there is no job security for a consultant....but I am glad you were amused...;-) )

My concern is what would be the most cost effective approach for my client over the 2-4 year time frame which will include upgrades to Oracle Apps.

As I said, I would be interested in hearing other peoples opinions on this... :-)

Best Regards

Peter
www.peternolan.com Received on Wed Nov 02 2005 - 02:27:31 CST