Transfer Order Locking Issue

[Former Member]

Hi Experts,

We are looking for a potential solution for transfer order lock issue:

Situation:

In out outbound picking scenario we use one single transfer order per delivery. One delivery can contain one or more material and batch combinations. essentially there will be around 22 pallets to be confirmed per transfer order.

We use RF functionality to confirm the transfer orders. On the picking side we use standard LM05 transaction.

The practice is user will confirm one pallet pull it out of the rack and drop it in the dock door or truck and then continue with the second pallet of the same TO.

Issue:

There is a possibility of signal drop near the truck. when the user moves at a place where there is a better reception he is able to connect back again. however the TO is locked under the user ID because of network drop. Now the user is able to get into another TO and continue but not the same TO. This TO gets unlocked only after about an hour when the basis batch job determines the user is not on that transaction anymore and unlocks. This way it causes a problem that user needs to wait for a long time to get the To unlocked.

We are aware that Basis transaction SM12 can unlock the table lock but that comes with a potential risk in production system that any other user/table can also be knocked off if we provide this access. hence not feasible.

Can anyone share if they have faced this issue with their clients and provide some hints on standard/custom solution that can resolve this issue.

Any pointers on this will be appreciated.

Thanks!

[Former Member]

Thanks Manish and Ravi for your responses. Our client has spread accross multiple geographies. By the time they raise a incident ticket and basis team resolves the issue it will take some time. So we are looking for an instant solution via a custom development so that user/supervisor is able to fix this by themself.

Best Regards,

Harish

[JL23]

Removing locks via Basis guys should certainly be an exception  and not a solution.

Theoretically this could even be done with a small ABAP started from your scanner device restricted to certain tables and users.

But as said, I don't think this is a good approach at all.

Better is to invest into the infrastructure. It is even possible to scan with smartphones and send the data via mobile telephony instead of own wireless network

[Former Member]

Hi Harish,

We face this same issue rarely even in our RF system also. When network drops, the TO gets locked and also multiple online session gets active for the user, due to which the operator does not get the task and also the TO does not get allocated to anyone. After Basis team's removing the active session of the user, he is able to continue. We don't depend upon the background job, and it only takes 5 - 10 mins.

[MANIS]

Do you really think this is a system issue and by writing some custom code this can be eliminated.

The only solution for this is that you need to look for your infrastructure by making sure that there is proper connectivity across the warehouse and in all the working area