In our projects we use Device Infor Records (DIR).During the cretion of technical master data a MDT gets triggered which installs the DIR at the Installation.
We are facing a issue currently in our system.Whenever employee starts the process ,it gives an error message that the Material/Seral Number <DIR No> is locked by the user.
If I execute the process individually on test system it works fine.In production environment whenever there are multiple processed are triggered simultaneously then this problem occurs.
Also occurance of this issue is not consistent ,we get 2-3 such cases per day.
Kindly advice what could be the issue and how we could fix this.
In production environment whenever there are multiple processed are triggered simultaneously then this problem occurs.
Multiple means the same process is executed simultaneously? If yes, then it will surely raise problem of Locking, This should be avoided.
Also are you sure that there is no user-exit where custom code is added? As COMMIT commad applies lock on master data and that could be the reason of the issue.
each node of the MDT commits itself, there is no explicite commit needed. Was the DIR created also within the MDT? Did that fail for some reason? And even if using several replication queues from CRM, each DIR should be used only once and by one single process. Or do you store one DIR within several installations/contracts? Normally only one DIR is used and only that particular DIR is touched during MDT processing.
But in order to check the issue, I'd suggest to run a lock-trace (ST01 or ST05) and check which particular lock is not released in time.