Gaps in document number ranges
Gaps in Document Number ranges
Attached notes for a possible explanation on the missing document numbers.
These notes will help you identify other possible gaps in document number ranges
175047Causes for FI document number gaps (RF_BELEG) -Here you can find a summary about situations, where missing document numbers (gaps) could occur. See also the referred notes at the bottom of the note.
193020 Invoice verification: Gaps in number assignment
452127MIRO: Standard number assignment per company code
Please note that it is complicated to fix all the gaps, but it is important to document existing gaps in number assignment for financial auditing purposes.
The possible and usual causes for the number range gaps are as follows:
1. User exit USEREXIT_NUMBER_RANGE in program RV60AFZZ.
Please check the user exit. (In SE38)
2. Number buffering (which might not be applicable to your case)
Please check transaction SNROfor object RV_BELEG to verify if buffering is switched on. Please refer to the note 62077, 23835 and 363901.
3. Update termination -this is the most likely cause of number range skipping.
Review transaction SM13 for update terminates during the run. Also use transaction st22 to check whether short dump occurred.
Understand that in different countries you have to explain document gaps to Legal Authorities.
For this reason there is report RFVBER00 for document gaps occurred due to an update termination. The report RFVBER00 does only list update terminations that are not older than 50 days. It is necessary that these update terminations are documented the 50 days expire.
The other possibility is that the gaps occurred not due to an update termination. Gaps without update terminations cannot be (easily) explained. They can be (only) detected via report RFBNUM00 (IN SE38). This report displays these document number gaps for the number range object RF_BELEG.
To make documentation more secure you could run RFBNUM00N once a month.
If you find any missing document-numbers, you could check them via SM13
Please review note 19050: Customizing activities may occasionally change a program to be carried
out after number assignment. As this happens while the program is
running, termination occurs (for example during output determination.)
For using report RFBNUM00N, please also have look at note 148757.