Abuibra
12th August 2002, 10:34
When is user is entering Cycle Counting Data, he gets the following message:
Record is modified by other user; new values are displayed
patvdv
12th August 2002, 12:01
I think this is more a Manufacturing and application related issue. Moving thread.
Djie-En
12th August 2002, 12:41
Hi,
Take a look into the application locks.
Probably the session has been killed and the user has logon again, but still there is an application lock on it.
If so, remove it.
GN
Eddy G
13th August 2002, 15:37
Djie-En,
I think an application-lock won't result in such an error.
I rather think:
- either really another user was there.
- or (worst case) this is an application error.
Regards - Eddy
Djie-En
13th August 2002, 17:11
Hi Eddy,
I think you are right.
I don't think it is a bug, if so you should get a fatal error, i suppose.
Maybe it has to do with the ILC parameter in tdilc0100m000:
Hi Abuibra,
Has the parameter been set
Block Location for Cycle Counting Orders: to YES?
GN
Eddy G
14th August 2002, 09:37
Hi all,
If this messages comes while no concurrent users are causing it, then it is 'always' an application problem.
It should be reported to Baan's CS&S to get is solved I think.
Even some parameter-setting should not cause this.
Regards - Eddy
BaanTech
14th August 2002, 19:38
The key when entering details for cycle counting orders is order+sequence (tdilc501). When using form type 3 against
this table all occurences (sequences) for the order are shown.
It could be possible that someone has entered details for an
item and that the second user has tried to enter new details
without getting the values entered by the first user via refresh.
The inventory being counted is blocked but it doesn't look like
there is any (appl.lock) logic to prevent multiple users from
entering data on the same cycle counting order and order lines.
Abuibra
27th August 2002, 06:24
We started getting this message after service pack 9 and it has nothing to do with the application locks since I had removed all of them.
Eddy G
27th August 2002, 09:38
This really sounds like an introduced problem.
Don't hesitate to report this to BaaN PEG.
Regards - Eddy