Duplicate Invoice Check

[Former Member]

Dear all,

Our client requires duplicate invoice check for FI document also ( exactly like MIRO duplicate invoice check ) but without considering the date. That means, even if the date is different, system should throw an error message. And it should not give an error while posting the reversed document with the same invoice number.

Plz help.

Regards

Balaji

[Former Member]

Dear Balaji,

Go to SPRO>Financial Accounting(New)>Accounts Receivable and Accounts Payable>

Vendor Accounts>MAster Data>Preparations for Creating Vendor Master Data>

Define Account Groups with Screen Layout (Vendors)

Define Screen Layout per Company Code (Vendors)

Define Screen Layout per Activity (Vendors)

In all the above three screen layout go to coampny code data>payment transaction

here tick mark the Double Invoice Validation as required entry.

save and transport to the required client.

Now when you create/change any vendor master it will ask to sleect "Chk double inv" as mandatory field.

This will stop duplicate invoising .

Regards,

Alok

[m_madhu]

HI,

I will explain how the check for duplicate invoices work in FI:

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.

Note 305201 clarifies this in a more detail, which I have attached for

your reference.

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

The duplicate invoice check in FI is hard coded in the programs

themselves which is different to that in MM.

Reg

Madhu M

[Former Member]

Dear Madhu,

Thanks a lot for your reply.

But, the Client's requirement is to have the same features of MM duplicate invoice check in FI transactions also. There are many company codes in our system which are in different countries. We need to have a solution exactly like MM where in we can modify according to different company code's requirement.

Regards

Balaji

[m_madhu]

HI,

In Rel 4.7, 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) in Rel 4.7. 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 see if attached Note applies to your situation.

568926

537213

305201

52505

31771

Reg

Madhu M