Inspection Lot locking

[Former Member]

Hi Guys,

How can we allow multiple users to access the same inspection at same time for results recording.

We are having multiple inspection stations and all users are inspecting same inspection lot but diff. characteristics and they would like to record results as they inspect the meters. Currently users are locking each others too often causing unacceptable process.

Is there any way to stop this.

[former_member587434]

You can try this development:

Create diff z t-code to do result recording for each operation with copy to QE51N.

ex. ZQE01, ZQE02, ZQE03...ZQE20

So with t-code ZQE01 you can do RR of first opeartion only, same way if you want to do RR of 3rd opeartion then you need to execute ZQE03.

Revery back if you have any query. Hope this helps!!!

Thanks!!!

[Former Member]

Hi

I am not very sure whether this can be achieved by QM perspective as multiple people accessing/updating the same instance(say table QALS ,QAMR with same object number etc) system will not allow synchronus data updation.

Still check wiith basis guys

Regards

sujit

[former_member42744]

There is nothing that we can do from a QM perspective that comes to mind. You might try breaking up the characteristics into various operations in the inspection plan and give each operation a different workcenter. You might find that if the characteristics are in different operations two users might be able to record at the same time. I can't say I have tested this and you might get the same lock issues as you are seeing. But it is the only thing I can think of that might help you aovid the problem. It shouldn't be to hard to test. Just create a new plan and temporarily assign it to one of your materials.

Other then that, the users have to really get in the habit of getting in and getting out of the results recording screens. Your probably already promoting that however.

I'm not into Basis myself and I don't know if they can help you by tuning the system any differently or not. But here is a link that might help. I don't know.

http://help.sap.com/erp2005_ehp_04/helpdata/EN/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.htm

Craig

[former_member42744]

There is one outlandish possibility. You can set up databases to lock on a table basis or at record level. If for some reason your using table locking that would cause significant issues. But I can't believe that any basis team would have not found that problem and I can't imagine anyone setting it up like that.

The only way I can see that happening would be if you had some type of customization in place somewhere in your results recording process and the developer specifically used a command to use table locking. Unlikely but I guess it could be possible.

But you never know.

Craig