Symptom
After importing a transport request from Development system to Test or Production system, the number range 17 is set to empty.
The number range 24 (83000000 -> 83999999) is inserted.
Due to this, when creating sales documents that would use the number range 17, the following error message is received:
- "For object RV_BELEG, interval 17 does not exist"
Environment
SAP S/4HANA Cloud Public Edition
Cause
Number range 24 and 17 overlaps, which was fixed in Public Cloud Edition 2508 and number range 24 was removed.
However, the Development system has been setup before the Public Cloud Edition 2508, so it still holds the number range 24.
When importing a transport from Development system, it detects the overlap with number range 17 and it is emptied.
Resolution
If the there is no number used in the interval, both ranges (17 and 24) are editable.
So it is possible to update the number range 24 to any free number ranges (e.g 999999998 to 999999999) and then set the number range 17 back to its original value (from 80000000 to 83999999).
To edit it, use the configuration activity 'Define Number Ranges For Sales Documents' (ID: 102819)
Number range 24 is obsolete and should not be used anymore.
See Also
- KBA 3641177 - Overlap of standard number ranges in object RV_BELEG
Keywords
Number range, 17, 24, RV_BELEG, sales document, delivery, number range object, SD number range, number interval, SAP entry, standard entry, greyed out, overlapping, overlap, SD document, interval, RV_BELEG , KBA , BC-SRV-NUM , Number Range Management , SD-CRF-NUM-2CL , Number Ranges (Public Cloud) , Problem
SAP Knowledge Base Article - Public