Skip to Content
author's profile photo Former Member
Former Member

Duplicated invoice issue happened

Dear Experts,

Let me ask you what would be the root cause of duplicated invoice issue.

1. Symptom:

Recently, I found our system had 2 duplicated invoices which have same data except their document number.

- Their document number are sequential; Billing no#1 with account document#1 & Billing No.2 with account document No2.

- They even have same posting date & document entry date (Entry & posting date: 26th October for both billing)

(But their entry time were different from each other, about a minute gap)

This is abnormal case.

As you know, normally,

once a delivery document is fully invoiced, it can't have any further invoice.

2. Reproduction result:

Currently, I can't reproduce the same symptom due to error message "Delivery doc#xxxx is fully invoiced...".

3. New type of duplicate invoice issue:

And release # of our ERP system is #606.

So, this is not related to notes#217157 which was corrected since release# 4.7

4. Other considerable factor:

And in this situation,

one of my colleague suspects the entry date / posting date of the firstly created invoice(called No1 in the above) is not correct data.

Cause, in the middle of November, there was system down time for monthly-Service maintenance.

And sometimes duplicated invoices can be created

if there's pending invoice data in some kind of SAP-queue which is temporary memory area

(I'm not sure what exactly this mean in technical point of view)

The following is his scenario:

i) On 26th October, sales person tried to create the first billing,

but there was something wrong so that the invoice & its account document had not been stored to DB.

instead, it had been stored to the Queue of ERP system.(Let's call this 'Billing No1')

ii) At this moment, the user regarded the first trial was failed

and there was nothing new in the document flow. So the user retried to create billing and succeed.(Let's call this billing No.2)

The billing No.2 & its account document had been stored to DB as normal.

iii)With above operation history,

our monthly-closing of October had been finished as normal

(There was no data inconsistency in sales performance report at this moment)

iv) In the middle of November, our BD did the service maintenance job

so that the pending invoice No1 & its account document could be created with past-entry&posting date.

v) In the monthly closing of November,

the duplicate billing No.1 & its account doc can be found

both SD-document flow & FI-G/L account balance display(t-code FS10N).

Do you think the above scenario is possible?

If so, how could be the billing No.1 inserted to the queue?

Thnaks in advance...

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Dec 03, 2015 at 01:30 PM


    The general behavior of system is once the Number Range is forwarded, that is by any change of Invoice No. 1 is not created and Number Range is skipped, it cannot be reused automatically.

    I mean say due to any reason, Number Range 1 is skipped then the next Invoice Number be 2 and later on there is no automatic way to create an Invoice with number 1.

    Thus even if Invoice number 1 was in DB queue and created in middle of November, it cannot have number 1 and also accounting document as sequential number range.

    This seems to be some other system update error. Probably your Basis consultant would be in a better position to explore this case.

    Also is this the only inconsistency or there are such inconsistencies in other modules too?


    Jignesh Mehta

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Mehta,

      First, thanks for the advice.

      I totally agree with you. Base on the sequential document number & entry time,

      The billing No.1 should be the only one billing for the delivery.

      But unfortunately,

      FI guys said by end of October, the account document of billing No.2 was the only one they could find via G/L account balance display, 'FS10N'.

      And in case of account document of billing No.1,

      FI guys couldn't find it until November

      & currently they can also find the account document on FS10N.

      This is the reason why they thought the billing No1 seems to be created later than Billing No.2

      And for more detail investigation, I'm also co-working with our BC guys.

      But still, we couldn't find out

      how the billings could be created existed just for a single-same delivery document....

  • Posted on Dec 04, 2015 at 10:11 AM


    Please find the document flow of both invoices. You can get better idea. If the reference delivery document of both invoice is different then there is no issue. If delivery document of both invoice is same then we can say i.e system inconsistency. You can raise the same case to SAP.


    Rahul Hande

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Jihoon Jung,

      Thank you for you thread. We are also experiencing the same exact issue that you have described on your thread.

      We also got the duplicate invoices after our monthly shutdown of SAP. We are on ECC 6.0 EHP7.

      We also created a SAP support message and working with SAP, and I am using your thread to convince SAP that we are not the only customer who faces faced this issue.

      If it is ok with you, can you please share the z program that you guys created to access pending data on DB-update Queue. We are also reviewing the sd billing report variant SDBILLDL where we have selected Asyn. updates. It is called in mutiple steps of RV60SBAT.

      Thank you


  • Posted on May 03, 2016 at 02:55 PM


    Please check OSS note 12934- Two billing documents exist for one delivery note.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Bruno Canuto

      Hi Bruno,

      What I took was same as I mentioned earlier in the above:

      "If your symptom happens only after system-shut down,

      i) After every system-shut down:

      Checking 'SM13' DB-update queue(This should be done by your BC guy...)

      ii)If there's any update-request entry exists,

      BC guy informs the relevant module guy(SD,MM, etc) whether they can remove the entry or not."

      This kind of manual checking is the only solution for my customer.

      And if you have any more question, please feel free~


      Jihoon Jung

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.