Serial error "already exist"

Get Help & Support
1

Good morning,
I’m serializing parts on the WO but the message error “already exist”

Serial_3
Serial_3461×677 28.2 KB

2

Hello,

I am looking into this now, can you send a link to that WO?

Thanks!

Cetec ERP Support

3

Here’s the link

https://cetecerp.ad.attolloengineering.com/order/AE8726.1/view

4

Hello,

I don’t have access to your environment right now, and your IT who usually lets me in is out of office, but, can you please please check the config “Force unique serial numbers” and tell me the value? If this is turned on it may be the problem.

Thanks!

5

Hi,
You have an access now.

Thank you.

6

Value is 0

7

Hello,

I was never able to find the reason those serials would not set, however, I do see that the order in question looks good now. Sorry for the delayed answer, I was OOO last week.

I did ask engineering to look into this last week, and they fixed an issue similar so I am wondering if that is what fixed your issue.

Let me know if you have this happen again.

Thanks!

Cetec ERP Support

8

Hi,
The issue is not fix. The WO order that you mention, I have to enter the serials over and over again. Every time I enter the serials there’s 2 that will go through, then I have to enter it again and another 2 serials will go through.

Here’s another one

https://cetecerp.ad.attolloengineering.com/otd/order/10822/serial_control

9

Hello,

I spoke with engineering and they have a fix being tested, it should be out early next week.

Sorry for dropping the ball on this last week and the frustration it has led to.

10

Hello,

The fix should be in your production, please let me know if the issue persists.

Thanks!

Cetec ERP Support

11

Still not working.

before error
before error1183×628 61.5 KB

12

Tomorrow you are scheduled for an auto-deploy update, including engineerings fix for this issue.

13

can you provide insight in to the root cause of this issue? thanks!

14

Hey Regis,

Per engineering:

"We added a new scheme called HEXSEQ that ended up also messing with the SEQUENCE scheme in 4.11

So even if you were using sequence, we were trying to convert that sequence to hex sequence when it wasn’t allowed which resulted in all 0’s for the sequence bit of the serial."

I’m sorry for the issues this has caused since the update.

15

Thanks for the explanation!