Dupe Sales Order Numbers: Has anyone ever had issu...
# administration
j
Dupe Sales Order Numbers: Has anyone ever had issues with duplicate sales order numbers being generated automatically by NetSuite? We have 2 remote order entry clerks that are entering orders. When the sales order form is opened, NS displays the generated sales order number on the form. Within 2 minutes, our clerks both entered an order with the same sales order number. I have been told that this would happen on a very infrequent time, but in the last 2 weeks it is happening more often. I have looked at setup > company > setup tasks > Auto-Generated Numbers. The checkbox for "Allow Override" is checked - if that matters.... Any thoughts on how this is happening and better yet, how to resolve the problem? thanks!
j
@JR Yeah, your problem is the
Allow Override
checkbox. Good news, you can prevent duplicate document numbers. I'd suggest you customize the
Sales Order
record to display the
generate TranID
on Save Box. (or set this to default with a workflow?) When this box is checked off, NetSuite will record the document number when the user saves the transaction record, not when the user creates the transaction.
j
@Josh Godfrey Thanks for your input, very interesting... I'm not too familiar with the auto-generate procedure. Are there any dangers in unchecking the "allow override" box? will this not allow a user to modify the sales order # at creation or editing of the sales order. I think today our customer service manager will modify the number to "push" the sales order through. I would have expected an error to occur when saving the sales order initially. The example i have occurred 2 minutes apart.
l
@JR Are you suggesting that someone is manually editing the Sales Order number after the Sales Order is generated? If so, this rather strange - why would you want to do this? What @Josh Godfrey is correct, unchecking this box will solve your problems. You can read more here: https://system.netsuite.com/app/help/helpcenter.nl?topic=ADMI_NUMBERING&whence=#bridgehead_4340447524
j
@Lee Hopper no, apparently 2 newly created sales orders have the same ID. I'll read your link when I get home tonight. Thanks much!
@Josh Godfrey @Lee Hopper So, I unchecked the "allow override" checkbox, and our B2B website integration with FarApp failed. Apparently, not being able to edit the tran id when a record is created is an issue. I guess I'll open a case with NetSuite about the original issue with dupes.
l
@JR I assume that the 3rd party integration is re-writing the SO with your B2B's order reference number? If so, that is why it is failing here. To be honest, I wouldn't set it up this way - I would leave NetSuite to generate its own SO number, then put the website order reference in another field (most people use the PO# reference field). I'm not sure opening a case will help you much, as if you read the link is sent you it says "Be aware that overwriting these record type numbers permits users to create duplicate numbers or numbering gaps." - i.e. what you are experiencing is expected behaviour and not an issue with NetSuite. A "work around" you could do is create a Saved Search that groups by SO number and counts the number of records - then emails you if this is >1 (i.e. there is a duplicate). You could then manually amend the SO number. Not great, but possible.
j
@Lee Hopper Thanks for your response. I agree about the reference number. This was setup by my predecessor and honestly, i don't know if this is a requirement by the third party or not. The source is a B2B website that we are retiring in about 2 months, so we will just be careful and mindful of the issue. By communicating, our customer service reps (only 3) can handle this. In my sandbox, i was able to open 2 new sales orders in separate tabs. They both had the same sales order id. I saved/created one without issue. When i tried to save the other, an error popped up alerting me that it was a dupe and could not save. However, in production, that error is not occurring. This has certainly been interesting. Thanks to you and Kevin, i learned a bunch of new things today! 😉