Sales order number duplication

lodger

We run NF 2.6 and sometimes have a problem when entering sales orders. We have 2 users on the same site entering orders when one of the users is part way through the order they receive a message informing them that the order has been updated by another user and will then take them back to the menu.

When investigated we can see that both users have been allocated the same sales order number. Only 1 order will remain in the system and the aborted order must be re-entered.

This also happens in the purchase order entry. There are no modifications that change the order entry process.

Has anyone seen this before and is there a solution?

Thanx
lodger

awarn

I can be half helpful and tell you why this is happening, and give you a work around...

The NF client does most of the work on the local computer, not on the server. So the info on the screen is not *totally* up to date. What is happening in your case is that 2 users are hitting the database to get the next number in the number series (onnewrecord trigger), but the record isnt saved / updated until the client decides to insert it (oninsert trigger) (ie by tabbing off the record).

Maybe in training you could suggest the following procedure:

F3 to create a new record (onnewrecord trigger)
enter the customer number
tab (mouse scrollbar or VCR buttons) to the previous button (tabbing off hits the oninsert trigger)
tab back to the new record and continue.

Hope that explains it.

-A

Sbhat

Hi,

Make the No. field on the Sales order non editable and have the user use the systems no. series and you will not have this problem.

Regards
Suresh.

lodger

Thanx for the help.

Manual SO numbers are not allowed so that can't be the problem.

awarn - you made me look at this and you are right. The number series table is uptaded immediatly but the header info is not written back until you move off the header. What appears to be happening here is that occasionally a user may stay on the order header for a while which would make this order look empty to another user if they looked at the list. We have 1 user who always looks at the list first and if an unused order is there they use it, but it is not empty, someone else is only part way through it and it's the first user to get to the items that keeps the order.

Thanx for the pointer it made me understand what was happening.

lodger

DenSter

Ah the problem is not Navision related, but that user should not use an order that appears to be empty. As soon as you leave the No. field, Navision inserts a new record into the database, you don't have to leave the record to save it for yourself, contrary to what is being said here.

But, if you then start entering information at the same time that someone else thinks they can claim that order, you will have situations like that. All users should start with an empty order and create a new one themselves rather than starting off with what they think is an 'unused' order.

hth,