[Paul Ceely]

There are some number sequences that are required -by AX itself- to be continuous (e.g. the one used for Advanced ledger entry in the General ledger module).  Can anyone point me to a list of the number sequences that AX demands must be set to continuous?

——————————
Paul Ceely
Group ERP Functional Support Specialist | Britax Group Limited
paul.ceely@britax.com
——————————

[Vinay Nayak]

?Retail Channel Id is probably another one.

——————————
Vinay Nayak
Lowe’s Companies, Inc.
Mooresville NC
——————————
——————————————-

[Kirk Blackburn]

?I’m not positive that this is what you are looking for, but…

There is a table in AX (2012 R2) named NumberSequenceTable. It contains a field named Continuous. Sounds like what you are referring to!

I looked in ours (yours may vary) and I found the following groups for those records with the Continuous flag set (with a value of true/yes)–284 records total in mine:

1. Acco_1 through Acco_83
2. AP Invoices and AP Payments
3. Bank_1, Bank_2, Bank_4, and Bank_5
4. Basi_1, Basi_2, Basi_3, Basi_8, Basi_9, Basi_14, and Basi_15
5. Budg_1 and Budg_2
6. Docu_1 and Docu_6
7. Envi_1 through Envi_8
8. Fixe_1 through Fixe_4
9. Fixed Asset Additions, Fixed Asset Adjustments, Fixed Asset Catch-Up Depreciation, Fixed Asset Depreciation, Fixed Asset Retirement, and Fixed Asset Transfers
10. Gene_1 through Gene_3, Gene_5 through Gene_8, Gene_10 through Gene_11, Gene_15 through Gene_20, Gene_22 through Gene_25, Gene_27 through Gene_28, and Gene_32 through Gene_34
11. Huma_1 through Huma_15
12. Inve_11, Inve_15, Inve_34, and Inve_38
13. Mast_5 and Mast_10
14. Prod_8 through Prod_10, Prod_12 through Prod_25, and Prod_27 through Prod_37
15. Proj_4 through Proj_12, Proj_23, Proj_29 through Proj_37, and Proj_48
16. Purc_3, Purc_7, Purc_10 through Purc_12, Purc_14, Purc_18, and Purc_21 through Purc_23
17. RFID_1 through RFID_6
18. Sale_3 through Sale_6, Sale_8 through Sale_13, Sale_18 through Sale_32, Sale_37 through Sale_40, Sale_42 through Sale_47, and Sale_52 through Sale_66
19. Tax_1 through Tax_2
20. Vehicles
21. Vend_1 through Vend_4

I hope that helps,

——————————
Kirk Blackburn
Sr. Engineer – Software Development
LDS Church
Salt Lake City UT
——————————
——————————————-

[Zvika Rimalt]

Kirk – what you have here is a list of the number sequences in your installation that were set as continuous.
but it does not inform us which of these number sequences HAD to be set up that way (since the system’s functionality is relying on it being continuous).

——————————
Zvika Rimalt
Functional Solution Architect
Vancouver BC Canada
——————————
——————————————-

[Jon Rubow]

?Is there a specific reason you are looking for this information? I would say that generally if it is in the Number Sequences it is “required” to be in sequence since you are wanting it to be unique. one thing we’ve done for one of the fields that is sequential and needs to be unique, the SYSID field, is to adjust the format of it. At the beginning of the year we just change the format to include the new year on the end and we reset the count, keeping the sequential number unique.

——————————
Jon Rubow
Systems Analyst II
Midland Paper, Packaging + Supplies
Wheeling IL
——————————
——————————————-

[Zvika Rimalt]

Both options will keep the number sequence unique.
With “continuous” turned on , AX will try to have no “gaps” in numbering.
so for example, if you used 1, 2, 3, 5, 6, 7, 8, 9 (skipped 4 for some reason), next time you create a record AX will number it with 4.

It is in fact CONTRARY to keeping things sequential, hence (and for several other reasons) I try avoid using continuous as much as possible. In my mind it serves very little useful purpose.
Even in countries where there is regulatory requirement not to have gaps with sequence numbers (e.g. Italy), that behaviour of “jumping back” is making it actually worse

——————————
Zvika Rimalt
Functional Consultant
Vancouver BC Canada
——————————
——————————————-