on 02-27-2009 5:20 PM
Hi,
As per my understanding, number ranges are assigned internally by the system for the billing document. Then how is it possible to miss one number inbetween.
EG: i have a billing document with number 12,14,15, what happened to billing document number 13. Please clarify under waht all sitaution a number is misssed though the number rangea are perfectly set.
This is a high priority issue for us. request your help.
Hello Prithika,
There are a number of reasons why gaps in invoice numbers may occur:
1. Object RV_BELEG is buffered. In this case the performace is improved
but this gaps are produced.
2. Update terminate/shortdump occures while billing document update.
- the number is set in to the invoice at the beggining of the program
If an interruption of the process happens after the assignation of
this number, the number has run in the range and cannot be recovered.
Update terminations in transaction VF01 and VF04. The billing
document number is reserved prior to the update. After a possible
update termination, it cannot be used again. Update terminations are
displayed in transaction SM13. At present, there is no possible
solution.
3. Incorrect userexit, eg.in Program RV60AFZZ, USEREXIT_NUMBER_RANGE.
Please check the following notes in order to solve this incidence:
175047 Causes for FI document number gaps (RF_BELEG)
19050 Gaps in document number sequence for billing docmt
23835 Buffering RV_BELEG / Number assignment in SD
As you might need to answer to the auditor on the gap of the invoices,
report RFBNUM00 from note 175047 will help you to display
document number gaps to the auditor if in your country the FI document
numbers must be assigned continuously. You use this report to document
the number gaps and the auditor will accept it.
We know that in different countries you have to explain document gaps
to Legal Authorities. For this reason there is report RFVBER00 to
document gaps occured due to an update termination.
As I already stated above report RFVBER00 does only list update
terminations that are not older than 50 days (or according to what time
is maintained in your system). So it could be that this log has already
been cleaned up. It is necessary that these update terminations are
documented before the 50 days expire.
Or a second possibility is that the gaps occured NOT due to an update
termination. Gaps without update terminations be (easily) explained.
They can be (only) detected via report RFBNUM00. Report RFBNUM00 display
these document number gaps for the number range object RF_BELEG.
Thanks,
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Pl check whether any number range buffering is done in the system. In all probability this could be the reason.
Murali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There may be some dump or system down for which this number is missed.
To have a continuous series, you need to create an invoice with the missing number 13. Reset the number range and make the current number as 12 and create an invoice and again reset it to the previous one. Please make sure when you are doing this activity nobody is doing vf01/vf04 to avoid duplicate numbers as you need to only create one invoice with number 13.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prithika
Welcome to SDN forum
Coming to your problem , i suppose that the number range is suddenly jumping , which should not happen ,so as the number as got missed from your series , you should consult with the BASIS consultant and explain the problem. So that he will check where the number range is getting problem , and also check wheather there is any problem from there side
Regards
Srinath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.