Idoc Locking Issue

[Former Member]

We are using an external WMS system (PKMS), so SAP is configured with

de-centralized warehousing. This means that when product is shipped we

receive from the external WMS an iDoc for the Post Goods Issue transaction.

They come in bunches, since there can be many orders on a truck. It seems

that the processing does not occur quick enough and some iDocs are blocked

because the SKU they are trying to update is locked while being updated. We

have turned on the option of 20 retries but still get too many iDocs

blocked on lock. The lock is always from the RFC user id, so the interface

is blocking itself.Many inbound SHP_OBDLV_CONFIRM_DECENTRAL idocs coming in from SBC (from |

an external WMS system) are being rejected with the error message M3024

Valuation data for material nnnnn is locked by the user RFCCI01.

For business reasons, these idocs are processed immediately and

therefore come into the system in a batch. Even with low number of

idocs coming in, up to 50% of them return with a status 51. For

example, of 13 idocs coming in 7 are going to status 51 with this

error.When we reprocess them with program RBDMANIN this obviously

reprocesses

them properly because it processes them sequentially preventing locking

|however this does not meet our business need.

[Former Member]

Before each IDOC, could you attempt to lock the object yourself with _WAIT = 'X' and then unlock it?

Rob

[christian_wohlfahrt]

Hi Scott!

In case you are getting a rejection of up to 50% of the IDOCs, then you should go for sequential processing as a immediate help (no parallel processing, not the 'real' sequential technic).

This might look slower in first hand - but with such high rejection rates you are anyway not faster currently. And it's much better to have more successful IDOCs than faster errors.

In a second step you should look for performance optimizations. If you are using Retail: there is an option for a late article master lock option (SPRO general data). It has also business effects, but should be discussed.

Also slow user-exits in update tasks can be a reason for long locks during booking -> check coding for slow parts.

Regards,

Christian

[Former Member]

Resolved - they did smaller groupings.

[vinotha_m]

Hi Scott,

Please explain the solution you have done to resolve this isssue.

I have the similar problem of Idoc error "Account is currently blocked by user"

Thanks,

Vinotha M

[Former Member]

Hi Scott,

I am having similar issue now. How did you resolved your issue. Also, can you tell me how did turned on 20 retries and where did you turned on.

Thanks,

Chandra