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

Similar Messages

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

Configuring double invoice check for vendor invoices posted through FB60

Dear all
Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
for miro documents..we can use Tcode OMRDC
Is there any such tcode which can be used for configuring fi invoices for double checking..
regards
Expertia

Dear Expertia,
In FI,when checking for duplicated invoices, the system compares the
following :Vendor, currency, company code, gross amount of the invoice,
reference document number and Invoice document date.
SAP Note 305201 clarifies this in a more details; please read it.
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.
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.
I hope this helps You.
mauri

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

Restricting TDS based on validation rules for vendor invoice posting

I have two Tax Types assigned in the vendor master. If at the time of invoicing user do not delete the unwanted tax types, system posts both the amounts related to both the tax types.
User has to necessarily delete one tax type which is not required and then proceed with simulating the vendor invoice.
Can this be controlled thru validation rules ? Even if the user forgets to delete the unwanted tax type while passing vendor invoice, validation rule must throw an error asking to delete the unwanted tax types before simulating the vendor invoice.
Please help how to build such validation rule with detailed procedure.
Thanks
Ravi

Hi Ravi,
I hope you have selected both withholding tax type and code at the vendor master level itself.
It is generally advisable to select withholding tax type at vendor master level and leave the field withholding tax code to be in display mode. Hence during vendor master creation, they can only select withholding tax type and not the withholding tax code. Ensure liable to tax should be ticked against all withholding tax types.
During invoice entry creation either in FB60 or in MIRO, they can select the withholding tax code next to the withholding tax type and simulate and post.
In your case, you cannot delete the withholding tax types at invoice entry level. Ensure to delete the unwanted withholding tax type from your vendor master itself, I mean delete only the withholding tax codes pertaining to that unwanted withholding tax type.
Hope this helps. Assign points if useful
Regards,
Dwarak.

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 .

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 .

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

Check Duplicate Postings, GL, A/R, A/P

Hi Experts,
My requirement is to post accounting documents based on data pushed from another interface via RFC. We're using BAPI_ACC_DOCUMENT_POST to handle this. Now, the client wants us to handle double postings to prevent reprocessing of same data. The postings are combination of GL to GL, GL to Vendor and GL to Customer. So far, what I've researched are checking on duplicate vendor invoices.
As a last resort, we're leaning on just having a log of all entries that we processed and comparing them with the incoming data.
Please help. Is there a function module or any other way to prevent double postings? Your inputs are greatly appreciated. Thanks.
Regards,
Reiko

Hi
One suggestion on the AR Part. Use the User Exit SDVFX008 to populate the XREF1/2/3 with the SD Billing Document No. Than in posting of the document. Than you can write a validation rule for the same in GGB0 to check for values existing already. You need to try this, but i think it should work
Regards
Sanil Bhandari

Vendor invoice numbers

Is there standard SAP functionality available that checks invoice numbers for the vendor to avoid duplicates when doing service entries?

This should have been posted in MM forum.
Check this thread
[configuring double invoice check for vendor invoices posted through FB60 |configuring double invoice check for vendor invoices posted through FB60;
G. Lakshmipathi

Cross Company Sales Automatic Vendor Invoice Not Created

Hi,
I have an issue in Cross company Sales Scenario (Inter company Sales),
During the Intercompany Invoice we can trigger output RD04 to create Automatic Vendor Invoice in the Ordering Company.
I have done the necessary configuration for creating Idoc (RD04), FI & MM.
I could able to create an Idoc successfully and the status of the Idoc is 53.
However when I check the Vendor Invoice in the Ordering Company T.Code FBL1N, system gives me message that no items found for the Vendor.
I request please let me know me what configuration I have to do to create Cross Company Sales Automatic Vendor Invoice
Regards,
Murali
Edited by: Murali Mikkili on Jul 27, 2008 9:05 AM
Edited by: Murali Mikkili on Jul 28, 2008 11:49 AM

Hi Daniel,
Both the company codes should be assigned to the same company.
Clearing accounts must be defined in every company code before a cross-company code transaction may be carried out. The clearing accounts may be G/L accounts, customer, or vendor accounts.
In the configuration you must assign clearing accounts to every possible combination of two company codes to allow cross-company code postings between these combinations
To reduce the number of clearing accounts, you can use just one company code as the clearing company code. In this case, you only have to assign clearing accounts to every combination of the clearing company code
In T-code OBYA
For ex: company code 1000 clearing account 12345 is same for Debit and credit
Company code 2000 Clearing account 67890 is same for debit and credit
Posting keys must be assigned to the clearing accounts to identify their account
types.
Hope this helps you to solve your probelm.
Regards,
Mir

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

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

Hello 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

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

Validation Check - Duplicate vendor Invoices

Similar Messages

Maybe you are looking for