looking back at the support ticket with SAP we were informed that this issue was fixed in v 12.0 patch 2 for SP11. I believe that is when we decided to move forward with our upgrade to 12.2.4. vs. applying the patch.
I also believe the upgrade did resolve this issue however due to the intermittent nature of the occurrence and the issues of duplicating the problem it is difficult to replicate it in a testing environment.
I hope this helps.
Bob
