UI for Logical SQL

User_BUU5W

Yes this is a very good idea :-)

Tamer El-Tonsy - FudgeLearn UK

This is a helpful feature to make it easier for end users to use LSQL

Eric Geddes

This is actually a big deal -- and a very good idea, indeed.

For the record, the workbook from Maxime Pignot-Oracle is a great start, but it's definitely not a solution for the problem Gail Langendorf-Oracle describes (the OP). It is a stop-gap workaround, at best, for what remains a fairly narrow slice of end users. Here's why.

• It's complicated. While straightforward, the process is "geeky" and fairly easy to mess up. It involves concepts most functional users know little or nothing about -- "blindly" following instructions they don't understand, and hoping they do so correctly.
• It's "fiddly" -- particularly the last step (copy/paste first into Word, then into Notepad++).
• It doesn't always work. For example, it fails when a source query contains "double columns" (e.g. DESCRIPTOR_IDOF) -- a common feature of many queries.

The value from combining Subject Areas can be significant, the need so ubiquitous, and the alternatives so demanding, I'm surprised there isn't a more straightforward, and less complicated solution already built-in. Here's hoping one day soon there will be.

That said, a genuine thanks to everyone who made this workbook workaround a reality in the meantime.

Gail Langendorf-Oracle

I would like to add here, that the assembler may allow a table name alias that is not accepted by the system, for example WORKER and POSITION as discussed here, in that case the error codes are ambiguous: https://community.oracle.com/customerconnect/discussion/comment/636924#Comment_636924

Alan Lee - Oracle-Oracle

Not a UI, but there is a Logical SQL reference here: https://docs.oracle.com/middleware/12212/biee/BIESQ/BIESQ.pdf

Ricardo V.

This is a good idea and would be a helpful feature for the teams.

MaartenDIF

How does this have only 2 votes with so many comments?

Very much needed to add this feature to the application. The current way of combining subject areas inside the application is way too volatile and error-prone and the logical sql combiner is not suitable for 'regular' users in my experience.