BTE for Duplicate invoice

Dear SAP gurus,
We are on ECC 6.0.  We are trying to use BTE 1110 to build our logic for duplicate invoice.
We have activated it in FIBF by copying the sample process, but it is not getting triggered while doing any vendor invoice posting.
Please adv
Thanks!!

Refer the below link:-
[http://wiki.sdn.sap.com/wiki/display/Snippets/BusinessTransactionevents(BTE)]
Regards,
SDNer

Similar Messages

  • Problem in Set Check for Duplicate Invoices

    Hi,
    I have did all the required setting s for check duplicate invoice , but when i do miro , its not giving any error or warning msge.. i did all the config  as per blw link..
    FYI-  in migo, i have entered the 3434 as a invoice ref # in delveriy note column and while doing miro , i have entered 3434 in ref column and give the 3434 as a dlvery note # in item tab .. but its not giving any error?
    Pls guide, where the mistake has gone wrongly??
    Problem in Set Check for Duplicate Invoices
    Edited by: UJ on May 15, 2009 1:45 PM

    Hello,
    Hope you have done all the required configurations for the checking of double invoice and ticked the vendor for the double invoice checking in vendor master record.
    You have to understand the way the system does the double invoice check.
    As per the configuration, if the system identifies an invoice for a vendor whose double invoice check is activated, at the time of MIRO, system will update a separate table.
    So system will check for the double invoice entry among the invoices entered after making the tick in the vendor master.
    i meant to say that, if you are introducing this double invoice check in between the transactions, the check will be valid only for the invoices entered after the activation of double invoice check.
    Regards

  • Set Check for Duplicate Invoices.

    Hi,
    what is the difference if is set "<b>Set Check for Duplicate Invoices</b>"
    in MIRO?
    Best regards

    HI,
    This check will prevent incoming invoices being accidentally entered and paid more than once.
    You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice.
    The company code check makes sense if you work with more than one company code.
    Depending on the reference document number entry, the system checks as follows:
    1. If you have entered a reference document number, the system checks whether the invoice matches in the following attributes:
    Company code
    Vendor
    Currency
    Invoice date
    Reference document number
    2. If you have not entered a reference document number, the system
    3. checks whether the invoice matches in the following attributes:
    Company code
    Vendor
    Currency
    Invoice date
    Amount in
    document currency
    Depending on the system settings, a warning message or an error message appears if the system finds an invoice that matches all attributes.
    Requirements
    The field Chk double inv. (Check for duplicate invoice) must be flagged on the Accounting view in the vendor master record.
    Regards
    Aasif

  • Check for duplicate invoices and trigger a workflow

    Hello All,
        I have a requirement to check for duplicate invoices in AP(Accounts payable) and trigger a workflow when duplicate invoices are found. I a not sure how to do any of the above. Please  let me know if you have any information on:
    1) Checking for duplicate invoices in AP
    2) Trigger a workflow
    Are there any standard workflows that checks duplicate invoices?
    Thanks.
    --Mithun

    Hi MD,
    I doubt if system gives an error on FI side when a duplicate invoice is posted.
    I feel you would require a BAdi for it, where you can call your WF using FM SAP_WAPI_START_WORKFLOW.
    Hope it helps.
    Aditya
    P.S also ask your Func Consultants, if there are any settings in the Customization, where you could capture Inv Dt, Inv Amt, Vendor, Company code.
    Edited by: Aditya Varrier on Oct 15, 2008 9:38 AM

  • Validation for Duplicate Invoice Entry

    Hi Everyone,
    Currently, it seems that SAP reviews an incoming invoice for reference field (invoice number), invoice date, vendor and company code.  If the comibation of the criteria are met, then a warning message appears stating to review the entry due to a possible duplication.  I've since changed the warning message to an error so that users can not post the duplicate invoice. 
    Now, what is the process of stopping an invoice from being posted that meets the following criteria: (1) vendor, (2) invoice number, (3) amount.  Would this be a validation formula or some sort of user exit or is there standard SAP IMG that can be performed?
    Thanks for the assistance,
    Pete

    hi Peter,
    this should be a substitution exit, should happen in FI, on line item level (check transaction GGB1), for all vendor credit postings (posting key between 31 and 39). The substitution has to be done on field amount (WRBTR), because this is the first point where you have all information you need (I guess the vendor invoice number is saved into header). You have to write a small code in the exit to select possible vendor invoices from BSIK and BSAK. If any found you should issue an error message and block the process.
    hope this helps
    ec

  • User exit for duplicate invoice in MIRO and FV60

    HI
    i want to find a user exit to findout the duplicate invoice from MIRO, F-47, FV60 (Parked Invoice), MR8M (Credit Memo).
    please let me know if you know any user exit for this.
    Thanks & regards
    Naresh

    Hi,
    for each transaction code so many user exits are there it is diffecult to pase all the user exits here
    check below link  and run the program in se38 and give the transaction code you get the user exits for each transaction code.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/find%252bapplication%252bclass%252bwith%252bexits%252band%252bbadis%252bfor%252ba%252btransaction
    Regards,
    Madhu

  • Invoice block for duplicate invoice

    Hi Sappers
    I have an issue with customer trade billing.
    We have a scenario where in all the Third party items, once invoice is received, billed to the trade customer automatically. In one scenario we received a duplicate bill from the vendor, which further resulted in two bills to customer. Definately the A/P blocked the bill for payemnts as delivery quantity had exceded, however the customer invoice couldn't be stoped.
    Can any think of an solution to this...
    Regards
    Ranjeet

    Ranjeet Rajendra Jain wrote:>
    > Hi Sappers
    >
    >
    > I have an issue with customer trade billing.
    >
    > We have a scenario where in all the Third party items, once invoice is received, billed to the trade customer automatically. In one scenario we received a duplicate bill from the vendor, which further resulted in two bills to customer. Definately the A/P blocked the bill for payemnts as delivery quantity had exceded, however the customer invoice couldn't be stoped.
    >
    > Can any think of an solution to this...
    >
    > Regards
    >
    > Ranjeet
    Hi
    Check your item category configuration , if you have set Relevance for Billing to *F* , then this problem can be solved.
    Regards
    Krishnakumar Surpur

  • User exits or BTEs for vendor invoices

    Hi,
    Can any body tell me the common user exit or the BTE which will applicable for the transaction codes
    'FB01', 'F-90', 'FB01','FB60','FB65','FV60','FV65'.
    I need only the common user exits across the above transaction codes.Because i know the user exits individuvally for each transactions. But i need to some validations which will be common across all the above transactions.
    Thanks.

    Hi,
    For doing enhancement using BTE,
    Go to Tcode FIBF ---> Environment > Infosystem(Processess)->Execute it.
    You will find the list of all BTEs.
    hope it helps you.

  • 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

  • Custom Table for Verifying Duplicate Invoice against Legacy Invoice Data

    Hi All,
    We are trying to upload legacy invoice data in a custom table. Then we want to use SAP duplicate invoice check functionality to look for the potential duplicate invoice from this custom table as well apart from the standard SAP tables.
    If you know of some user exit or any function module which I can use to link this custom table with the standard SAP duplicate invoice check functionality then it would be of great help.
    Regards,
    Sanjay

    Hi Jurgan!
    Thanks for the reply,
    We are using ECC6,
    Support pack : SAPKH60013
    Settings for Duplicate Invoice Check In Vendor Master is correct
    Customization setting OMRDC transaction, tick mark for invoice reference no. only
    If all the cited characteristics match, the system displays a
    customizable message. M8462 (if logistics invoice documents are found) or M8108 (if accounting documents are found).
    I have ensured that message M8108 (if accounting documents are found) is maintained as an error message in OMRM.
    Still system is allowing duplicate invoices for the reference nos. 00082 and 00072.
    For other reference Nos. which are previously used for other documents, system issues error message successfully.
    I dont want to delete archived accounting doc. and if I maintaind BKPF entris of this archived doc manually it will create probelm in FI.
    is this happen due to life span of secondory index of archived accounting doc. is completed ?.
    Please Help
    Many Thanks
    Vikas

  • Duplicate Invoice Check for Transaction MIR7

    Hi Experts,
    My client requirment is .
    Currenty system checks the BUKRS,LIFNR,WAERS,XBLNR,WRBTR,BLDAT for duplicate invoice this is a standard SAP functionality for T.code MIR7.
    Logic needs to be changed
    Duplicate Check in SAP for Vendor invoices to only check Vendor number (LIFNR) and Reference number (XBLNR).
    I have found a function module which is used to through the error message CUSTOM_MESSAGE is the FM under  MRM_FI_DOCUMENT_CHECK. advise what can be done for this.
    Thanks,
    vikas

    Hi Nabheet,
    BSIP is the table which is used for the Vendor Duplicate invoice check.I can do the validation based on xblnr and lifnr for my requirement but i am not sure where i have to do the validations. Please suggest.
    Thanks,
    Vikas

  • Reject duplicate References for Vendor Invoices

    I have a requirement to check for duplicate invoices. I have put in the neccesary config to make the reference Field mandatory, I have also checked the 'Check duplicate Invoice" field in the vendor master and the 'set check for duplicate invoice' in Logistic Invoice Verification (IMG). All this works fine if I enter the same invoice reference, date, amount and company Code. but if I change the invoice date for example, the system accepts the invoice. I dont want this- I want the system to reject the invoice if if has the same reference  irrespective of other parameters. that is, the control should be on the reference field (the same kind of control we have by making VAT reg No REQUIRED in the vendor master). How may i do this please??

    Hi Joe,
    Can you let me know you are posting PO invoice or non PO Invoice.
    Thanks,
    Venkatesh

  • How do i check ensure that SAP checks for duplicate vendor invoice numbers?

    Hi Experts -
    How do I verify that SAP checks for duplicate vendor invoice numbers and blocks duplicate invoices from being paid?
    Thanks!

    Hi
    Pls chek the settigs by following the path
    IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoice.
    Here you make the settings for creating a duplicate invoice check.
    Moreever, in the vendor master, you need to tick the check box for duplicate invoice check.
    I suggest you search the Forums before posting a query. There are lots of postings on this issue.
    Thanks & regards
    Sanil K Bhandari

  • Validation for duplicate AP invoice

    We would like to prevent duplicate AP invoices from being posted through FB60.   We created an FI validation in OB28 in which the prerequisite = Tcode FB60, and the check is a user exit to check the values in vendor / company code / reference fields and if those 3 fields have the same values as in an existing document, to generate an error message preventing the duplicate document from being posted.
    The above works well for creating new invoices.   However, when we have to make changes to an existing invoice (created through FB60), the system also calls on that validation and generates the error message, even though the only fields we can change on the invoice is payment terms, payment method, payment method supplement and text. 
    Other than modifying the user exit, does anybody know of a better way to do this validation or to prevent duplicate manual invoice from being created?  
    thank you.

    This has already been answered before so extracted part of the reply
    there are two duplicate checks in SAP:
    1. the one for FI documents, this is relevant for all F... postings (but nor for MIRO!)
    this can be turned off or on (in vendor master record) and 6 fields are checked:
    Check Flag for Double Invoices or Credit Memos
    Indicator which means that incoming invoices and credit memos are checked for double entries at the time of entry.
    Use
    Checking Logistics documents
    Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
    Checking FI documents
    The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
    Checking Logistics documents
    In checking for duplicate invoices, the system compares the following characteristics by default:
    Vendor
    Currency
    Company code
    Gross amount of the invoice
    Reference document number
    Invoice document date
    If all of these characteristics are the same, the system issues a message that you can customize.
    When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
    Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
    No message is issued if you enter a document that has previously been reversed.
    Dependencies
    The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
    In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
    Reference document number
    Invoice document date
    Company code
    This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
    Example
    The following document has already been entered and posted:
    Reference document number: 333
    Invoice date: 04/28/00
    Gross invoice amount: 100.00
    Currency: EUR
    Vendor: Spencer
    Company code: Munich
    You have made the following settings in Customizing:
    The field "Reference document number" and "Company code" are deselected, which means that these characteristics will not be checked.
    Now you enter the following document:
    Reference document number: 334
    Invoice date: 04/28/00
    Gross invoice amount: 100.00
    Currency: EUR
    Vendor: Spencer
    Company code: Berlin
    Result
    Because you entered a reference document when you entered the invoice, the system checks for duplicate invoices.
    The reference document number and the company code are different from the invoice entered earlier, but these characteristics are not checked due to the settings you have made in Customizing.
    All other characteristics are the same. As a result, the system issues a message that a duplicate entry has been made.
    If the "Reference document number" had been selected in Customizing, the system would have checked the document and discovered that it was different from the invoice entered earlier, so it would not have issued a message.
    Checking FI documents
    Depending on the entry in the field "Reference", one of the following checks is carried out:
    1. If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
    Company code
    Vendor
    Currency
    Document date
    Reference number
    2. If no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
    Company code
    Vendor
    Currency
    Document date
    Amount in document currency
    2. the one for LIV.
    this can be customized (as stated above) and is relevant for MIRO (and not for F... postings!).
    Company, Reference and Invoice date
    Set Check for Duplicate Invoices
    In this step, you can configure for each company code if the system is to check for duplicate invoices when you enter invoices.
    This check should prevent incoming invoices being accidentally entered and paid more than once.
    You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice. The Accounting documents are checked first, followed by documents from Logistics Invoice Verification (only incorrect invoices or those entered for verification in the background).
    When checking duplicate invoices, the system compares the following
    attributes in the standard system:
    Vendor
    Currency Company code
    Gross invoice amount Reference document number
    1. Invoice date If the system finds an invoice that matches all attributes, the system
    displays a customizable message.
    If you are entering credit memos, subsequent debits, or subsequent
    credits, the system does not check for duplicate invoices.
    The exception is the Argentina country version, where the system checks
    for duplicate invoices and credit memos.
    If a previously processed document is later cancelled and then entered
    again, no message is displayed.
    Requirements
    The system only checks for duplicate invoices in Materials Management
    if you specify a reference document number when entering the invoice.
    In Customizing (IMG) for Invoice Verification, you can specify that the
    system check the following attributes

  • FV60 and MIRO -duplicate invoice doent chk for diff inv dates

    In ecc 6.0 ,We use FV60 and MIRO  to enter all invoices. We have config (under MM) for duplicate invoice check against  "ref field" only. When we enter an invoice with the same ref field value, it gives error message as expected. However, when we change the date, the error message is gone and we are allowed to create the invoice and post the invoice.
    Pls help

    Hi,
    Check your config for duplicate invoices.  There is another check box for "Check Invoice Date", see if it is checked.  If yes, then remove it and the system should not allow you to post the same invoice with a different date.
    Cheers.

Maybe you are looking for

  • Multi-Camera-Link Vision Acquisition using .avi

    So I'm trying to use two Camera-Link Cameras (JAI CM-200-MCL) with the NI PCIe 1430 frame grabber in order to obtain video of a y-axis tensile testing project, and I'm relatively new to the whole LabVIEW experience. Essentially, I want to be able to

  • I cant sync my new ipod?

    ok will i had any old ipod4 and somrthing happened to eat so a few months past by and i buy a new one on ebay which was yesterday i got it,,today i wanted to put music on it but i dont know whant to do because everytime i conect it to my computer on

  • Disk Space Monitor

    hi I have set up a logical disk space monitor for windows 2012 servers on my Operations manager 2012. The threshold value is 500MB. However, No alert is generated even when my disk has exceeded 500MB. It works when i set the threshold below 100 MB. C

  • Installing desktop version of Story Plus

    When I attempt to install the desktop version of Story Plus, there is a "download error".  The help icon takes me to the Adobe AIR 3 page on adobe.com.  I already have the latest version of AIR installed. How to I install the desktop version?  I have

  • Viewing LR Star Ratings in Bridge

    I thought I would see what happens to LR Star Ratings when the images are viewed in Bridge CS3. The answer I have is inconclusive. On one set of photos that were exported from LR as jpegs, the star ratings show up in the exported photos but not in th