I personally believe this is a bug because users should not see internal codes simply because they are not user friendly and leads to confusion. If the internal code must be used then a user friendly value should be displayed to users (e.g. Select All Values).

Chandra, That's good as the SQL I wrote to extract the Compensation Market Data was used to create a data model and a BI Publisher Report. At least I know my report will still work once the Direct Database Query disappears. Regards, Karen Waddell

Chandra, Not all HCM Data is accessible via the OTBI subject areas; therefore, how do we run reports on this data if the SQL capability is removed? E.g. see the following post about the Compensation Market Data not being accessible via the HCM Subject Areas:…

Hi, I totally agree with this; and can't believe Oracle are removing the functionality. If the access to run direct queries is removed Oracle will need to ensure the OTBI subject areas cover all tables and columns in the DB. Regards, Karen Waddell

Ashley, I agree with Gary and you and think the ability to Password Protect any report which can be sent from OTBI should be standard. Regards, Karen Waddell