SQL Views

Is there any way in OneWorld we can read a SQL View defined? For example.
- Lets say we create a sql view (i.e. ms SQL View not OneWorld view because the tables are outside oneworld).
- Now can we create an empty OneWorld table to point to the data returned via that view.
- Create a OneWorld view over this OneWorld empty table.
- Use that in OneWorld grid and use QBEs on it?
This is possible, has someone done this? Any help would be appreciate.

Yes, it's possible.

You need to create the OneWorld table with the exact column names and definitions as the SQL view will return and give it the same name as the business view (so the business view should probably be named F55xxxxx). Do not generate the table. Now you can continue to develop OneWorld views, applications, and UBEs that reference the pseudo table.

SHelly Not sure it will work, Have you really tired this and made it working....Just curious

JJ

Yep, it worked fine for us in our DEV environment. We've never actually had a need to to do this that warrants a change in Production, but we'd read that it was an option and wanted to test it to verify.

So what you are saying is that the oneworld table and oneworld view need to be of the same name or just the OneWorld table need to match the name and definition of SQL view. Once the OneWorld table is defined create the OneWorld view, appl etc. Please let me know. Thanks
Thanks

SHelly thanks... I tried this long time ago but JDE simply said not possible. It does works...

Jaise

Just the OneWorld table. The OneWorld view will be based on the table and can be named however you want, as usual. First create the SQL view, then the OneWorld table in JDE to match it, and then the OneWorld view, application, etc.

Seem like it should work. Great, will give that a shot, need to get someone
else involved to get the sql view created.
Thanks for the info

Re: RE: SQL Views

We use lots SQL views as OneWorld Tables in PRODUCTION and they work like charm, especially response-speed-wise.

We use SQL scripts to create SQL views that join several OneWorld Tables based on certain criteria, then create OneWorld tables matching those columns SQL views. You may try to join F0618, F0719, and F0724 into a SQL view as <????DTA>.F59XXX then Create a OneWorld Table with structures the same as F59XXX and named as F59XXX. ???? stands for respective environment owners. When you use UTB to browse this F59XXX table, you will notice the difference, especially the speed.

Re: RE: SQL Views

Do you need to setup a datasource. Can this be a datasource just on the AS/400, and not down on each users machine?