Skip to Content
0
Former Member
Dec 20, 2007 at 11:06 AM

Table Lock Error

83 Views

Hi All,

We have our own workflow tool to process consignment idocs. Here we call MB11 transaction using synhoronous mode twice to do material movements.Couple of weeks ago what happended was it did 632 movement (reduce in transit stock) but failed to do 631 (increase stock in consignment location) due to table lock error which was caused by first movement. When it attempted to do the second one it failed. We believe it to be a SAP Performance issue since we had a major roll out the same week which had resulted in more system usage. It had caused serious problem since the goods did not reach the destination. So to avoid this critical issue what i did was, i put 2 seconds delay while calling MB11 transaction for the second time and it had solved the issue. But my question is , is this an ideal solution? Or should i handle it in a different way? Please advice.