Greetings to all,

The procedure that is described below will explain how to prevent the creation of duplicate ERS invoices by using the MRRL transaction code.

Problem Statement:

The issue is that duplicate ERS invoices are generated during business transitions for the same reference# in the account of the related vendor, resulting in double payments to the relevant suppliers and a direct loss to the company. Another unexpected discovery is that when using the transaction code MIRO, the system can only create a duplicate ERS invoice for a duplicate reference# for the particular Vendor. However, when using the transaction code MRRL, the system is able to create a duplicate ERS invoice for a duplicate reference#.

Duplicate ERS invoices are posted in the vendor’s ledger account as a result of this issue, and the finance and commercial department of an organisation must deal with them. In other instances, the company has also paid the relevant vendor twice, and it might be very difficult to recover that money from the relevant vendor.

Solution:

To apply a solution for the above-written problem and to address a compliance issue, please see the SAP Note that follows. The ABAP code for this solution can be found in the SAP Note that follows.

To Conclude:

A duplicate ERS invoice will not be issued for a duplicate reference# for a vendor once the aforementioned SAP note has been installed on the system and is used in transaction MRRL.