Skip to Content
avatar image
Former Member

Document Condition number in Billing document are not in sequence.

Consider two Billing documents 11 and 12. The Billing document 11 was created first and then 12. The document condition number for Billing document 11 is 22 and for 12 is 21. The doc condition number are not in sequence. This is creating a mess in our Billing Report where we try to sort the Billing document number using Doc. condition number. Can someone tell me in what cases this issue occurs? I am trying to replicate the scenario in testing system but not able to do so.

One reason I have noticed in production system when Billing document 12 is release to accounting first before 11. But I am unable to replicate same scenario in testing system.

Please help me to understand the issue. Thank you!

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    Apr 07, 2016 at 05:41 AM

    RV_BELEG is delivered not buffered in standard, but at least in the systems in which I can check, KONV is buffered in main memory.

    Maybe a colleague from your BASIS team can help you in reproducing the case in the test environment.

    Your PRD is probably with more than one application servers, while DEV/QA can be with just one for example.

    The reason I mention that is because in note 1679514 there is the following text:

    If you use several application servers, the numerical sequence will not reflect the (chronological) insert sequence because the numbers are buffered separately on the individual hosts

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 06, 2016 at 01:44 PM

    Interesting case. In programming sequence Document number (Vbrk-vbeln) gets populated before Condition number (Konv-knumv), so one would expect of two billing documents, the older one should have the older (smaller) condition number.

    Are billing document creation dates the same? Is there another billing document wedged in between, or are 11 and 12 in line (For ex: For 11, vbrk-vbeln = 90001422, and for 12 vbrk-vbeln = 90001423).

    If numbers are in line, and creation time difference is very small, I would suspect a delay while processing 90001422 might have caused the system to give next condition number to 90001423. It's a long shot, but that might be the cause of this strange behaviour.

    P.S: Release of billing document to accounting does nothing to do with this, as condition number gets generated even if billing document is not released to accounting.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for your reply. I have checked the system and found 90001422 was created at 08:46:40 and 90001423 was created at 08:53:19. Both were created on same day.