Suggested by Rob Williams – New
Currently, if two products are assigned to Serial number groups that call the same Number sequence, and Production orders are created concurrently (either manually or by Firming planned orders), the system can enter a "race" condition where non-sequential Serial numbers are issued to each order.
For example, Order A is issued Serial numbers 1, 2, 4, 6; Order B is issued Serial numbers 3, 5, 7, 8.
The race condition usually occurs on large-quantity orders due to longer processing times; large quantities also make it more challenging to identify where the non-sequential discrepancies occur.
The concern is for traceability, especially in regulated industries. Non-sequential Serial numbers for a group of products (particularly those originating from the same Prod order) could lead to labeling errors and documentation discrepancies, especially when the ERP must interface (directly or indirectly) with external systems like a lasermarker that would etch the serial number on the product.
Microsoft indicates that the limitation is due to the way the system generates transaction numbers from number sequences. A solution could be implemented via the Tracking number group module to limit the impact, as opposed to directly in the Number sequences module which has wider systemic exposure.
There is a related traceability feature and tracked component feature in Production.
Thank you, Sherry. Correct, the items can be traced and tracked within the Dynamics ERP; the concern is detailed in the second paragraph around nonconsecutive numbers.