After activating the CAA subject area, we observed that one of our reports are erroring with the following message:

State: HY000. Code: 17001. [nQSError: 17001] Oracle Error code: 942, message: ORA-00942: table or view does not exist at OCI call OCIStmtExecute. (HY000)

One of the dim tables - OAX$OAC.DW_GL_SLA_RECON_CF - is coming in the query which seems to be deprecated with the older GL Account Analysis subject area. However the report is not even built with the CAA Subject Area (or the older GL Account Analysis subject area), but built with Financials - GL Detail Transactions subject area. Report made from this subject area should not be bringing in the table OAX$OAC.DW_GL_SLA_RECON_CF at all. At Semantic Extension, one of our custom fact tables is joined with logical table for Journal Details which seems to be bringing in this physical table at backend.

Please help us figure out a way to avoid this table to be used by our report. Current workaround is to add a column from the DFF-Journal Batches folder, which forces the report to use OAX$OAC.DW_GL_JOURNAL_CF table instead of OAX$OAC.DW_GL_SLA_RECON_CF, which resolves the issue but we are looking for a long term fix so that user need to add an additional unwanted column every time they want to use reports from Financials - GL Detail Transactions subject area.