You’re offline. This is a read only version of the page.
Announcements
108
Hi Yepitsme,
I'm with Sergei here. It is controlled by the design. Note that this wizard seems to be easy, but I prefer to make an own set of number sequences. The coding done by the system is not meaningful. E.g. sale_1 to sales_1138 is not something helpful when you search for a specific number sequence.
In addition, some number sequences control values for vouchers and causes overlap in numbers which would give issues later. E.g. if you posted 24 invoices and then wants to post a credit note, you can get an error that number 1 was already used. So, to prevent this, you would still have to review the generated number sequences.
Hi Yepitsme.
As per my understanding There are some number sequences in the system which are super sensitive to control data integrity and used between cross modules and also generated automatically when we settle 02 documents together. For Example: Closing voucher & Payment voucher. These both numbering sequences are used when we do closing settlement of invoice and update open transactions so by default system keep their smallest number larger than 1 to allow sufficient numbers to be used without any manual intervention.
Hi Yepitsme,
It's controlled by NumberSeqModule* classes and how the number sequence is set up. For some number sequences, the lowest number is set by parmWizardLowest method to a higher value than 1. Probably it's needed for some legal requirements or to spread ranges between several number sequences.
Hi,
Were some of these sequences setup beforehand, which might have been used for creating master records/transactions?
#1
André Arnaud de Cal...
294,095
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
