Does the error also occur when reprocessed with BD87? Try to set a soft breakpoint in the processing function (look for the processing code in table TEDE1). Then execute the IDoc in BD87 and see how it behaves there. If nothing helps, stop the update queue with SM13 for a short time (mind nobody will be able to leave a transaction with SAVE meanwhile), then process the IDoc with BD87 and check in SM13 what updates are done.
Dig Deeper on SAP UX
Related Q&A from Axel Angeli
An SAP user is receiving an error message while integrating SAP iDoc PORDCR1 for a purchase order. Continue Reading
SAP expert Axel Angeli explains how to update the "further dates" tab information in am SAP transaction through an SAP IDoc. Continue Reading
An SAP R/3 4.7 user wants looking to post a document entry using different trading partner fields for credit and debit for function FB01. Continue Reading