Skip to Content
0
Aug 28, 2018 at 02:30 PM

Duplicate Records due to slowness of the update task

179 Views

Dears,

we have had the situation that our update tasks are fully occupied and very slow. We have running a job every 5 min which converts PR to PO. In the dialog task the program checks whether the PO already exists. Therefore the update task was too slow the records were not posted to the DB but queued into SM13 and so each time then the job was running it creates another record for the same PR.

Is there any possibility to avoid such a behavior?

Thanks

BR

Arnold