Number Range object configuration can be seen on SNRO transaction, 'Ranges' tab:
Rolling object
If the flag is not set (No-rolling), this means that the NR object is defined as Rolling.
When object is defined as 'Rolling', numbers will start to be taken from the beginning when an interval has been used up.
So, numbers will automatically start from the beginning as soon as the upper limit is reached.
- The option "No rolling" is not selected in the definition of the number range object.
- There is an interval shortly before the "to" number is reached.
- Once this is reached, the number assignment starts from the "from" number again.
What should be checked so that there is no attempt to generate a duplicated entry upon the second assignment of numbers?
See Note 2688698 - NR: Interval before rolling, what should be done?
- Is the number the only key field? => entries from the application table must be archived or deleted to avoid duplicated errors
- Are there other key fields? => in that case, those other key fields will make the entry unique, so no duplicate key errors will occur.
No-Rolling object
What happens if the object is defined as No Rolling?
If interval has been used up, no more numbers can be requested from that interval.
This should be checked by colleagues from corresponding Application team responsible for NR object, to check how Number Range functionality is called; and next steps.
See KBA 2890487 - NR: ERROR => ThINoAddNum: overflow
It might be needed, if possible, to increase the "To number" interval limit.
See also
If you want to display the intervals that are in the critical range -in accordance with the definition of the number range object (warning percentage)-;
or you want to display the intervals in which percentage of used numbers has reached a certain threshold.
2292041 - Number Range: Monitoring intervals over critical number (warning %)