FI_DUPLICATE_INVOICE_CHECK

I am trying to use this function call and am having trouble when the program comes back from the call. I use the debugging tool and it shows me the duplicate message - but within the program there is not a return code or anything that I see that will allow me to display the duplicate message. Can anyone help???
Thanks

Hello,
You can copy the existing message number to new message number and also include the amount.
then the same can be assigned OBA5 with E. This time the system checks for amount combination also.
Regards,
Ravi

Similar Messages

  • Duplicate check for non inventory vendor invoices in Finance

    Hi,
    SAP provides duplicate check for non inventory vendor invoices posted through transactions F-43 and FB01 etc. The field values checked for duplicate invoice include Document date and Reference field.
    I want to know, is there any flexibility of removing Document date from checking criteria?
    This is to facilitate picking more invoices in duplicate check net.
    Regards,
    Vijay

    Dear Vijay
    Yes, you can control this via business transaction events. Please review the below explanation.
    In Rel 4.6, duplicate invoices are checked using function module
    FI_DUPLICATE_INVOICE_CHECK which is called when invoices are posted via trans FB60.  Duplicate invoice checking criteria can be customized using the open FI interface SAMPLE_PROCESS_00001110 (custom function module) starting from Rel 4.6.  Please verify if the open FI interface 00001110 is being used in your system and review duplicate invoice selection criteria via trans BERP. You may wish to omit the document date (BLDAT field from the duplicate invoice check criteria to trigger error msg F5117.  In addition, table BSIP (vendor duplicate documents) may need to be updated.  (see note 114563 for further info).
    Please also check note 537213, and note 31771 for your information.
    If this helps please reward with points.
    Best Regards
    Kesav

  • Urgent! Sales-related item?

    Does anyone know where the field XUMSW (sales-related item) is checked when posting a vendor(yes, actually)  invoice (FI-AR invoice)? Me and two co-workers are debugging a program when parking an invoice in FV60, and are about to come to a solution on an existing problem.. This field information is very important, but unfortunately a black hole for us.
    Thanks,
    Eaj

    Thanks.
    To be more specific; when is this indicator checked in the first place?
    The function modules FI_DUPLICATE_INVOICE_CHECK checkes <i>if</i> the indicator is checked. But we need to know at what point the indicator is set in the first place.
    CORRESPONDENCE_REQUEST/CORRESPONDENCE_REQUEST_POSTING unfortunately isn't relevant.

  • FMs to Check for Duplicate FI Invoices

    Std FMs to check whether a FI invoice is parked or posted.

    Hi
    Use the FM:
    FI_DUPLICATE_INVOICE_CHECK
    Regards,
    Sreeram

  • Double Invoice Check Failed-Trax FB60/FB65

    Dear Sap Gurus,
    When iam posting invoice by using FB60 it is allowing duplication.iam able to post two invoices with same data.system is not giving any error. how to get error messages. i have done all necessary settings
    1.vendor master double invoice check is activated
    2.ob41 -posting keys -Sales related check
    any input in this regards is highly appreciated
    regards,
    siva

    Hi,
    FI_DUPLICATE_INVOICE_CHECK which is called when invoices are posted
    via trans FB60. Duplicate invoice checking criteria can be customized using the open FI interface SAMPLE_PROCESS_00001110 (custom function module) in Rel 4.6,
    Duplicate check looks also at the reference field in the header where you input the invoice number.
    Assign points in reply to thanks

  • Stop Parking same document twice

    Hi,
    How to restrict parking of same invoice twice against a Purchase Order.
    Please advice.
    Thanks

    Hello,
    Maybe you could try to add sale order into FM:FI_DUPLICATE_INVOICE_CHECK for modifing the standard system behivior.
    Best Regards,
    Gladys xing

  • Double invoice entry at the FI Level

    Where do I go in the FI level not to allow double invcoice entry.
    Thanks
    AG

    > Csaba Soltesz,
    > Could you explain both:
    > How do I set up the FI_DUPLICATE_INVOICE_CHECK
    > validation and also how to do it for MIRO
    > transactions.
    > I would appreciate feedback.
    > Thanks
    > AG
    Hi Ana,
    sorry for the late reply.
    For the FI check, there is no specific setup. Only thing you need is to set the corresponding flag in the vendor master (company code view). Then, if the prerequsites are met (see below), a warning message will appear.
    How the check is working in FI? (ie., FB01, FB60 or similar, NOT logistics invoice verification, for LIV, see below):
    1. Is this a vendor line (account type K)?
    2. Is the flag set in the vendor master?
    3. Is the line item sales relevant (based on the posting key, e.g., 31 is sales relevant, 25 is not)
    4. Is this a normal document? (not recurring, parked, clearing, sample doc)
    5. Do we know the document currency?
    6. Do we know the document date?
    7. Is the amount in document currency <> 0?
    If the answer to all of the above was YES, then the check is carried out. What is actually checked, is table BSIP. Every time when you post a document meeting the above criteria, BSIP will be updated. Next time the BSIP entries are checked.
    And here the checking rules:
    IF the reference field (BKPF-XBLNR) is filled in, then the message is issued when there is a BSIP record already with the same:
    - company code
    - vendor number
    - document date
    - reference
    - document date
    - D/C indicator
    IF the reference field is NOT filled in, in addition to the above, the amount in document currency is also checked in BSIP, so that field must match too in order to get the message.
    The message is F5 117 and the type can be changed in customizing (view V_T100C) as usual for customizable messages.
    The above list also answers another question in this thread: NO, it is not possible to check it cross company code. I.e. if you have entered an invoice for company code A, then you can enter the very same invoice for company code B, there will be no message at all. You need to create some validations (transaction OB28) to achieve this. The standard check is working within the same company code only, see the list above.
    Now,  that was the pure FI thing, how about Logistics Invoice verification (MIRO, etc.). Here, you have some more configuration options. The function module called here is MRM_FI_DOCUMENT_CHECK.
    The check in Logistics Invoice Verification is carried out only if the below criteria are met:
    1. Reference field is filled in (!!!!! extremely important!!!!)
    2. This is an invoice (and not a credit memo... see RBKP-XRECH must be X)
    3. The vendor number is known
    4. The flag is set in the vendor master (company code view).
    The check is made against BSIP again, but WHAT exactly is checked, i.e., which fields must match, is customizable. In table T169P, you can tell the system which fields you want to consider as indicators for a double invoice entry. You can choose from: Reference, Company code, Document date.
    Here is part 2 of the answer to the previous question: YES, Logistics Invoice Verification can be set up in a way that invioces are checked cross-company code. If you do NOT mark the field company code, than this field is not checked, and the same invoice cannot be entered for 2 different company codes.
    First, the system tries to find a BSIP record with the same values in the fields below:
    - Vendor number
    - Document currency
    - Amount in document currency (this only if Reference is NOT ticked in table T169P)
    - Company code (only if ticked in T169P)
    - Document date (only if ticked in T169P)
    - Reference (only if ticked in T169P)
    If there was a BSIP entry found, message M8 108 will appear as a warning. Again, you can change the msg type to error if you like (user-specific).
    Also, Logistics Invocie Verification can be a 2-step procedure: first, the invoice creation (entry in table RBKP) and second, the posting of this invoice to Accounting (entry in table BKPF). In most cases, this happens in the very same moment when you press Save in MIRO, but it could be also set up in your company that you do these 2 steps separately.
    That's why after the posted invoices (BSIP) were checked, the system tries to check the invoices not yet posted to Accounting (invoice document status is "Not yet posted"). This is to make sure an entered but not yet posted invoice is also checked early enough. Basically the same fields as above are checked, but the message is a different one: M8 642. Default type is warning, changeable to Error if you like.
    Hope that helps, points welcome
    Csaba

  • Std FM for Duplicate invoice posting

    Hi All
    Can any one send me the standard function modules which checks whether the INVOICE is parked or posted. (combination of company code/vendor/doc date/ref).

    Hi
    Check whether this can help for u
    FI_DUPLICATE_INVOICE_CHECK
    FI_DATA_FOR_SELF_INVOICES
    FI_DATA_FOR_SELF_INVOICES_CALL
    Regards,
    Sreeram

  • Duplicate Invoice Check for Transaction FB01 or similar transactions

    The standard function module FI_DUPLICATE_INVOICE_CHECK will check whether an invoice/credit memo has already been posted where all of the following attributes match: Company code, vendor, currency, document date, reference number (If a reference number was entered in the current invoice/credit memo). If no reference number was entered in the current invoice/credit memo the system checks whether an invoice/credit memo has already been posted where all of the following attributes match: Company code, vendor, currency, document date, amount in document currency.
    The above functionality described in the short description doesn’t provide for the need within AP to check on duplicate invoices. The functionality in FI differs from the functionaltiy provided in LIV and therefor needs to be aligned. The risk of posting duplicate invoice entry is eminent since the check is dependent on all parameters. For a good duplicate invoice number check we need FI to check on Vendor and invoice reference within the same fiscal year. To modify rules, copy FI_DUPLICATE_INVOICE_CHECK, modify the checks and then call the copied function module from FB60. The remaining field check in the standard function module should be deleted.

    Exactly what is my requirement is standard function module checking based on some parameters. In this requirement different way to check this process.

  • Duplication of invoice- please help

    frnds
    i posted one invoice with invoice date 04/18/2007, reference 2900 and cocode xx80
    vendor 123909
    i tried to post another inovoice with the same informaiton except invoice date which is 04/18/2007, it allowed me to post, shouldnt it stop me to post the inovice as reference and co code and vedor was the same?
    i had following settings at OMRDC 1. co code was checked 2. reference doc no was checked 3. invoice date was not checked.
    how can i stop the above entry?
    please let me know
    thanks

    Source: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/sap+solutions&
    <b>Duplicate Invoice Check</b>
    In which cases a check for double invoices is run through (prerequisites)? Which function module is relevant? Which fields are relevant?
    Solution/Answer:
    Prerequisite:
    If the field 'Chk double inv.' is marked in the vendor account.
    The Function Module name is FI_DUPLICATE_INVOICE_CHECK
    It will check
    The following fields must be identical for Duplicate invoice check
         Company code                              (BUKRS)
         Vendor number                             (LIFNR)
         Currency                                      (WAERS)
         Reference number                         (XBLNR)
         Amount in document currency         (WRBTR)
         Document date                              (BLDAT)
    If the document is having any one of the above filed different then the system does not consider it as a duplicate invoice.
    http://help.sap.com/saphelp_47x200/helpdata/en/ce/4f3e39ea3aee02e10000000a114084/frameset.htm

  • Problem with BTE RWBAPI01

    Hi,
    we are receving the Vendor invoices from SEIBEL system through WEBSPHERE using BAPI_ACC_DOCUMENT_POST.
    SInce Bapi allows duplicates we have implimented BTE RWBAPI01 in FIBF to restrict the duplicates.
    in FIBF we gave customer prodcut and not provided any RFC destination, as we have this RWBAPI01 as Process interface we have configured the FM in customer process interface. we used the standard FM logic 'FI_DUPLICATE_INVOICE_CHECK' for this requirement.
    our problem is when ever we are using this BAPI with in SAP this restriction is working fine but when we are receivng the Invocies from WEBSPHERE it is allowing duplicates,
    Please let us know if we are missing any config or what is the use of RFC destination in FIBF.
    Thanks,
    Ram.

    HI,
    It is solved, actually legacy not tested with proper data ther after they confirmed that it  is working.
    Thnaks,
    Ram.

  • Change the standard function module

    The standard function module FI_DUPLICATE_INVOICE_CHECK will check whether an invoice/credit memo has already been posted where all of the following attributes match: Company code, vendor, currency, document date, reference number (If a reference number was entered in the current invoice/credit memo). If no reference number was entered in the current invoice/credit memo the system checks whether an invoice/credit memo has already been posted where all of the following attributes match: Company code, vendor, currency, document date, amount in document currency
    my requirement is
    The above functionality described in the short description doesn’t provide for the need within AP to check on duplicate invoices. The functionality in FI differs from the functionaltiy provided in LIV and therefor needs to be aligned. The risk of posting duplicate invoice entry is eminent since the check is dependent on all parameters. For a good duplicate invoice number check we need FI to check on Vendor and invoice reference within the same fiscal year. To modify rules, copy FI_DUPLICATE_INVOICE_CHECK, modify the checks and then call the copied function module from FB60. The remaining field check in the standard function module should be deleted.
    how  to achive this. i didn't understand the requirement .Please give me any suggestion for this.

    Hi ,
    I think what you are saying is the functionality given in Logistics Invoice verification is not suitable for FI Invoice.
    If I am correct , then there is a configuration setting in SPRO where you set check for duplicate invoice. It has just three checkboxes
    a) Company code b) Reference number c) Invoice date
    so I think this configuration setting will suffice your requirement.
    Please let me know.
    Amit

Maybe you are looking for