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
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…
BI Publisher bursting currently reports an email delivery as successful once the email has been processed and sent from Oracle. However, there is no customer-accessible functionality in Oracle Fusion/BI Publisher to determine whether the email was subsequently delivered, rejected, bounced, or returned as undeliverable by…
ERP: Ability to provide copy functionality for reports within report security permissions or manage privileges without providing full edit / write access. Currently, it does not appear that 'copy' access can be given independently.
FDI: Ability provide copy functionality for reports within report security permissions or manage privileges without providing full edit / write access. Currently, it does not appear that 'copy' access can be given independently.
Currently any user account having access BIPDataModelDeveloper role is providing the ability to see any sensitive information in the Oracle fusion irrespective of data restrictions placed in the front end through role assignments. User while creating a data model can see any HCM data like (Payroll details, DOB, SSN, etc.)…
