How Does BI Build The Physical SQL

Question

How does BI build physical queries? Below I have two queries.
Query1 – This is what BI builds. I tried to run it but after 14 minutes of no results, I kill the job.
Query2 – This is just the extraction of the base query from Query1. This runs in 2:08 minutes.
For whatever reason, BI is taking the base query and making it an inline view to create Query1. The wrapper query around this view is slow. Very weird.
There are only 409 rows returned.
Why does BI build these physical queries with the code WITH SAWITH0 ... ? It seems to be very inefficient.
Is there a way to force BI to not use this inefficient method?
Query1
WITH SAWITH0 AS
(select max(T321619.PRJ_EST_SALES) as c1,
max(T321619.PRJ_EST_TONS) as c2,
max(T321619.PRJ_EST_MARGIN_PCT) as c3,
T316339.NAME as c4,
T321619.REGION as c5,
substr(T324598.X_TERRITORY,
instr(T324598.X_TERRITORY, '.', 1, 4) + 1,
instr(T324598.X_TERRITORY, '.', 1, 5) -
instr(T324598.X_TERRITORY, '.', 1, 4) - 1) as c6,
T342203.PER_NAME_MONTH as c7,
T321619.PROJ_DESC as c8,
T316552.FULL_NAME as c9,
min(T342064.PER_NAME_MONTH) as c10,
T321619.BUILD_PART_ORD_IND as c11,
T321619.STATUS as c12
from obia.W_DAY_D T342064 /* Dim_W_DAY_D_SOCPM_Order_Create_Date */,
obia.W_DAY_D T342203 /* Dim_W_DAY_D_SOCPM_Proj_Creat_Date */,
obia.WC_VW_PROJECT_INFO_F T342484 /* Dim_WC_VW_PROJECT_INFO_F_SOCPM */,
obia.W_EMPLOYEE_D T316552 /* Dim_W_EMPLOYEE_D_Sales_Sales_Order_Resp_Custom */,
obia.W_CUSTOMER_LOC_USE_D T324598 /* Dim_W_CUSTOMER_LOC_USE_D_Sales_Customer_Bill_To_Loc_Use_Custom */,
obia.W_PARTY_D T316339 /* Dim_W_PARTY_D_Sales_Sales_Order_Customer_Custom */,
obia.WC_ORDER_VWO T321619 /* Fact_WC_ORDER_VW_SalesOrderCustom */
where (T316339.ROW_WID = T321619.CUSTOMER_WID and
T316552.ROW_WID = T321619.X_SALESREP_WID and
T321619.BILL_TO_SITE_USE_WID = T324598.ROW_WID and
T321619.ORDER_DATE_WID = T342064.ROW_WID and
T321619.DIVISION_INCL_BSC = 'VP' and
T321619.PROJ_DESC = T342484.PROJ_DESC and
T342203.ROW_WID = T342484.MIN_ORDER_CREATION_DATE_WID and
T342203.PER_NAME_MONTH = '2013 / 04')
group by T316339.NAME,
T316552.FULL_NAME,
T321619.REGION,
T321619.PROJ_DESC,
T321619.STATUS,
T321619.BUILD_PART_ORD_IND,
T342203.PER_NAME_MONTH,
substr(T324598.X_TERRITORY,
instr(T324598.X_TERRITORY, '.', 1, 4) + 1,
instr(T324598.X_TERRITORY, '.', 1, 5) -
instr(T324598.X_TERRITORY, '.', 1, 4) - 1)),
SAWITH1 AS
(select max(D1.c1) over(partition by D1.c8, D1.c4, D1.c9, D1.c6, D1.c7) as c1,
max(D1.c2) over(partition by D1.c8, D1.c4, D1.c9, D1.c6, D1.c7) as c2,
max(D1.c3) over(partition by D1.c8, D1.c4, D1.c9, D1.c6, D1.c7) as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8,
D1.c9 as c9,
D1.c10 as c10,
D1.c11 as c11,
D1.c12 as c12
from SAWITH0 D1)
select distinct 0 as c1,
D1.c4 as c2,
D1.c5 as c3,
D1.c6 as c4,
D1.c11 as c5,
D1.c7 as c6,
D1.c8 as c7,
D1.c9 as c8,
D1.c12 as c9,
D1.c3 as c10,
D1.c1 as c11,
D1.c2 as c12
from SAWITH1 D1
where (D1.c7 = D1.c10 and (D1.c1 >= 500 or D1.c1 <= -500))
order by c2, c3, c4, c5, c6, c7, c8, c9
Query2
select max(T321619.PRJ_EST_SALES) as c1,
max(T321619.PRJ_EST_TONS) as c2,
max(T321619.PRJ_EST_MARGIN_PCT) as c3,
T316339.NAME as c4,
T321619.REGION as c5,
substr(T324598.X_TERRITORY,
instr(T324598.X_TERRITORY, '.', 1, 4) + 1,
instr(T324598.X_TERRITORY, '.', 1, 5) -
instr(T324598.X_TERRITORY, '.', 1, 4) - 1) as c6,
T342203.PER_NAME_MONTH as c7,
T321619.PROJ_DESC as c8,
T316552.FULL_NAME as c9,
min(T342064.PER_NAME_MONTH) as c10,
T321619.BUILD_PART_ORD_IND as c11,
T321619.STATUS as c12
from obia.W_DAY_D T342064 /* Dim_W_DAY_D_SOCPM_Order_Create_Date */,
obia.W_DAY_D T342203 /* Dim_W_DAY_D_SOCPM_Proj_Creat_Date */,
obia.WC_VW_PROJECT_INFO_F T342484 /* Dim_WC_VW_PROJECT_INFO_F_SOCPM */,
obia.W_EMPLOYEE_D T316552 /* Dim_W_EMPLOYEE_D_Sales_Sales_Order_Resp_Custom */,
obia.W_CUSTOMER_LOC_USE_D T324598 /* Dim_W_CUSTOMER_LOC_USE_D_Sales_Customer_Bill_To_Loc_Use_Custom */,
obia.W_PARTY_D T316339 /* Dim_W_PARTY_D_Sales_Sales_Order_Customer_Custom */,
obia.WC_ORDER_VWO T321619 /* Fact_WC_ORDER_VW_SalesOrderCustom */
where (T316339.ROW_WID = T321619.CUSTOMER_WID and
T316552.ROW_WID = T321619.X_SALESREP_WID and
T321619.BILL_TO_SITE_USE_WID = T324598.ROW_WID and
T321619.ORDER_DATE_WID = T342064.ROW_WID and
T321619.DIVISION_INCL_BSC = 'VP' and
T321619.PROJ_DESC = T342484.PROJ_DESC and
T342203.ROW_WID = T342484.MIN_ORDER_CREATION_DATE_WID and
T342203.PER_NAME_MONTH = '2013 / 04')
group by T316339.NAME,
T316552.FULL_NAME,
T321619.REGION,
T321619.PROJ_DESC,
T321619.STATUS,
T321619.BUILD_PART_ORD_IND,
T342203.PER_NAME_MONTH,
substr(T324598.X_TERRITORY,
instr(T324598.X_TERRITORY, '.', 1, 4) + 1,
instr(T324598.X_TERRITORY, '.', 1, 5) -
instr(T324598.X_TERRITORY, '.', 1, 4) - 1)
;

Answer 1

When you have aggregation rules applied on the front end, OBIEE forms the additional query where you are concerned about.
Try to push the logic as much as possible to RPD side and also try to use FILTER function instead of CASE WHEN.