cancel
Showing results for 
Search instead for 
Did you mean: 

Invoice number gaps

Former Member
0 Kudos

Hi SD Guru's

Iam facing this issue in Production client where Invoice numbers are randomly skipping without any pattern.The number range is assigned to only one Billing type which i have checked. Also there is no Number range buffering for the Invoice Object RV_BELEG. Also i have checked that the client does not use LIS so there is no question of any synchronous updating happening.

I have also checked T-code SM13 but it shows no data.

The user does not get any update termination error while creating invoice also.

The user says after creating the invoice when he clicks on Save button the invoice gets saved and the number is generated. But when he goes back and tries to see that invoice in VF02 or VF03, it shows "Invoice does not exist"

SO DOES ANY ONE HAVE A SOLUTION FOR THIS PROBLEM.!!!!!!!!!!!!!!!!

PLZ HELP..................

Regards

Abhijeet

SD

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

may be u have assigned the same number range to any other document type(sales/delivery). say u have assigned a number range from 1-10

may be billing doc istaking 1

delivery doc is taking 2

sales doc istaking 3

revert backif iamwrong.

kiran

Answers (3)

Answers (3)

Former Member
0 Kudos

T.Code: SNRO

Object: RV_BELEG

Go to Change & Check: Number Range Buffering & make it blank.

Regards,

Rajesh Banka

Reward points if helpful

Former Member
0 Kudos

Hi SD guru's

I have already mentioned that THERE IS NO BUFFERING FOR OBJECT : RV_BELEG in my posting.

So does anyone have a solution for this peculiar issue.

Regards

Abhijeet

Former Member
0 Kudos

Hi,

In SD module, the gaps in invoice number may be caused normally due to

two reasons:

- update interruptions - 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,

is no possible solution.

- Object RV_BELEG is buffered. In this case the performace is improved

but this gaps are produced.

Please check the following notes in order to solve this incidence:

175047 Causes for FI document number gaps (RF_BELEG)

23835 Buffering RV_BELEG / Number assignment in SD

19050 Gaps in document number sequence for billing docmt

I am sorry to tell you that there is no way to solve the gaps or to

'refill' the missing invoice numbers.

There is a report RFBNUM00 that shows the gaps regarding the FI-

document numbers.

But for the SD invoice numbers you could do a hardcopy of the update

termination that caused the invoice number gap; this termination can

be seen in the syslog.

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 cannot be (easily) explained.

They can be (only) detected via report RFBNUM00.

Report RFBNUM00 displays these document number gaps for the number range

object RF_BELEG.

Regards,

Murali

Former Member
0 Kudos

murali,

the information is very extensive, i just hope abhijeet is able to solve the issue. But just to say immediately after an invoice is saved it takes a little while to display in even in VF02, because at the backend so many tables need to get updated which takes some time.

Thanks

former_member227476
Active Contributor
0 Kudos

dear abhijeet,

The problem is due to buffering of number ranges.

please check OSS Note 141497 Consulting: Buffering of number ranges.

reward points pls

siva

Former Member
0 Kudos

HI Abhijeet,

It happens if system fails to update the data in VBRK.

Check in ST22 or short dump analysis .. and find the reasonf for the dump..

i blv the options i thought abt this probl is that only..

check again correctly..

Reg

Shan1242