F-43 duplicate vendor invoice check

Hi All,
Generally we use F-43 transaction for direct posting, there we will give document date, vendor date, Amount, and reference number etc etc.. among those details these four are majors. that is for a duplicate invoice chek we will check these four things if for other document, thse four fields matches then we can throw error or warning message to the user by configuring in OBA5. now my requirement is
i want to get error message if all the four matches and i also want to give one warning message if three of them matches, i.e. if any of them mismatches then i want to give warning message. In the configuration level I can give either Error or Warning message. But now want to give both depends upon situation.
for this req is there any way by means of configuration or shall i do it in programming. If i need to do it in programming where can i write the code, i mean are there any user exits, customer exit or BADI.
Regards.
Ramesh .

Similar Messages

Duplicate vendor Invoice check in FB60

Hi Experts,
I want to put the duplicate invoice check while posting the vendor invoice through FB60. I want the system to check the duplicate invoices in combination of the Vendor code and vendor invoice number ( we put the vendor invoice no. in the reference field of FB60 ). How to make this possible. I do not want to make the FI validation for the same. Can you please suggest how to go ahead with this.
Thanks,
BABA

Hi Shailesh,
phuu, ok, let's start from the beginning then.
Some theory first:
you need the validation because the standard check takes the doc.date ito consideration and this is not wanted. And you need the exit from the validation (! not a separate exit! not the original), locate the IF-statements where there is an ELSE option ending with function CUSTOMIZED_MESSAGE. It is up to you what to do here. In the original functoin module, the messages are issued here immediately. It can be an error or a warning, depending on the setting in table T100C. If my understanding is correct, you always want to see an error message, bt this should be done in the validation, not in the function module. So you should skip the customized_message function call and just issue the messages here as info message regardless of T100C settings. In this case, remove the function call customized_message (as many times as it occurs) and issue the message included directly as an information. Right after the message was issued, set E_RC to 4, infoming the validation that the check has failed. (Note that the customized_message function is only called if the check has failed, so no worry that you always get the message.
4. Define the exit for the validation
=========================
Go to your form pool Z_RGGBR000 (defined in V_T80D) and locate the statement APPEND EXITS. It should appear few times, locate the last occurence.
Right after that, enter the following:
exits-name = 'U901' .
exits-param = c_exit_param_none.
exits-title = text-901.
append exits.
This will define a new exit namd U901 for the validation routines. If in V_T80D, you already had a Z (or Y) report, check if the string U901 is used in that code already (check for the main program). If this is the case, instead of U901, use another name, it should begin with U followed by 3 digits. Also, you make sure the text symbol text-901 (or the 3 digits you are using) is existing, doubleclick it and enter a description like "Duplicate invoice check validation" or similar.
Well, the exit is published, we have to write the main code now.
go to the very end of your Z_RGGBR000 report and add a new form U901 like follows:
Duplicate invoice check validation
FORM U901 USING B_RESULT.
Vendor master flag
data: l_reprf like lfb1-reprf.
Result of function module
data: l_rc like sy-subrc.
Check vendor master first
select single reprf into l_reprf from lfb1 where bukrs = bkpf-bukrs and lifnr = bseg-lifnr.
Do not continue if flag is not set.
if L_REPRF is initial.
b_result = b_true.
endif.
check not L_reprf is initial.
Call modified function module
CALL FUNCTION 'Z.....your function'
    EXPORTING
      i_bukrs = bkpf-bukrs
      i_lifnr = bseg-lifnr
      i_waers = bkpf-waers
      i_bldat = bkpf-bldat
      i_xblnr = bkpf-xblnr
      i_wrbtr = bseg-wrbtr
      i_koart = bseg-koart
      i_reprf = L_reprf
      i_shkzg = bseg-shkzg
      i_xumsw = bseg-xumsw
      i_bstat = bkpf-bstat
      i_belnr = bseg-belnr
      i_gjahr = bkpf-gjahr
      i_blart = bkpf-blart
EXPORTING
      e_rc = L_RC.
Decide if validation message must be issued or not
if L_RC = 4.
b_result = b_false.
else.
b_result = b_true.
endif.
endform.
After this, activate the source code. Make sure you have defined the text-symbol 901 before!
5. Define the validation
=================
Go to OB28 now, and enter your company code(s) and the call-up point 002 (line item). If there is a validation defined already, you have to add a new step only, if not, you have to create the validation anew.
I assume there is no validation defined yet, so enter a name for the validation like FI_2 or similar. It should NOT be named DUPLIC or similar, i.e., you should not include the purpose in the validation name. This is because the validation is defined on company code / call-up point level and it may contain many steps for different purposes later. A generic name FI-2 or probably your company code followed by 2 (2 is the call-up point) is the best choice.
Before presing enter go to the last column Validatin active and enter 1 here.
Then press enter and you will get an error that the validation does not exist. No problem, go to menu path Environment --> Validation and let's create a new validation.
First, enter a description for your new validation in the right hand panel. Again, this should be a generic description, tell nothing about duplicate invoice checks here.
You may be asked here to assign a message class to the boolean class 009. You should enter here a Z message class where the validation message should be issued from. If no appropriate message class exits, open a new session go to SE91, enter a new message class Z... press create, enter a description. Then go to the Messages tab there, and create a new message with number 001 (NOT 000) and enter the message text there. E.g. Duplicate entry not allowed.
Coming back to the validation, if the message class was already assigned (this is the case if there was a validation defined earlier), you can create a new step. In case of a new validation, it will become the first step. But if there was already a validation in OB28 for your company code and call-up point 2, then it will be the last step. In the left hand panel, make sure the new (or existing) validation is selected and press the Create Step button (Ctrl-Shift-F5).
In the right hand panel, enter a description for your step. This is the point where you can enter Double invoice check or similar.
We have three parts here, a Prerequisite and a Check part, finally a message.
In the left hand panel, select the Prerequiste. This will activate that screen block in the right side. We have to make sure that our validation is called only for the relevant vendor line items, so press Ctrl-F3 to hange to expert mode ) and enter the following in the Prerequiste window in the right hand panel:
BSEG-LIFNR <> '' AND BSEG-XUMSW = 'X' AND BSEG-KOART = 'K' AND
BKPF-BSTAT = ''
Beware '' is a ' followed by another ' and not a single " !!
Then switch back to normal mode using Ctrl-F1 and check the small lamp below that should be green now. Also, you can see the field descriptions now. If the lamp is red, press Ctrl-F3 again, delete all and copy the above again. Do not bother with line breaks. Switch to Ctrl-F1 again until the lamp is green. OK, what we have told here was please call the validation only if we have a vendor number and if this is a sales relevant item (invoice or credit memo, but not a payment or similar, this is the standard logic as well), and the account type is vendor (K) and this is a normal document.
WHen you are done here and the lamp is green, then go to the left side again and select the Check part. Now you should be able to edit the Check screen lock in the right hand side again. Switch to expert mode and enter simply U901
This is the name of the form in your Z_RGGBR000 report. NO brackets, no spaces, only U901 here. Switch back to Ctrl-F1 and instead of U901, you should see the text of your form (text symbol 901 in report Z_RGGBR000).
Finally, click the Message part in the left side to be able to maintain the message in the right side. If you issued an error from the function module already, you can give here an information, or you can give it as an error if you like. The message number is one of the messages from your Z message class, you have to define the text in SE91 (see above).
When done, save the validation and you can test it immediately.
Here a brief summary what is happening:
OB28 setting defines that in your company code a validation like FI-2 or similar is active on line item level. Whenever a line item is abut to be created, the validation will be called.
However, the prerequisite of the validation is quite strict: only a limited number or vendor items will allow to continue, other line items (G/L, customer, not sales relevant vndor, etc.) will just skip the whole validation.
If the prerequsite was met, the Check part is carried out. Here we have the exit U901.
In the exit, first we check if the vendor is flagged for double invoie checks. If not, we quit and processing can be continued. B_TRUE means it is OK. If the vendor is flagged, we call the new Z function which is almost the same as the original one.
The Z function will check table BSIP, but it will skip the document date comparison. If the current invoice seems to be entered earlier (regardless of the doc.date), instead of the standard customized message (which can be E or W for instance), the very same standard message will be issued as an information. So the user will be informed about the previous document number but the processing won't be stopped. In addition, a return code will be set to 4, meaning check has failed.
Jumping back to the exit, if the return code is 4, we have to tell the validatin that the check has failed (B_RESULT = B_FALSE), otehrwise we can tell the validation that the check was OK (B_RESULT = B_TRUE).
Now we are back in the validation, and, depending on B_RESULT, we just continue processing (B_TRUE), or issue an error message from a Z message class (B_FALSE). As the main standard message was isued already from the Z function, the user should know at this stage what the matter is. Your Z message can be a bit generic one, no need to include the vendor number or the previously issued invoice, etc.
Hope that helps, points welcome
Csaba

Validation Check - Duplicate vendor Invoices

Hi,
We have a situation where the Duplicate Vendor Invoices have been entered by the users, bearing the same date and reference nos. as the original ones. When we checked we observed that, the system gives the warning message, but the same is ignored by the users. To prevent the same from happening again, we want to convert the warning message into the error message.
Could any one guide as to how can we set up the validation checks, such that the system would throw an error message. In the vendor masters, we have set up the check for Duplicate Invoices.
Thanks in advance.
Best Regards,

Hi,
If you already know the message number, then go to T.code:OBA5 or
T.code:SE91 (if its an custom message class) and change the message from waring to Error.
If you are not aware of Message, and try to post a duplicate invoice & when the warning message comes, double click on the same, it will give you the message number.
This will resolve your issue.
Please let me know the result of the same
Thanks
Kalyan

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

Duplicate Vendor Invoice

Hi All,
while doing a direct posting in F-43, i want to avoid the duplicate vendor invoice. For this i know we can go to OMRDC and there we can activate it and also for that particular vendor in XK03 we need to tick the double invoice check and also we need to configure in OBA5 the standard message with ID 117 and type as E for error and W for warning.
but now my requirement is if user is trying to do direct posting, If
Docmuent date
Vendor number
Amount
Reference
all the four matches then the error message should be displayed
if any one those mismatches then insted of error i want to throw warning message.
to full fill this function where i need to write the code, i mean user exit of customer exit (any enhancement),
the message and message type it getting from the function module CUSTOMIZED_MESSAGE
Can any body help how to proceed further....
its urgent.....
Regards,
Sunil Kumar Mutyala.

Can any body help me

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 Vendor Master

Hi Experts,
I am purposing vendor master to be created centrally to the client. How can I make it sure the same vendor is not created duplicate. What are the primary fields which i maintain so that system pops up a message for duplicate vendor entering. I checked with VAT number, Tax number nothing works. even the same name you can enter with all details same. What is the mechanism to prevent the creation of duplicate vendor other than the Zprogram or any exit.
Thanks in Advance,
Lekhram

hi lekhram
there is no need for a z program for duplicate vendor creation check.
add these 2 message control for vendor master data
goto financial accounting - accounts receivable and accounts payable - vendor accounts-master data - preparation for creating vendor master data - change message control for vendor master data
add message no 144 i i for both online and batch
add message no 272 i i for both online and batch
kind regards
Arman
SAP FICO

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
Shaun

Hi,
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

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

Vendor duplicate invoice check ???

Dear Expert.
Since in for FI documents will check double invoice when we post invoice with the same
- Company code
- Vendor
- Currency
- Document date
- Reference number
But our client would like to see or check double invoice if it is raised by different
VENDOR
For example, if we post invoice in FI with
- company code: 1000, vendor code: A, Currency USD, Document date: 01.04.2009 and invoice no. 1234
and we also post invoice in FI with
- company code: 1000, vendor code: B, Currency USD, Document date: 02.04.2009 and invoice no. 1234
So is there any Standard report or standard Configuration check available ?? Or How I can achive this ?

Hi Uday,
Please check the steps again:
SPRO --> Materials Mangemnt ...> Purchasing ...> Partner Determination
A. Define Partner role
B.Define Permissible Partner Roles per Account Group( In this step, you can specify for each account group of the vendor which roles the vendor may assume.)
C.Partner Settings in Vendor Master Record
In this section, you define partner determination schemas and assign them to account groups.
D.Define Partner Schemas
In this step, you define partner determination schemas.
E. Assign Partner Schemas to Account Groups
F. You need to include the Partner Function PI in the Partner Schema assigned to your PO document type.
MM-Purchasing -partner Determination - partner settings in purchasing documents
Apart from the above setting if you have set duplicate invoice check in a particular Vendor Master record and there is an entry in the Reference field when you enter an invoice for this vendor, the system always checks if there is an invoice containing same data as which just entered.
The following check criteria can be used
- Co, Code.
- Vendor
- Currency
- Reference
- Invoice Date
- Amount
You must specify in customizing whether the Co. Code, reference and Invoice date are included in the check.
If it finds an invoice that matches all these attributes (Message # M8 108) is issued as error or information.
All these are SAP standard settings; and they should work. You can always look to enhance the check logic with the help of a BADI or FM Exit.
Hope this is useful.
Thanks,
Reetesh

Duplication Check for Vendor Invoices

Can we check for duplicate invoices in SAP
Regards
Satish

Hi
The configuration settings are made in
IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoice
In vendor master you need to maintain the tick for Duplicate Invoice Check
Thanks & Best Regards
Sanil K Bhandari

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,
Bob

Hi,
Try check link below:-
http://help.sap.com/saphelp_afs30b/helpdata/en/ce/4f3e39ea3aee02e10000000a114084/content.htm
Regards,
Fauzi

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

F-43 duplicate vendor invoice check

Similar Messages

Maybe you are looking for