I got the message below from someone in our IT. Does this make sense to anyone else? Doesn't seem logical that the EDI job would need to be doing a full table scan each time. I'm pretty sure he means the EDHISTRANS table since I can't find the table he mentions.
-----------------------
Our you ok with us purging the transaction history?, it is causing the ED501/ED502 job to run extremely slow.
The ED501 should complete in 1 minutes, but it taking upto 12 minutes. And we submit the job over 100++ times a day. This will eventually cause a break down , since the PO120 will want to write the FILE ED501 needs to delete.
The issue is EDI is doing a full table scan in the EDTRANSHIST table every time it runs, so the smaller the table the faster ED501/ED502 will run.
----------------------------
That's good then. Lawson knows that this is apparently an issue and created ED300/10/20 for it and it's not my IT staff just trying to delete stuff like usual