Alter express code to include views and unions for top dim items

Question

If a user selects a dimension item at the top most level, the explain plan shows that it does a full table scan of the fact table instead of using the materialized views. If we add the highlighted information(see below) to the osa generated sql, then the explain plan does what we want it to do.
Do you know if it is possible to alter the express code to include the views and unions for the dimension items that are at the top most level in the hierarchy? I think that I need to alter how the sq.query.drv program figures out what to include in the sql. But this is beyond my express comfort level.
The query below is generated by the osa cube and we want to include the highlighted information in the sql that is generated which will force it to use the correct query rewrite and return data in a reasonable time frame.
Is this possible and has anyone tried this before?
SELECT 'B4' || lt2.acct_lvl_4_id
, 'C2' || lt6.cust_grpng_id
, 'G1000'
, 'L1000'
, 'O190012880'
, 'P1000000000'
, 'R100001'
, 'T3' || lt25.mth_id
, 'E190'
, SUM (ft34.usd_curr_pl_amt)
FROM osa_fivcas_mth_ifct_gbl_992 ft34
, osa_fivcas_acct_992 lt2
, osa_fivcas_cal_mastr lt25
, osa_fivcas_cust_898_000 lt6
-- Extra Tables
, osa_fivcas_geo_942 lt20
, osa_fivcas_org_817 lt22
, osa_fivcas_prod_710 lt23
WHERE lt2.acct_lvl_9_skid = ft34.acct_lvl_9_skid
AND lt6.cust_lvl_10_skid = ft34.cust_lvl_10_skid
AND lt25.mth_skid = ft34.mth_skid
-- Extra Join Conditions
AND lt20.geo_lvl_8_skid = ft34.geo_lvl_8_skid
AND lt22.org_lvl_12_skid = ft34.org_lvl_12_skid
AND lt23.fpc_skid = ft34.fpc_skid
AND lt2.acct_lvl_4_id IN ('81013286')
AND lt6.cust_grpng_id IS NOT NULL
AND lt25.mth_id IN ('AUG08')
GROUP BY 'B4' || lt2.acct_lvl_4_id
, 'C2' || lt6.cust_grpng_id
, 'G1000'
, 'L1000'
, 'O190012880'
, 'P1000000000'
, 'R100001'
, 'T3' || lt25.mth_id
, 'E190';

Answer 1

David,
When u add a field to a header table. U can use the User data source to bind it. Even if u add the DBDatasource the Coulmn needs to be present in the DB at the time of setting the data source to the Field in the UI.
Actually if u add a header filed to the DB it pops up on the User-Fields Form i guess u can use it as no extra code is needed. To view the UDF form VIEW--User Defined Fields.
Hope it helps,
Vasu Natari.