Query Tuning:PPI not being used in select - response (5) by teradatauser2

Hi Diether,
Thanks for a quick response.
1. i was not able to understand your first answer fully. ppi is used to help in range queries as in this case. if we replace tab2.date1 and tab2date2 with some finite value either by hard coding or current_date, it uses the elimination. So, why does it use elimination in this case ?
But, in practical scenarios, the value come from another table, as in my eample.
The min and max that you suggested would change the o/p result (correct me if i am wrong here). Not sure if this can be acceptable to business logic.
2. Yeah, my table is a single row table, i understood you view concept. I will try to implement it.
I have two queries to tune one with a general scenario ,case1 ,and other with single row 
3. Additionaly, I tested with a sample table for 2nd approach .With a single row also , using the view approach, it doesn't even give "enhanced by dynamic partition elimination".  Rest all enhancements that you suggested does happen.
Is there not a way to force the optimizer to use partition elimination in these cases ?