Logical SQL is a powerful tool that we can use to help us join subject areas that might not otherwise return useful data using the standard cross join analysis. However it is not user friendly and many users can't create logical sql without a technical resource, even after reviewing samples and training videos. Having a business functional end user interface, to assist in creation of logical SQL, would really help customers and increase adoption of OTBI.
When joining Salary to Assignment or Performance, and many other use cases, it may be necessary to use Logical SQL. Please see:https://cloudcustomerconnect.oracle.com/posts/8e9a22fb6dhttps://cloudcustomerconnect.oracle.com/posts/132e0068a8https://cloudcustomerconnect.oracle.com/posts/fc68b59a3bhttps://cloudcustomerconnect.oracle.com/posts/de43145427https://cloudcustomerconnect.oracle.com/posts/c238315b66https://cloudcustomerconnect.oracle.com/posts/e68146186fhttps://cloudcustomerconnect.oracle.com/posts/5884ed4854https://cloudcustomerconnect.oracle.com/posts/c02be4a127https://cloudcustomerconnect.oracle.com/posts/d79ae98106https://cloudcustomerconnect.oracle.com/posts/a0edcf37c1https://cloudcustomerconnect.oracle.com/posts/5ee5e41623https://cloudcustomerconnect.oracle.com/posts/5ee5e41623
Original Idea Number: 3dccb24a0e
Yes this is a very good idea :-)
This is a helpful feature to make it easier for end users to use LSQL
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.
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.
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
Not a UI, but there is a Logical SQL reference here: https://docs.oracle.com/middleware/12212/biee/BIESQ/BIESQ.pdf
This is a good idea and would be a helpful feature for the teams.
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.
I'm trying to build a calendar of work in visual builder that I can add to the Maintenance Management Landing Page. Unfortunately visual builder seems to only allow number format into the Values section. e.g. below trying to add this string (work due) to the display values, which it doesnt allow. I am doing the exact same…
The seeded Common Content folder under: /Shared/Common Content is visible to BI users, including users assigned the seeded BI Consumer Role. We would like to restrict the visibility and access to this seeded folder for end users based on our organization's reporting security requirements. Currently, the BI Consumer role…
Issue Description The Identifying PO field is a header-level attribute, but it is currently displayed under Distributions → Invoice Distribution Details → Purchase Order Information in the Payables Invoices – Transactions Real Time subject area. When an invoice has multiple POs, the same header-level PO can be repeated…
