Duplicate Records due to slowness of the update task

[arnold_fritz]

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

[arnold_fritz]

Hi Mike,

Thanks for your answer. But if the update task is too slow in my opinion also the lock into the lock table won't be posted. But maybe I'm wrong.

Thanks

Arnold

[pokrakam]

Every 5 mins??? Off topic, but I'd suggest making this event driven if you need a PO that fast.

Rather than just looking for a PO, also check whether the PR is locked before creating a PO for it. If it's locked, leave it for the next run.