Hi,
We currently have 2 sets of Purchase Orders (i.e. 4 purchase orders in total) which have the same OrderNbr.
![](https://uploads-us-west-2.insided.com/acumatica-en/attachment/ea82c5fa-7c95-474d-8743-1f7ebbea3c08.png)
Fortunately, this isn’t causing any issues in the database, since the 2 sets of PO’s have different types, i.e. 1 Drop-Ship and 1 regular PO, and luckily this has only happened twice in more than 2 years, but I don’t think this is normal behaviour, is it? Note that we are using MySQL as database.
We’re using the numbering sequences with auto incremental values, so technically these 4 POs should all have had different reference numbers, right?
![](https://uploads-us-west-2.insided.com/acumatica-en/attachment/4b2fdc8f-76d0-4fc7-8b8d-0385e1fc8cd1.png)
![](https://uploads-us-west-2.insided.com/acumatica-en/attachment/a33639fb-81ae-4cde-8c23-07f37c5611a4.png)
Is there perhaps something we can do to enforce that this doesn’t happen? It is causing a little bit of confusion in our operations department when they see 2 POs with the same reference number.
Best answer by Gabriel Michaud
View original