Hi Chinthan,
Thanks. I assume it is in one of the 3 Notes 2173722, 2173725, 2173726 that came out on May 28th for 2.0 SP3 (although the fixes listed in these Notes do not specifically mention this particular issue, but I may have missed it). We are up-to-date on all prior SP3 Notes. Will apply these new Notes soon and inform.
Thanks,
Jay.