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
We recently moved to HCM Cloud and finding that the standard OTBI Subject Areas are limited in functionality. Having a tool to write LSQL or help guide building LSQL would be very helpful with using OTBI with out having very technical resources.
This would be a great feature!
Great idea! We are currently using LSQL in following sceanrios:
1) Seeing the before and after Changes in employees records.
2) Performance Rating completion rates - percentage of employees with Rating out of all those eligible for a Rating.
3) Absence Rates - percentage of hours employees are absent against total Normal Working hours and how it Trends over time (i.e. Employee record needs to be correct as of the start date of the absence)
Having a UI here for creating and amending would be really helpful.
Fetching previous row data
OTBI is ideal for our less technical users, and BIP is for our more technical users. LSQL is in between but leans toward the more technical users and can push off the less technical users. Would be nice to make it more user friendly for our less technical users.
This perfectly describes the niche for this enhancement, and illustrates why it is ideal for a cloud solution and the business end user.
I concur, this is definitely comming handy in later stages of implementation.
Usually the way subject areas work gives limited results and obliges us to combine 2 or more different subject areas, and even sometimes do 2 or more analysis and combine them.
Having a LSQL easy builder would be extremely useful.
For anyone needing immediate assistance there is a very helpful workaround posted here:https://cloudcustomerconnect.oracle.com/posts/18820e4bbe
This seems helpful indeed. Any thoughts of either incorporating UI for Logical SQL or incorporating something like this excel sheet functionality in OTBI? Thanks!
We face the same issues described by everyone else.
