Hi Khurram,
you cannot exclude it completely that this exception occurs. The destination could have been adjusted by an administrator just after you have retrieved it and just before your code wants to use it. Hence, to b absolutely on the safe side, your code needs to be able to to react on such a situation and resume processing by simply executing the call again.
Best regards,
Markus
P.S.: This issue definitely happens more often, when using destination management in a wrong way and adding and removing destinations all the time programmatically, e.g. if one thinks that only thus a user to the same logical target can be exchanged, which would be done better using an RfcCustomDestination
