1. Evaluated Receipt Settlement –
ERS procedure in SAP.
Evaluated Receipt settlement (ERS) in SAP R/3
ERS allows settlement of a goods receipt without receiving the Actual Invoice
from the vendor
Using Evaluated Receipt Settlement (ERS) means that you have an agreement with
your suppliers that they do not create invoices for purchasing transactions, but you post
them yourself based on the information contained in purchase orders and service
entries. Thus, ERS has the following advantages:
· Purchasing transactions are closed more quickly.
2. · Communication errors are avoided.
· No price and quantity variances in invoice verification.
Pre-requisites:
(1)Vendor Master : XK01
Purchasing data
Vendor no. 410001 is created in the following Co.Code and P.Org. with above
setting for ERS
(2)In Info Record : ME11
Maintain the following setting. ie. ”No ERS” flag should remain un checked.
Say in the following Info Record:
3. (3) In Purchase Order (PO) (ME21N) maintain the following setting.
Thus ERS indicator should be checked. This Flag will only appear and
default to flagged if selected for that specific Purchase Organization in the
vendor master.
4. Also Tax code should be maintained in the PO.
With the above setting the following PO is created with Vendor 410001,
material 104 in Plant 1001.
(4) Release the PO if Release Strategy is present
T-Code:ME29N
(5) MIGO: Goods Receipt against PO 4500000218
5. You will get the following Message
So Enter the delivery note and post the GR.
The Accounting document is as follows:
(6) Mandatory IMG Setting required for Message Determination as
follows:
(a) Define the Message type
The message type ERS is set up in the path
SPRO> IMG>MM>LIV>Message determination > Maintain Message Types
6. Thus Access sequence assigned with condition type ERS is 0004.
Check the Form and Program maintained for ERS.
(b) Maintain Message Schemas
Maintain the message type (ERS) in the message Schemas MR0004 – ERS
Procedure in the following IMG path
SPRO> IMG>MM>LIV>Message determination > Maintain Message Schemas
7. (c)Assign Forms and Programs
Assign the forms and programs for the message type ERS in the following
IMG path. In case custom program and form is designed, same has to be
assigned to the message type ERS.
If the Form is different for different medium of output, the relevant forms
have to be assigned to the message type and medium.
SPRO> IMG>MM>LIV>Message determination > Assign Forms and programs
9. (8) ERS with Logistics Invoice Verification T-Code : MRRL
Evaluated Receipt Settlement (ERS) process posts the invoice documents for
all open goods receipts without expecting the invoice from the vendor.
The Process can be run using the transaction code MRRL. The important key
fields are available for document selection like Company code, Plant, Vendor,
Purchasing Document number etc.
The Simulation is also possible by test run so that the goods receipts which
can be posted are listed and also the documents which cannot be posted are
also listed. At this point, the system makes no postings and only goods
receipt documents are listed
First run in test mode
After simulation run, the transaction can be executed to settle the documents
by un cheking the test run indicator.
11. The Accounting Document generated is as follows:
-------------------------------End of document------------------------------------
12. ERS with Planned Delivery Costs:
In the earlier Releases Planned Delivery costs cannot be taken into
account by ERS.
But now it is available in Customising.
Steps:
(1) The Following Customisation is required.
(2) To maintain Transaction MRDC in Table T169F
(You can maintain the transaction MRDC directly in table T169F, by T-Code
SE16)
Or from Spro
13.
14. SAVE this setting.
(2) Maintain Condition Record by T-Code MRM1 for the Freight
Vendor:
15. SAVE
(3) T-Code : ME21N Create PO with ERS
Take Vendor 410001 and freight vendor 200004.
16. Planned Delivery Cost is maintained in Condition type FRA1, ie.
Freight % is taken as 2%, and the Freight vendor maintained is
200004.
17. Next save the PO.
(2) ME29N release the PO if required.
(3) MIGO: GR against PO 4500000220
18. Post the Goods receipt document
The Accounting Document generated contains the planned
Delivery cost of Freight.
(4) ERS in Logistics Invoice Verification : T-Code MRRL
Menupath from Sap Easy Access
19. ERS for the Planned Delivery cost can be settled through T-Code :
MRDC or by MRRL only.
MRRL
Test Run
Execute
20. Next we execute de-selecting the Test Run
Execute
Thus Invoice No. 5105600875 is generated for the freight vendor
200004 and Invoice No. 5105600876 is generated for the normal
vendor 410001.
