Hi, I'm struggling to find best practices regarding number sequences, so I have a few questions I'm hoping someone can answer or provide me with a suitable link for.
1. Some countries have regulations saying that number sequences for transactions that are posted to the ledger must not include duplicates nor gaps. Gaps can be solved by simply using a continuous number sequence, but there is often a risk of duplicates when using the wizard for generation as several sequences get identical formats, or duplicates can be generated when a number sequence goes very high and overlaps another. Is there a convenient way to make sure that no duplicates will be generated or do I need to adjust the number interval manually for all number sequences intended for ledger transactions? Has anyone come across a list saying what number sequences are used for transactions posted to the ledger (as these are typically the ones covered by regulations)?
2. What is the downside of using continuous number sequences?
3. Should the company code be included as a prefix in the number sequence or not? What is best practice and why?
4. Is there something to consider when it comes to length of a number sequence? For example reports that allow a maximum number of characters and will cut the number sequence if it is too long?
1. Duplicates should never occur and they would usually cause the whole process to fail, because number sequences are typically used for unique fields and the database reject records with such duplicates. If you configure conflicting numbers sequences for a single field, it's a bug in your configuration.
2. The main problem with continuous number sequences is the impact on performance.
3. It depends on how you want to use the values.
4. You need to respect the length of data field. If there is a report that can't accept all characters of a field, it's a problem in the report and not in a number sequence.
Hi,
In Turkey we have certain requirements for number sequence to be continious. So we use some localizations by to add a field on voucher transaction and update accordingly in the year ends or month ends, depending on the rules.
If you are ok to have number sequences, you can use ledger parameters parameter to not to allow duplicates.
As I used to do, I go over all the number sequence parameter and change the number sequence in the parameters to be able to have visuality in number sequence like to add a constant upfront. (you can upload number sequences via Data Management)
There s no downside to use continious number sequence.
You do not need to use company code as a prefix. You can use if you require in the report to understand from which company does that transaction come from but it is not a must just a way. You can use data area id for that purpose.
For number sequence length, you need to be sure that the field you use has the correct length of the number sequence or else number sequence will be cropped.
André Arnaud de Cal...
292,111
Super User 2025 Season 1
Martin Dráb
230,934
Most Valuable Professional
nmaenpaa
101,156