Control of duplicate invoice posting at T.Code FB70

Dear Experts
As per clients need to we need to control with error message when user trying post duplicate customer invoice at T.Code FB70.
we request your help on how do we can meet this requirement.
if any body know the relevant application areas for message control, pleas let me know. 
I tried with application area F5, but it is not working for customer postings.
Thanks in advance.
Best regards,
S. Habib Pasha.

Hi,
I used this validation for vendor invoice.
$$1 is the document number, which is about to be generated after passing through this validation.
So far as the check part is concerned, I used user exit form and coding in program ZRGGBR000, which is a copy of standard program RGGBR000. The coding is as follows-
exits-name  = 'U300'.
  exits-param = c_exit_param_none.        "AP Duplicate Invoice Check.
  exits-title = text-104.                 "Posting check
  APPEND exits.
FORM u300 USING b_result.
*****Local Variables
  DATA:    l_bukrs   LIKE   bkpf-bukrs,  "Company Code
           l_belnr   LIKE   bkpf-belnr,  "Doucment Number
           l_gjahr   LIKE   bkpf-gjahr,  "Fiscal Year
           l_buzei   LIKE   bseg-buzei.  "Number of Line Item
  b_result  =   b_true.
  SELECT  bukrs
          belnr
          gjahr
     FROM bkpf
     INTO (l_bukrs, l_belnr, l_gjahr)
     WHERE bstat = bkpf-bstat
       AND xblnr = bkpf-xblnr
       AND stblg = ' '.
    IF sy-subrc = 0 .
      SELECT  buzei
         FROM bseg
         INTO l_buzei
         UP TO 1 ROWS
         WHERE belnr = l_belnr
           AND gjahr = l_gjahr
           AND bschl = '31'
           AND lifnr = bseg-lifnr.
        IF sy-subrc = 0.
          b_result =  b_false.
          bkpf-belnr = l_belnr.
        ENDIF.
      ENDSELECT.
    ENDIF.                            "closed for SY-SUBRC
  ENDSELECT.
ENDFORM.                                                    " U300
Regards
K Khatri

Similar Messages

  • Duplicate Invoices posted

    Kindly tell me how can i find the duplicate invoices posted against a single GR if any. which are the tables to be used or is there any standard transaction.

    Dear,
    As per my view two invoice is not posted against same bill number.
    If you want to search it, Please use MIR6 t-code.
    Enter MIR6 t-code.
    Enter bill number in field of reference.
    Then click on Invoice Verification online >> Posted.
    Held/Parked >> Parked as saved and parked as complete.
    Then click on execute button .
    Regards,
    Mahesh Wagh

  • How to block duplicate invoice posting in MIRO

    Hello,
    How to block duplicate invoice posting in MIRO?
    Regards,

    Hi Niteen,
    In addition to the expert's comment use the note 305201
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=305201]
    Please check and revert.
    Thanks,
    Hrishi

  • Duplicate invoice posting due to archived accounting documents

    Hi,
    Duplicate invoice posting is allowing against the below two Invoice reference nou2019s
    In transaction MIRO.
    00082 and 00072.
    After investigation I have found that these invoice reference nou2019s are used in 2002 for accounting documents 3300130419 and 3300135574 and these two documents are archived, and found that these accounting entries are missing in the table BKPF and existing in the table BSIP.
    We donu2019t want to allow the system to post duplicate invoices (For Example: against 00082 and 00072 Invoice reference Nos.)
    Could you please look into this

    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 posting

    Dear Sapgurus,
    I have done this configuration duplicate invoice check option in mm transaction code is OMRDc and in vendor master i choose this option dupliucate invoice check after i was post onevendor invoice document number year is 2009, code 2001 in miro in this one reference field 12, wheir as i am entering one more document in 2010 miro with same invoice  reference field 12, system is allowing, because of two different fiscal year, then after same fiscal year 2010 only with same vendor if i will give same invoice reference field 12 system is allowing but i dont want this transaction allow to post  please tell me.
    Regards 
    SAP

    Hi,
    Go to customizing transaction OBA5 and give the Application Area as F5.
    In the next screen Give message number as 117 and make it E for "Online" and "Batch" processing.
    Regards,
    Gaurav

  • 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 invoices

    Presently, Invoices in the SAP system are getting posted using XMS upload program.
    Problem:
    System is not giving error message or not stopping the XMS upload program from posting two invoices with same reference number and text description (even though date of posting is different)?
    Please suggest some ways as to how to avoid these duplicate invoices posting.
    Note: If this has to be resolved using substitution rule then please explain the exact procedure to be followed for that.

    I assume that the duplicate invoice check you are talking is for Vendor invoices in AP and LIV.
    I am not sure what you mean by XMS upload but here is how duplicate invoice check works in standard system.
    Standard Duplicate invoice check on vendor master enables the system to block duplicate (Same invoice reference, company code, invoice date, amount and vendor). If either of these differ the system allows the invoice to get processed.
    So as per requirement of our client we developed a new validation rule that checks a invoice document while posting for any duplicates accross all company codes and for vendor invoices.
    Prereq:If inv doc type is KR or RE
    Validation: In user exit
    Write code for checking same reference in BKPF-XBLNR=XBLNR and BKPF-Doc Date=Doc Date.
    If there exists same XBLNR check for
    BSEG-Posting Key=31, BSEG-LIFNR=LIFNR;  and issue the message for duplicate check.
    Note: This will still post duplicate invoices if the document date is changed. If you want to block the invoices accross all document dates remove the code of BKPF-Doc Date check.
    But understand the implication. You are telling the system to check for duplicate invoices accross all posting dates. Hence if you are looking 1 yr or 2yrs down the lane the system will slow down alot for invoice posting given that it has to check invoices accross all dates. If you have a seperate doc type for XMS upload you can control the validation by doc type.
    Hope it resolves your issue.
    Thanks,
    Sivaram

  • Tcode FV60 with ECC 6.02 does not check duplicate invoices

    Hi,
    We use FV60 top enter all invoices.  We have config (under MM) for duplicate invoice check against company code and "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.  This is not desireable and behaves very differently than tcode MIRO. 
    Is there any solution to have tcode FV60 perform the same checks, look to the same config for duplicate invoices in SPRO as MIRO and not allow for invoice creation if the "ref field" is identical?

    Hi all,
    Any solution on this..  Even we have the same kind of issue in our organization.  I am also trying various ways.  Plz help me if anyone has found the solution for this.  If I get something, i will update.
    Regards

  • Double Invoice check across company code

    Hi All,
    I have been trying to use the double invoice check functionality across company codes. i.e. when an invoice is posted in Company code A with ref no: xxx, and when I try to post a new inovice with the same reference ie. xxx in company code B, system does not give error message.
    Please note: I have maintained message in application F5, no: 117 and 312.
    Also in customization for double invoice check, I have unchecked "Check Company code" and checked "check reference" and "check invoice date"
    I have also maintained the double invoice check flag in the vendor master.
    Please help at the earliest.
    Regards,
    Ankush

    Hi Ankush,
    Good Day,
    Duplicate invoice check across company code will not check for FI related invoice ( Like FB60)
    But you can able to achive this with BTE ( SAMPLE_PROCESS_00001110 for FI Duplicate invoice check)
    Steps for Implementing a BTE
    (1)Goto transction FIBF menu Environment->Info System (P/S )
    (2)Select the BTE you want to implement.
    (3)Press button Sample function module
    (4)This brings you to SE37 - Copy the sample function module to a Z-function module (First create a new function group for the function module) . Note: The name of the Z-functionmodule is not important
    (5)Edit the code in the new function module
    (6)Go back to transaction FIBF - Menu Settings->Products -> Of a customer and create a new product whicj identifies the new product . Remember to mark the Active field.
    (7)Go back to FIBF menu Settings->P/S function modules->of a customer - Create an entry that links the BTE and Product with the new function module
    Best Regards,
    KSK

  • POSTING ERROR IN T.CODE FB70

    Dear sap Gurus.,
                    while i am doing sales invoice posting with tax code A0 using sap t.code FB70 system not able post the invoice , and also system  has given the message of "Enter a true account assignment object with revenues" .but without using tax code A0 system has been accepted for posting invoice.
    very urgent issue in production server, please anybody will give solution for this issue,i am facing this problem in production server.plese anyone help me.i have attached the document for reference, please find the document and will give the solution as soon as poosible

    Sharmila madam i already given cost center and profit center in FB70, but system again showing that same error, please give me your valuable solution for that issue
    Enter a true account assignment object with revenues
    Message no. KI166
    Diagnosis
    You made an account assignment for 3001010001, a revenue element, in controlling area 9000 to a cost center or profit center.
    System Response
    Cost centers and profit centers can carry revenues in the SAP system as statistics only. To ensure reconciliation between FI and CO for revenue element 3001010001, a CO account assignment object must record the revenues as a real value. This object type is used for updating to the reconciliation ledger.
    In principle, it is possible for the SAP system to automatically derive this CO account assignment object, the reconciliation object. However, all postings made in CO for costing-based Profitability Analysis are logged in the reconciliation ledger under "reconciliation object". In this manner, the reconciliation ledger identifies the exact values flowing into the operating profit. If you post reconciliation objects during revenue postings to cost centers or profit centers, you must do so while keeping the interpretation of the reconciliation ledger reports in mind. The sums of revenue postings to profitability segments, cost centers, and profit centers cannot be broken down further.
    Procedure
    To avoid posting to reconciliation objects, make account assignments to a real CO account assignment object.
    If you want to post to reconciliation objects, you can change this message to a warning or a note for future users, or deactivate the message entirely. Use the Implementation Guide under "Controlling: General" and choose Change message control. Enter area KI and message number 166. If you do not enter an individual user here, the change is valid for all users.

  • Duplicate invoice check in FV60/65

    Hi
    I am trying to set up a custom error message for duplicate invoice based on Vendor number (LIFNR) and Reference number (XBLNR) alone. The system presently considers a bigger set of fields to check for duplicate invoices which are
    Company code
    Vendor number
    Currency
    Reference number
    Amount in Document currency and
    Document date
    I need to override this setting and have duplicate invoice check based on vendor and reference no. combination.
    I have seen some threads which talk about BTEs where an FI interface - SAMPLE_PROCESS_00001110 can be customized by copying the sample function module and make customizations in the BTE.
    Can somebody throw more light on how to approach this.
    Any kind of approach solution would be appreciated
    Thanks
    Nag

    There are two steps to be followed for the duplicate invoice check in FV60/65:
    Step 1:
    I guess you know how to access the sample function module. Go to tcode BERP and select the business process 01110.
    Click on the button ‘Sample function module’ and you would be taken to SE37 and the sample function SAMPLE_PROCESS_00001110 would be displayed. Make a copy of this function module in to ZSAMPLE_PROCESS_00001110 or something like that.
    Write your custom code required for the duplicate invoice check as per your requirements.
    Step 2:
    This involves configuration where the custom function module created in the earlier step should be made active in the BTE process.
    Go to tcode FIBF and create a product through the menu path: SETTINGS -> PRODUCTS -> ….of a customer
    First create a product by clicking on ‘NEW ENTRIES’ button and save the product.
    Next, you have to attach the Z function created in the first step to this product. For this, follow the menu path SETTINGS -> PROCESS MODULES -> ….of a customer.
    Attach your z function to the product as shown in the first line and you are all set.
    Test the tcodes FV60/65 and see if they hit your custom code in the z function to verify the results.
    Hope this helps.
    Note: Here is the custom code that I have written in the function module for my purpose.
      SELECT COUNT(*) FROM bkpf
                      JOIN vbsegk
                      ON    bkpfbelnr = vbsegkbelnr
                      WHERE bkpf~xblnr   = i_xblnr
                        AND bkpf~blart   = i_blart
                        AND vbsegk~lifnr = i_lifnr.
      IF sy-subrc = 0.
        MESSAGE e000(za) WITH 'Document already exists for given Vendor:' i_lifnr '& invoice ref:' i_xblnr.
      ENDIF.
    Thanks
    Nag
    P.S: Please reward points if solution is useful...thanks

  • 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

  • Accounts payable invoices (fv50) - duplicate invoices hard warning

    Currently we only receive a soft warning when we try to enter a duplicate invoice. Is there a way to reconfigure to make the warning a hard warning that can be overwritten it necessary. We are running ECC 6.0.
    Thanks,
    Jon

    H Jon,
    In FI, if the field 'Chk double inv.' is marked in your vendor account, the message F5117 - check whether invoice was already entered with number ...."  appears if an invoice is created before with the same information (comp. code, vendor, curr, doc date (inv date), and ref number). This is the standard functionality.
    Please note that the following fields must be identical for error message F5117 (duplicate invoice) to occur:
         Company code                    (BUKRS)
         Vendor number                   (LIFNR)
         Currency                        (WAERS)
         Reference number                (XBLNR)
         Amount in document currency     (WRBTR)
         Document date                   (BLDAT)  <<<<<<<<<<<
    If the document date is different using the same invoice number, the system does not consider it a duplicate invoice.
    Please let me know if the document date of the duplicated invoices are the same. If not, unfortunately this is the way system works.
    Best Regards,
    Vanessa.

  • Duplicate invoices verification not working in FI

    Hi all,
    We experienced the problem with duplicate invoices posting check in FI (not logistics).
    The indicator Chk double inv. (LFB1-REPRF) is checked in Vendor master data. However, we are still able to post several documents with these fields identical: BUKRS, LIFNR, WAERS, XBLNR, WRBTR, BLDAT in FB01 or FB60.
    The message F5 117 should appear but it does not - when I check OBA5 for area F5 the message is not here at all.
    What could be the problem?
    ECC 6 EHP 6 SAPKH60605
    thanks to all
    Jan

    Hi
    Go to transaction OBMSG and add the message 117 in application area F5 as below:-
    Application Area - F5
    Message - 117
    Allowed - EWS
    Standard - W
    Switch Off-Select the check box.
    Now go to transaction OBA5 and application area F5, maintain an entry as below:-
    Message - 117
    Online -E (Error)
    Batch - E (Error)
    https://scn.sap.com/docs/DOC-35459
    Regards
    Nakul

  • Duplicate Invoices getting posted in MIRO

    Dear Expert,
    My user has raised an issue that while posting a MIRO transaction duplicate documents are getting generated with the same details(amt, invoice ref etc.) in a span of 30 seconds giving two document numbers.
    I have asked the user to reverse one of the open items using t code MR8M to resolve the issue for the time being.
    But the user is asking me why duplicate invoices are getting posted and needs a permanent solution to the issue.
    Did anybody faced a similar issue previously. Kindly suggest me on this.
    Regards,
    Sudish

    Hi,
    Please check the configuration in belowpath:-
    IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoices
    Moreever, in vendor master, you need to maintain the double invoice check tick in the company code data.
    You can also configure the extended rules to check double invoice in BTE 00001110 in FIBF transaction. Search SDN for more details on it. (It has been answered several times.)
    Regards,
    SDNer

Maybe you are looking for

  • Reinstall Photoshop CS6 in Win7 results in error.

    I don't think I installed the 32-bit version PS CS6 Upgrade into Windows 7 64-bit after I downloaded it over a year ago. So, today, I went to execute Photoshop_13_LS16.exe file and I got the error message: "The file archive part of Adobe Photoshop CS

  • How to use FlashIsland.EVENT_BEGIN_UPDATE and FlashIsland.EVENT_END_UPDATE

    Hi All,   I am traying to get value from SAP into Flex component, i am trying to find out where exactly its filling up the array in Flex component and i am unable to figure it out. i am getting values into flex component i can see them but when i am

  • Differences in field TEXT_MCHA_CHARG

    Hi expert, i have a problem when i want to make a query for batch characteristic, i only use MCHA table and i want to use MATNR and CHARG field, i also add a simple code to get the batch characteristic, the problem is when i try to generate the infos

  • Modifing Date format

    hi, I am trying to create a class that will take in a Date in a certain format and give it back in a different format (eg mm-dd-yyyy to dd-mm-yyyy) without using substring(). I am trying to get Month =mm Date = DD and Year = YYYY and from there put t

  • Transport Request - Subtask changes

    Hi All, I have done the changes in a include and structure. But already one person is working on that include and structure. My changes are activated and created a sub task under his main request. Now he wants to move his changes to other system whic