Improve performance of qryMMSSalessummary_listbydaterange

exec qryMMSSalessummary_listbydaterange @EntityID=3997,@StartDate='2019-01-01 00:00:00',@EndDate='2019-12-31 00:00:00'

Looks like they've run the report for a whole year date rage. 

But the proc only uses temp table variables, which won't be able handle this load. I checked with Martin, and he mentioned this proc was optimised on the trunk code a year back. ( see attached )

Please try to replicate these optimisations, or at the least if we can change the temp table variables into temp tables that would help the proc alot.