INVOICE: Gap in document number assignment

Hi,
on the sap sd system of the customer, executing the RFBNUM00N report they turn out some numeration jumps for the invoices.
The SD invoice range is internal, while the range of the accounting documents is external, therefore the problem should be in the invoice number determination in SD.
The number range object RV_BELEG is not buffered.
This problem has legal consequences.
We work at a release 4.7.
Do you have advices to be given?
Thank you,
Maddalena

Hello Maddalena,
Plz refer to OSS note: 19050.
Also, plz check this thread:
Re: Number range Skip
I hope this helps.
Rgds,
Raghu.

Similar Messages

  • Gaps in Document Number Assignment & Invoice Numbers Allocated Twice

    In Period End Closing Financial Accounting there is Gaps in Document Number Assignment & Invoice Numbers Allocated Twice for day-end closing. I understand the difference between the two, but why is the business process procedure a process decision between the two as opposed to a process flow that includes one after the other?
    T-Codes:
    S_ALR_87012342 vs. S_ALR_87012341
    Thanks in advance for you help!

    The report is used mostly by SOX and Internal auditors to check if there are any gaps in the document number assigment. This could be possible if due to various reasons certain numbers have been skipped and document numbers are not in sequence. Also as per some of the local reporting GAAPs there hsould not be any gap in the document numbers assignment. To ensure all this this report is checked.
    Thanks and regards
    Kedar

  • Gaps in Document Number Assignment

    Hi,
    can somebody tell me what is the exact use of the report " Gaps in Document Number Assignment -S_ALR_87012342"
    In what sort of instances we use this report/?
    Thanks,
    Regards
    Gayani

    The report is used mostly by SOX and Internal auditors to check if there are any gaps in the document number assigment. This could be possible if due to various reasons certain numbers have been skipped and document numbers are not in sequence. Also as per some of the local reporting GAAPs there hsould not be any gap in the document numbers assignment. To ensure all this this report is checked.
    Thanks and regards
    Kedar

  • Document number assignment can be found in the critical area (MATNRUnknown)

    Dear all,
    Pls advice me to resolve mention error which is pertaining to msg no -vf205 in sap.
    while creation of idoc associated document (article and billing) is not generating by our system. when ill see the error its showing "upper limit of number range is exceeded" but in spro in not exceeding.
    kindly advice .
    Regards
    Sunil kr.savita

    dear raju,
    we dont want to increase upper limit coz document  no generated by system is within the no. range limit .
    but when we double click on this error its showing.
    Document number assignment can be found in the critical area
        Message no. VF205
    Diagnosis
        Document number assignment for the number range object RV_BELEG in
        number range 49 is found in the critical area.
    Procedure
        You can either increase the upper limit of the number range interval o
        set the current status back. You must, however, make sure that infutur
        no number is entered more than once.
    regards

  • External Document Number assignment using Bapi_acc_document_post

    Hi All Experts and Max,
    We want to post th same external document no using BAPI_ACC_document_post, but we are unable to post thatexternal  Document no.
    Note: If we are posting the same no using transaction FB01 , we are able to post the document , if we are passing the Acc_do_no field as the external Document no.
    Our requirement is to post the document no of the e.g A system to B system with th esame document No .
    Kindly provide what value we need to pass in the obj_type , obj_key and obj_sys fields of BAPI_ACC_Document_post.
    I am aware about the scenario that in case of internal document no creation we will get all these 3 fields from th eBAPI, but we need the values in case of external document no assignment.
    We tried with obj_type as 'BKPFF' but we are not able to post the document with that obj_type, In that case Bapi is clearing the exterbal document no acc_doc_no field in the first subroutine.
    Note: We are uploading a file in different system  with the .dat format and we are using BAPI_ACC_DOCUMENT_POST method.
    Please refer the below link for more issue details.
    Link:[External Document Number assignment using Bapi_acc_document_post;
    Kindly provide the solution.
    Thanks,
    Rahul Sisodia

    Hi All,
    Please suggest if you came across such situation. <removed by moderator>
    Thanks,
    Rahul Sisodia
    Edited by: Thomas Zloch on Sep 19, 2011 10:18 PM

  • CO Document number assignment

    Dear Sir,
    CO document number assignment not possible for business transaction COIN in CO area xxxxxxx And how to assign business transaction COIN to a number range group? How to create a new number range group?
    points will be rewarded

    Hi,
    The number range for CO document is maintained at controlling area level.
    Use T-code KANK for maintaing the number range.
    Regards
    Amit Parkhi

  • Invoice Reduction - Incorrect Document Number Transferred

    I am attempting Total-Based Invoice Reduction on an IDoc that is held up in Invoice Overview.
    As far as I can tell, the document types are correct and the number ranges are correct.
    The RD and RS ranges are pointing to internally assigned numbers beginning with 51 and the RE and (invoice reduction) ZI document types for MR1M are pointing to number range 51 which is external. 
    What can I be missing to get the following error?
    Incorrect doc.no.: $ 2. Select document number between 5100000000 and 5199999999
    Message no. F5151
    Diagnosis
    The document number you specified, "&v1", is not in the appropriate number range. The number range is dependent on the document type.

    It seems that the Invoice Reduction Document Type did not have the correct numbering assignment - it was external when it should be internal.
    In my mind I was thinking the invoice reduction document would be a transfer from MM, but it is not.  It is an internally created financial document so it need an internal document assignment.

  • Report with Invoice and Accounting Document Number

    Dear Experts,
    Here i have a requirement.
    I wanna a report which gives a Invoice (MIRO) and its accounting documents (Follow on document) in one page. Because If I view a MIRO document, for checking the accounting document, I need to click on Follow on doc, then I'll get.
    But If wanna see for 1000 MIRO documents with accounting document number, then I don't want to click 1000 times to see the account doc for respective Invoice number.
    The approximate format is,
    Column 1                              Column 2     Column 3        .......................              Column n
    MIRO  (Invoice number)                             Accountting Doc Number
    5100000099                                              5100000011
    Which tcode will give the both in one screen?
    Thanks in advance
    Regards,
    navahsek

    Hi,
    Enter Sork Key 002 for Vendor Master Record.
    and also you can check the Report in ECC 6.0
    MIR5 - Display List of Invoice Documents
    There you select Export Mode --> Display Accounting Document Number.
    You can get Report FI and MM Document Numbers.
    Hope It will Clear.
    Regards,
    Kishore

  • Document Number Assignment.

    Hi Guru's
    Am a newbee in this mySAP PLM area and have a question regarding Number Assignment.
    I have a small scenario. Company "S" aquired companies A,B,C & D. All companies were following thier own ways of generating new part numbers.Now the task is implement SAP in all these companies and standardise the procedure of generating the part numbers AS PER THE GROUPS.
    Meaning, files belonging to one particular group should start with particulat number. like,
    Assemblies -
    S10XXXXX
    Parts----
    S20XXXXX
    Piping assemblies-------S70XXXXX
    Harness Assemblies----S80XXXXX
    Library Parts----
    S90XXXXX
    Lables etc----
    S91XXXXX etc.
    The same should be followed in all the companies like S, A,B,C & D.
    How to configure this type of numbering system ? I guess I should use mixed numbering , am I right ? Once done in SM, how normally it will be rolled out in other plants ?
    Please suggest.
    This may be a very basic question in DMS, but a clear answer for this will be really appriciated.
    Thanks,
    S.Achar.

    Hi Achar,
    in case you want to use such kind of document number, you should customize value '3' or '4' in the field 'Number Assgmt' in transaction DC10 for your document type. This kind of number assignments will also check the logic in BADI DOCUMENT_NUMBER01. Further you would have to create your own number exit and replace the standard program 'MCDOKZNR' with this own individual number exit program.
    Within your own number exit you can define your individual logic for the generation of your document numbers. For further information please see also the small blue info button at the upper right corner at the document type detail screen.
    Best regards,
    Christoph

  • No CO-document number assignment (CO area 2000, activity COIN)

    Hi
    I am getting the above error while issuing the materials against Order( mvnt. type: 261).
    Basically, the error is <b>While maintaining Controlling area</b> the activities like (COIN, CPPA,CPPP,FIPA,KABG,...etc) are not got copied. Now, it is not allowing to copy also.
    I want to create these activities/elements and assign the number ranges to it. So,Can anyone tell me <b>How to create these activities/elements</b>??
    Best Regards,
    Ajit.

    Hi Ajit,
    You can do this in TR code KANK
    Provide your controlling area 2000
    Click on mantain(F6)
    in the menu bar click on group---Insert
    Then provide a text(Controlling Documents) and mantain No range. Lets say from 0000001 to 20000o and save
    now you will see variuos activities like COIN, KABG are there below not assigned.
    Check the box against controlling document range you have created.
    put the cursor on COIN and click on select element(F2) and then click on assign element group(F5)
    And Save
    Reagrds
    Pratiksha

  • Gaps in Document No. Assignments

    Hi,
    We have found the documents in the T.code. S_ALR_87012342 - Gaps in Document Number Assignment.
    when we have open the documents thr FB02 the error message showing:Document 90039905 does not exist in fiscal year 2007.
    what is the problem? How to analyse the documents?
    Please advise me.
    Thanks in advance

    Hi,
    Check the document type used for the SD billing type.
    There may be chances, where FI document number and Billing document number are same.  In sales, billing document type can be configured to use a particular FI document type.  This FI document can not be used for any other puposes.  In this case, Reversal billing document type also should use same FI document type other wise this type of inconsistency will happen.
    For examble,
    If you created a billing type F2 assigned a FI Doc type RE, when ever you post an entry with this billing type, the billing document(0002) as well as FI document(0002) should have same number.
    There may be some chances, where the reversal billing type F2 could be assigned to FI doc type RA, in this case if you  reverse the F2 billing document (0003) in SD, it will create one FI document (0001) with type RA. 
    When you create next billing document (0004), it will consume FI document 0004 not 0003.  In this case, 0003 can not be used as the 0004 is already been used for the fiscal year.
    If this is the case, you don't have to worry. It is like this only can be done.
    Hope it clears your doubt
    Regards
    A.Saravanan.

  • MIRO Invoice document number range to be assigned based on company code

    Hello all,
    We have different company codes in single client and we want each company code have diffrent set of Invoice document number. and seprate number range assignment i.e internal or external
    But SAP standard support Invoice document number assignment based on financial year..
    Please help me, how I can customize this in my system?
    Regards,
    PAVAN

    Hi Pavan,
    I assume you're talking about logistics invoice number (financial invoice number depends on company code as a standard)
    pls have a look at exit LMR1M003 (function module EXIT_SAPLMRME_003).
    I hope this helps. Kind regards,
    Alvaro

  • Invoice & Accounting Document Number

    Dear Experts,
    We are facing number range problem. When we are saveing an invoice then Invoice number and accounting document number showing different. It should come same number. Can you pls advice why this is happening and how I can resolve this issue.
    Thanks in advance for your kind support.
    Best Regards.
    Ripon Kumar Paul

    Dear Ripon,
    Please check the below which will help you achieve same document number:
    SAP gives you customizing options to make both document numbers the same. The solution lies in the number range assignment of the MM and FI document. You need to configure the MM document number assignment as internal and external for the FI documents. (FI documents are set up with external-assigned numbering, while the MM document has internal, or system-generated, numbering.) In this case, the MM document number is passed on to the FI document, which means that the number of the FI document is identical to the MM document.
    Because the document number assignment in MM is not company code-specific, in contrast to the FI document, you need to take the following points into consideration before using external document number assignments for FI documents. They have the following effects on your system:
    Continuous number assignments for FI documents are not guaranteed, especially if you have more than one company code.
    The document number ranges in MM and FI have to be the same for all company codes.
    In Release 4.6C, you need to use internal number assignments for revaluation documents, invoice reduction documents, Evaluated Receipt Settlement (ERS) postings, or reversal documents. There are no restrictions as of SAP Enterprise 4.70.
    Use a different number range assignment for FI invoice posting (FB60), because FI invoice postings usually use internal number range assignments and the postings originate in FI, not MM.
    If you use document parking and the number range intervals are fiscal year-dependent, you cannot change the posting date of the document if the fiscal year is different to that determined for the previous posting date. In this case you have to delete the document and re-enter it. There are no restrictions for fiscal year-independent number ranges.
    What do you do if you have already posted thousands of invoices in your system and the numbers are already different? In this case, you need to find unused number range intervals in MM and FI. Since most companies do not change the SAP standard delivered number ranges during the original implementation, number range interval 52 is usually available in MM and FI.
    Now let's look at the detailed customizing steps. With the following customizing steps, you can align the MM and FI document numbers going forward only. No fix is available for invoices already posted in your system, since SAP does not allow the change of document numbers.
    Step 1. Maintain FI document number range. Use transaction OMR4 and go to Number range for document types in FI. Select the company code for which you want to create the new number range interval and click on the change interval button. Insert a new document number range by clicking on the insert interval button on top of the screen. In this example, I created number range interval 52 with the document numbers 5200000000 u2013 5299999999. Don't forget to set the external number range check box (Ext).
    Step 2. Assign FI number range to FI document types. The second step is to assign the number range created in step 1 to the FI document type for invoices. Again use transaction OMR4 and go to Document type. Double-click on the document type, which you are using for LIV invoices. In my example, I used the SAP standard document type RE. In the number range field, assign the new number range interval 52.
    Thanks!!!
    Murlidhar Khatri

  • Missing orders in SAP-Gap in number assignment

    Hi All,
      We are facing a situation where there is a gap in assignment of order numbers. We do not have any trace of any failed updates in ST22,SM13 etc. Does this mean that we missed only a "number" and not an order? Is there any other transactions that can give some information on this? Do we have any documentation from SAP that talks of a similar isssue?

    <b>This is report I used for FI = RFBNUM00</b>
    <b>FYI</b>
    OSS note # 62077
    Symptom
    Gaps (jumps) occur when allocating internal numbers.
    The status of the number range does not match the number last assigned.
    The number assignment does not match the insert sequence.
    Additional key words
    Document number, Number range, Number range object, Buffering, Current number level, Trip number assignment, Number interval, CO document, CO actual posting, Inspection lot, Material document, Physical inventory document, Production order number, Planned order number, Process order number, Maintenance order number
    FB01 VF01 KO88 KE21 KE11 FD01 FK01 XK01 XDN1 MB01 MB0A MB11 MB1A MB1B MB1C MB31 KANK KB11 KB13 KB14 KB41 KB43 KB44 KB21 KB23 KB24 KB31 KB33 KB34 KB51 KB53 KB54 PR01 PR02 PR03 PR04 PR05 XD01 VD01 MK01 SNUM SM56 SNRO VL01 VL02 CO01 CO40 CO41 VA01 MR1M MIRO
    Cause and prerequisites
    A large number of number range objects are buffered. When buffering a number range object, numbers are not updated individually in the database, rather, the first time a number is requested, a preset group of numbers are reserved in the database (depending on the number range object) numbers and these are made available to the application server in question. The following numbers can then be taken directly from the application server buffer. If the application server buffer is exhausted, new numbers are generated in the database.
    The effects described under "Symptom" then result:
    If an application server is shut down, the numbers that were left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
    The status of the number range interval reflects the next free number that was not yet transferred to an application server for intermediate buffering. The current number level does not therefore display the number of the "next" object.
    The current number level (per server) can be displayed with Transaction SM56. Start Transaction SM56 and branch into the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
    If several application servers are used, the chronological insert sequence is not determined by the numerical sequence on the individual hosts, due to the separate buffering on the various servers.
    Buffering the number range objects has a positive effect on the performance as no database access (on the number range table NRIV) is required for every posting. Furthermore, a serialization of this table (database blocking) is prevented to a large extent so that posting procedures can be carried out in parallel.
    Solution
    As the number range buffering does not lose any guaranteed attributes, a correction is not required.
    If you still require a continuous allocation, you can deactivate the number range buffering deliberately for individual objects.
    Proceed as follows:
    - Start transaction SNRO and enter the affected object
    - Press the 'Change' pushbutton
    - Deactivate buffering: Menu 'Edit' -> 'Set buffering' -> 'No   buffering'
    - If you only want to change the buffer size, please enter the   corresponding value in the field 'No. of numbers in buffer'
    - Save the changes
    Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - that is, you must check the change manually after every import of a maintenance level.
    For the the following number range objects, gaps may cause user insecurity as a sequential numbering is 'expected':
    Area CO:
    - RK_BELEG   (CO Document)
    Caution: Note that the problems described in notes 20965 and 29030 can occur if you deactivate the buffering.
    - COPA_IST   (Document number during actual posting)
    - COPA_PLAN  (Document number with planned posting)
    - COPA_OBJ   (Business segment number)
    Area FI:
    - DEBITOR    (Customer master data)
    - KREDITOR   (Vendor master record data)
    Area HR:
    - RP_REINR   (Trip numbers)
    Area PM, PP, PS
    - AUFTRAG    (Order number, Production, Process, Maintenance order
    number, network number.)
    - QMEL_NR    (Number range message)
    Area MM:
    - MATBELEG   (Material documents)
    - MATERIALNR (Material master)
    Area QM:
    - QLOSE      (Inspection lots in QM)
    - QMEL_NR    (Number range message)
    - QMERK      (Completion confirmation number)
    - QMERKMALE  (Master inspection characteristics in QSS)
    - QMERKRUECK (Completion confirmation number of an inspection
                 characteristic in QM results processing)
    - QMETHODEN  (Inspection methods in QM)
    - ROUTING_Q  (Number ranges for inspection plans)
    - QCONTROLCH (Control chart)
    Area Workflow:
    - EDIDOC     (IDocs)
    Number range buffering can be activated or deactivated at any time.
    Number range objects that must be continuous due to legal specifications (for example RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered with the buffering type 'Main memory buffering'. Please see also notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
    Source code corrections
    Thanks
    SK

  • Gaps in customer number range

    Hi SAP Gurus
    We have been reviewing our customer master data and noticed that a series of GAP in our customer number range.
    Please could anyone advise on what is reponsible for this and how it can be fixed.
    Thanks, Felix

    Hello Felix,
    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

Maybe you are looking for

  • HT5628 Security after Boot Camp 5 / Windows 8

    After installing Windows 8 using Boot Camp 5 on my MacBook Pro (Mountain Lion), do I need to worry about virus protection, increased vulnerability, etc. on either side?

  • Goods return without quality inspection

    Dear Friends , I wants to do material return without quality inspection , is it possible , how can we do this. Regards, Mahesh.

  • Trouble with iCloud Contacts & Calender / duplicates from system failure

    Duplicates do appear on iPad Contacts and even duplicate birthday entries. Even on iCloud.com the birthday entries are duplicate. The problem is when you delete a duplicate contact on iPad you lose both! Check on iCloud.com if the contact is really a

  • Need user's manuals document for my Satellite L645

    Hi I need users manuals for my notebook. I bought it in Asia but unfortunately I dont have manuals for it. Ive already searched it on toshiba page but I cannot find it. Who can help me? My notebook model is Satellite L645. Thanks in advance +Message

  • Hi iam very new to OBIEE

    1.Can any one clarifies my doubts ..what is the differnce between Fact table LTS and Dimension LTS and if we have multiple Dimension LTS how we need to define ? 2. What is the use of Bridge tables? 3. what is the use of views and is it possible to gi