Hi,
I believe this topic is about 2 users trying to update - at the same time - the same record ?
Here is what I know about the sales order side :
- P4210 will 'lock virtualy', while accessing the sales order detail line, the sales order through inserting a record in the F00092 (tip P00092). Each time the P4210 cannot insert in this file he advise the 2nd user that this SO is reserved by USERNAMEID with an error (red !).
You'll have to check some SAR's about that (Keyword Record Reservation) because it was badly handeled in some cases.
- P4205 is also using the RR functionnality.
!!! THAT's ALL for the interactive side !!!
- R42520 can also handle the RR if you have the correct SAR installed.
!!! THAT's all for batches !!!
Be aware that R42565 and many others don't use the functionnality, JDE is reporting some of those batches either as NON MULTI THREAD batches or as batches that can be run at the same time but not on the same data selection.
Hint : see the UDC 00/RR to have an idea on which IV or BV can use RR functionnality. Perhaps other interactives or batches also use it [without giving a disable possibility], but don't add any record to this UDC, it won't do anything as the IV or BV must have the correct code to handle it.
We had to correct the code ourselves after few tests, watch P00095 while running tests (same user with 2 windows entering the same or 2 different sales order and going out on just one of them - P00095 completely cleared !).
Anyway, to be sure, for the batches : try to have multiple queues to allow performance, but don't run batches on different queues if they can run over the same records.
Hope this helps
Fred
