After a lot of research R&D and MF Support found the problem. Initially the error was with record 1039, but after further analysis it was also affecting Entitity IDs 1039-1051. I ran this to identify the offending records and then I subsequently deleted…