MIRO: duplicate invoice check on subsequent credits/debits
Gents, can anyone explain why there is no duplicate invoice check on credit memo's when processing MIR7/MIRO? what's the logic behind this? I know i can change this using note 305277, but what's the reason behind this choice?
You need to make changes as per this OSS note.
This is an extended functionality provided by SAP via this OSS note.
There can be scenario, where multiple credit memo can come on the same day with reference to same invoice.
Regards,
Gaurav
Similar Messages
-
Duplicate invoice check on MIRO/Logistics invoice verification.
Hi SAP Gurus,
I am stuck with a small issue here. I am trying to post an invoice through FB60 with same vendor, same comp code, same GL and same reference and I am aware there are two settings to do the duplicate invoice check one is through vendor master (payment transaction screen) and the other is OMRDC transaction where we check certain fields to validate invoices based upon same values. now when I take a vendor without that vendor master config for duplicate invoice check and checking all the fields in OMRDC transaction the system doesn't validate or throw any error while posting FB60 with all the same values. so is there any other configuration available apart from these two configuration settings?
My requirement is the configuration already exists which checks duplicate invoice based upon same invoice date for all the vendors of a company code and I need to change the configuration setting back where it ignores checking invoice date. it doesn't show any kind of error in my test whether I make change in OMRDC transaction or not.
Regards,
BobHi,
Try check link below:-
http://help.sap.com/saphelp_afs30b/helpdata/en/ce/4f3e39ea3aee02e10000000a114084/content.htm
Regards,
Fauzi -
Duplicate invoice check ( MIRO)
Hi All
I have done all the settings for duplicate invoice check. And I posted an invoice with the following parameters on a limit PO
Company code:ABC
Document date:12.09.2009
Reference:INV1
Currency:USD
Vendor:102221
Amount:20
Now I am trying to post another invoice
Company code:ABC
Document date:12.09.2009
Reference:INV1
Currency:USD
Vendor:102221
Amount:100
Now I am getting duplicate check invoice Error, even though I changed the amount in the second invoice. If I change the reference no or doc date, then system is differentiating it as different invoice and it is not throwing any error. If I just change the amount, then , it is throwing duplicate invoice error. How to fix this problem.
Thanks in advance for looking into thisDouble invoice check for a vendor is possible for:
1. Company Code
2. Invoice Date
3. Referece document
If in config all of these are selected, and if you enter 2 invoices with all same values for above parameters, then system will throw an error.
Amount is not checked for this. -
In FB60, duplicate invoice check does not work if invoice date is different
In FB60, duplicate invoice check does not work if invoice date is different
This issue is in FB60 and not MIRO.
Duplicate invoice check is activated in vendor master.
I posted an invoice for a vendor with amount $ 100, Reference 1234 Invoice date Nov 01, 2011
I tried posting for same vendor (and also Co Code) with amount $ 100, Reference 1234 Invoice date Nov 01, 2011. System does not allow. This is fine.
Now I change only date, from Nov 01 to Nov 02, and system allow posting.
Why I don't get the error message when date is different ? It should not be treated as a different invoice since invoice reference, amount, Vendor and Co Codes are same.
SAP documentation says that it checks document date during duplicate invoice check even for FI invoices, then why does it allows in this case.
Is this a bug ?
I already tried changing settings in SPRO under LIV, this does not impact FB60 invoice booking.
Thanks
SandeepHi,
Use BTE - 1110 - (Check on Invoice Duplication) for FB60. Take the help of your ABAPer to make a coding in Function module mentioned in BTE.
Need to make a copy of the FM and then you can do relevant coding.
refer the link.
[http://www.thesapconsultant.com/2006/10/sap-business-transaction-events.html]
Regards,
Shridhar -
hi all
i have set up the necessary checks to catch duplicate invoices under path MM-LIV- incoming invoice-set check for duplicate invoices. and in vendor master i flagged the "chk double inv" and in PO ticked "GR-Bsd IV". but the duplicate check doesn't seem to work, i can still enter an invoice which already been booked previously. i couldn't figure it out! anyone can help me on this issue? thanks.hi,
i've done these settings, not working either! do i need to config Error or warning msg? i 've tested the IDES, i found company code 7500 is set up with duplicate invoice check. and when i tried to enter invoice 2nd time in MIRO, system generated error msg: Another relevant document exists with the same official document number
Message no. 8A332
The official document number that was entered in the reference document field was checked against other documents that have the same business partner and are assigned to the same document class.
The result of the check was that another document with the same official document number already exists in the system.
Please check your entry of the official document number.
If the you are not able to change the entry in the reference document number on the current screen, please choose 'Document overview' and change your entry on the following screen.
where to config this msg? -
ERS does not check duplicate invoice check
Hi there,
We have all the vendors in the vendor master set up with duplicate invoice check on. However this does not work during MRRL process.
Any sugegstions, information is greatly appreciated.
Thanks,
GajananHello Gajanan,
If you create an invoice with transaction MRRL (ERS) then this invoice
will be created automatically in the background (not online).
Unfortunately I have to inform you that the function 'Duplicate
invoice check' is not implemented for ERS. This check was primarily
written for the online transactions, like MIRO.
A possible solution to this issue is contained in note
48121 which describes how you can create your own validation user exits
in the FI interface (function module ckmv_ac_document_create). In such
an user exit you can implement your own coding, for example the double
check for the invoices:
the following
CALL FUNCTION 'MRM_FI_DOCUMENT_CHECK'
EXPORTING
i_bukrs = i_bukrs
i_lifnr = i_lifnr
i_waers = i_waers
i_xblnr = i_xblnr
i_bldat = i_bldat
i_wrbtr = i_rmwwr
i_blart = i_blart
EXCEPTIONS
invoice_already_exists = 1
OTHERS = 2.
will be called in the validation user exit and if the sy-subrc = 1
(invoice already exists) then your own error message will be proceeded
and the invoice won't be posted.
Hope this helps
Ray -
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 helpHi,
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. -
FB60 Including or excluding a characteristic in duplicate invoice check
When entering vendor invoice in FB60, system checks entry of company code, vendor, document date and reference number for duplicate invoice. If duplicate invoice is detected, message F5117 will be issued.
We would like to change the duplicate invoice check by excluding document date for vendor invoice entered in FB60. Such change does not affect customer invoice entered in FB70. That is, document date will continue to be part of duplication check for customer invoice FB70.
I understand such change (of adding or deleting characteristic in the message parameters) requires ABAP expertise. I could not find message F5 117 in the source code of program SAPMF05A (FB60). Would appreciate any help as to where the change be made.
Regards,Hi,
I has written in the program SAPFF001
it is used in the program 2 times in sub routines
FORM doppelte_belege_pruefen_s
FORM doppelte_belege_pruefen.
Regards
Krishna -
Including or excluding a characteristic in duplicate invoice check
When entering vendor invoice in FB60, system checks entry of company code, vendor, document date and reference number for duplicate invoice. If duplicate invoice is detected, message F5117 will be issued.
We would like to change the duplicate invoice check by excluding document date for vendor invoice entered in FB60. Such change does not affect customer invoice entered in FB70. That is, document date will continue to be part of duplication check for customer invoice.
OBA5 and OBMSG allow change of message status for W, E, etc. We can create customized message (e.g. Z117) in SE91 and assign it to application area. But what about changing the message parameters to include or exclude certain characteristic? Does such change have to be done in program SAPMF05A (FB60) and that requires ABAP expertise? If we change the message parameters directly in the program, then we can assign separate messages for vendor and customer documents?
We set u201Cduplicate invoiceu201D indicator in vendor master. I have reviewed Note 305201.
Appreciate any insight or feedback. Thanks in advance.Problem solved.
Use Business Transaction Event 1110
Activate SAMPLE_PROCESS-_00001110 -
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,
vikasHi 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 -
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
NagThere 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 -
Hi,
We have made the settings for duplicate Invoice check. In one scenario, when we use same reference number for different vendor also, system is throwing duplicate invoice check. Could anyone of you clarify why system is throwing error for same reference even it is a different vendor also.
Regards
UmaHi Kumar,
Standard SAP always checks duplicate invoice check at FI document level BSEG-XBLNR, not at Vendor level. If this situation occurs we always input XXXXa inorder to avoid this type of situation. Hope this helps.
Thanks
Raghuram -
Duplicate invoice check in LIV
Hi,
How system check the duplicate invoice check in LIV.
We have activated Duplicate invoice check in vendor master and activated this in IMG via "SPRO-LIV-Incoming Invoice-Set check for Duplicate invoice" in the combination of Company code, reference number & Invoice date.
Message number M8 462 as Error message only
In our case, we have used the same reference number, Invoice date, amount, currency, vendor code, company code in MIR7 at header level. But we have posted to the different GL number and this is not reference to PO/SES number.
Could any one help on this scenario and whether duplicate invoice check is available in G/L account tab also.
Thanks & Regards
R>Saravanan
Edited by: saravanan_rsa on Nov 30, 2009 2:35 PMHi,
Refer below link
[http://www.erptips.com/Snippet1/rbjyatmlgc.pdf]
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/ce/4f3e39ea3aee02e10000000a114084/frameset.htm]
Regards,
Vikas -
Duplicate invoices check criteria
Hello Gurus,
I have a quick question,
We have set the duplicate invoice checkbox in Vendor master records to check for duplicate invoices and the reference field in FB60 is a mandatory field, now as per the documentations, 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
How can I add Amount as a criterion to check for Duplicate invoice check??In case of FI document , duplicate vendor invoice check is available for :-
Company code
Vendor
Currency
Document date
Reference number
You need not to restrict to amount for example
a vendor gives you duplicate invoice with different amount. system will block the entry or give warning message depending upon message control maintained.
in case you have scenario for restriction you have to maintain user-exit. check user-exit for fb60.
thanks
S AP
Edited by: S AP on Aug 11, 2008 3:34 PM -
Duplicate Invoice Check -Vendor
Hi everyone,
I found out that I posted an invoice(FB60) for the same vendor with same, amount, reference,invoice date,same company code.one invoice was posted on 3rd march and other was posted on 25th march,I checked in the vendor master record indicator" chk double inv" is checked.Why system didn't give any error or warning message.Please guide.
Regards
ShaunHi,
Good Day,
Please follow the below steps ( taken from another post and its working fine for me)
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.
and also It will check duplicate invoice check in vendor master data
and in posting key is there check box selected for sales related
The setting you making in OMRDC i.e Materials management->Logistics
Invoice Verification->Incoming Invoice ->Set Check for Duplicate
Invoices is only valid for MM and not FI invoices posted via FB60/FB65.
You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
in the relevant vendor master record (transaction FK03).
Please also check, that message F5 117 has been set correctly in the
IMG using this path:
Financial Accounting -> Financial Accounting Global Settings ->
Document -> Default Values for Document Processing -> Change Message
Control for Document Control For Document Processing
Finally & mainly, go to the relevant posting key is defined as sales
related in transaction OB41. You have to flag this field if the
duplicate invoice check should work.
Best Regards,
KSK
Maybe you are looking for
-
Creation of Multiple Similar Assets
Hi experts, I need to ask if following is the best that can be done for splitting few assets of one class to another class or is a better solution exists for it Or is there any transaction/report that can create Multiple Similar Assets? Currently, we
-
BDOC's to update the custom fields in R/3 from the CRM sales order
Dear All, I need a small help. My requirement is as follows. When ever a sales order is created in CRM, an outbound delivery will be automatically created in the R/3 system. There are some fields in the CRM sales order which are not there in the R/3
-
I Need to Update CS2 Trial Key to Full Key
I have several users who are on CS2 trial keys which are going to expire at the end of the month. Does anyone know of a way I can update them with the full licence without uninstalling? Ideally I would like to roll out the updated key via SCCM (SMS).
-
Hi, the document type AB is used for cash payment(FBCJ) and reversal so its create confusion. As per requirement if we use document type SK for cash payment(FBCJ) then its reversal document will be AB,this is the scenario . Please advise me Thanks,
-
Reset FI CO transactional data
All - We recently built a production box from a sister company refresh. We now have a production box with two company codes configured, one company code with transactional data (irrelevant for this golive). One company code to go live with (no tra