HI @ankit,
Thing which i understood from this whole exercise of virtual table and calculated column within a virtual table is that if a calculated column is created in a virtual table it will hold on to the lineage of relationships it had in the parent table from where we have called it.
This is same thing happening with @grdate too. @grdate in a way belongs belongs to material movement table and hence if you call or use this as a calculated column in any other virtual table it will hold on to the lineage it had within material movement table.
There is another way of doing it if we somehow break the lineage of @grdate within virtual table and then force the calendar to use @grdate for filtering. The reason why it will work is because if we create @grdate and @rdte as physical column in order table first and then build our virtual table by summarizing order table than we will get the result we want to achieve.
This is how i have solved it. I created @grdate and @rdte in order table first as physical column and then did the summarization and userelationship. It worked perfectly.
I will wait for some other folks to verify this before closing this thread. Lets c may be there is another way to solve it.
Regards,
Hemant