How to Restrict to Create Duplicate ERS Invoice for the same Reference# for a Vendor by using Transaction Code-MRRL
The following process will shed light on how to Restrict to Create Duplicate ERS Invoice by using Transaction Code – MRRL.
The problem is that duplicate ERS invoices are produced during business transitions for the same reference# in the account of the corresponding vendor, and as a result, double payments are made to the respective suppliers, which results in a direct loss to the business. Another unexpected finding is that the system is only able to create a duplicate ERS invoice for a duplicate reference# when we use the transaction code MIRO, but when a business uses the transaction code MRRL, the system can create a duplicate ERS invoice for a duplicate reference# for the respective Vendor.
Due to this problem, the Finance and Commercial department of an organization has to deal with duplicate ERS invoices that are posted in the vendor’s ledger account. In some cases, the organization has also paid the respective vendor twice, and it can be very challenging to get that money back from the respective vendor.
As a compliance issue, not placing the ABAP code here and to implement solution for the above written problem please refer below SAP Note. In the below SAP Note itself you will find the ABAP code for this solution.
SAP Note#1604492 – MRRL ERS: Duplicate Invoice Check. Link is placed below:
Once the above SAP Note will be implemented on the system then by uses transaction MRRL, duplicate ERS invoice will not be generated for a duplicate reference# for a vendor.
Please follow Neeraj Jain for more content on issues & topics related to SAP Sales & Distribution and Material Management.
If any questions, please click here
Thanks for your interest! Please share feedback, comments, or suggestions below.
SAP Technical Manager in HCL Technologies Limited