Some of you may be noticing issues with number sequencing in AX2012. Here is some additional information on the cause, and how to resolve these issues.
The number sequence wizard in AX2012 will generate generic number sequences for the company using the company ID as the prefix, a dash, and a number of digits predefined somewhere in the code. Below are the issues you need to watch for that will cause AX to try to use duplicate number sequences when generating transactions:
1. Same formats for voucher number sequence codes generated by the wizard: Voucher number sequences all have to have a unique format or have to all be pointing to the exact same number sequence code; otherwise, you will get duplicate vouchers. The wizard is not smart enough to know that the voucher number sequence it created in different modules needs to be unique (for example, it created the same format in the GL module and in the expense report module).
Resolution: Find the duplicate formats by going to the Number Sequence form in Organization Administration. Use the Area drop down to view the number sequences in each module, and the Reference drop down to see which ones are for vouchers. Note the ones in each module that are using the same format and modify them to be unique. (Or if the client wants the same voucher number format regardless of the source, go to the parameters in each module and point all voucher number fields to the same number sequence).
2. Number sequences created by the wizard are too long: In some cases, the field on the table where a number sequence will populate is as little as 10 characters. With the addition of up to 4 character company numbers and a number sequence wizard that uses the company number, a dash, then a minimum of 6 digits, it may already exceed the length of a field from the start. When this gets used on transactions, the last digits that don't fit the field on the table get dropped. So, for example, a number sequence in company CEUW generated by the wizard is CEUW-######. But if the field on the table that it will write to is only 10-digits in length, then the number CEUW-000001 and the number CEUW-000002 will both try to write to the table as CEUW-00000. So the first record will post, but the second record will not.
Resolution: Without some sort of script that can compare the number sequence length to the field length where it will write to, the only way is to wait to see if you get the error. It will occur on the second transaction that gets created, so at least you won't have a million transactions in the system before this pops up. You can tell if this is the issue because the number sequence value shown in the error message will be 1 or more digits short of the number in the transaction you are trying to post and of the number sequence format assigned for it. Then, simply go to the number sequence and shorten the length.
Hope this helps and happy number sequence hunting.
