in one of the previous posts was mentioned "a wrapper business object" that would allow to create a business object having data/columns from several tables.

The BusinessObject = 1 table is slightly problematic in the case when you would need to create a business object that would include columns from several tables (a SQL join)  and perhaps some computed fields (some computation rather done in the database than in the application).

In a Oracle environment would

a) this kind of wrapper solve this problem or
b) DDT bring any help on this issue
c) something else...? 

Lastly, is this true: the data structure of the business object is just a place holder and the query populating the data structure can be whatever, e.g any SQL-statement? If this true, then it would be possible to create just some dummy tables/views into the database. However, a wrapper approach would perhaps be "cleaner" as it wouldn't add anything to the database.

Kari