Incorrect log location for sedatacheck when running as morning process script

We are running the ./morning-data-process-yj.sh script in QA7(Fuji system) when reseller timezone(Japan) falls to next day. We observed that Sedatacheck-morning log is stored in sever date folder not in the reseller timezone date.

Steps to reproduce
Run the morning-data-process-yj.sh script such that server date is current day and reseller date is next day.

Sever date: 5th November
Reseller timezone(Asia/Tokyo): 6th November

Ran the /morning-data-process-yj.sh
Wed Nov 5 15:01:04 UTC 2014
[TSAApp@aml-qa7-core1 bidmgr]$ ./morning-data-process-yj.sh

reseller timezone = Asia/Tokyo
refdate 2014-11-05; discrepStartDate 2014-10-27; discrepEndDate 2014-11-04

Logging to /var/local/tsa/log/2014-11-06/sepull-yj.sh_15.log
Executing sepull-yj.sh -d3 --date 2014-11-05 --force

Logging to /var/local/tsa/log/2014-11-05/sedatacheck-morning.sh_15.log
Executing sedatacheck-morning.sh -d3 --distribution 178

Logging to /var/local/tsa/log/2014-11-06/whsumm.sh_15.log
Executing whsumm.sh -d3 --date 2014-11-05 –lowgran

Actual Result: sedatacheck-morning.sh_15.log is placed in 2014-11-05 folder which is server date.

Expected Result: sedatacheck-morning.sh_15.log should be placed in 2014-11-06 folder which is reseller Timezone.

Note: Sepull and whsumm logs are getting stored in reseller timezone date (2014-11-06).