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

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 that are posted in the vendor’s ledger account must be dealt with by the organization’s Finance and Commercial department as a result of this issue. It can be exceedingly difficult to recover money from a vendor when the organisation has paid them twice, as happens in some circumstances.


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.

MRRL ERS: Duplicate Invoice Check, SAP Note#1604492. Below is a link to it:

To Sum Up:

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.

For additional information on issues and subjects relating to SAP Sales & Distribution and Material Management, please follow Neeraj Jain.

If you have any queries, kindly click here.

We appreciate your interest. Please leave any comments, recommendations, or criticism below.