F31122 is having record with UKID=0. This occurs randomly and solution to it is delete the record
We have customer who recently upgraded to E1 9.2 from E1 9.1 and they reported one issue with F31122 record where a corrupt record generated in F31122 table with UKID 0 and that stops further processing of any records in F31122. the only solution is to delete that record and move ahead. The customer reported that this was happening in E1 9.1 also and Oracle couldn't replicate and provide any fix for it.
Has anyone come across similar issue and have permanent fix for it?
Your help will be highly appreciated.
Thanks
Jinesh Masalia