Sending an ERS Document via EDI (MM-IV-LIV)
Use
In the EDI scenario, goods receipts are settled using Evaluated Receipt Settlement (ERS procedure), in which the invoices and the corresponding FI postings are generated. An ERS document is sent via EDI as verification of the transactions settled.
The scenario runs within a scheduling agreement. ERS documents can also be sent for individual purchase orders.
Prerequisites
Application
Output Control
The following condition components must have been maintained:
Condition Component |
Value |
Access sequence |
0002 |
Condition |
0 |
"Exclusive" |
select |
Output type |
ERS6 (ERS procedure by EDI = transmission medium 6) |
Schema |
MR0004 (ERS procedure) |
Application |
MR |
Processing subroutine |
Program RSNASTED , form routine EDI-PROCESSING |
General data |
Select Condition access and Multiple sending of output, otherwise leave the fields blank |
Time |
such as 4 (immediately, IDocs are generated immediately after posting) |
Transmission medium |
6 |
Partner function |
LF |
You can define condition records from Logistics Invoice Verification by selecting Environment.
IDoc Interface
You must maintain the following values for both the outbound partner profiles and the additional partner profiles for outbound processing using output control:
Field |
Value |
Message type |
GSVERF |
Partner type |
LI (vendor) |
Partner function |
LF (vendor) |
Port |
SUBSYSTEM |
Output mode |
such as Collect IDocs |
Basic type |
GSVERF01 |
Application |
MR |
Output type |
ERS6 or the type you have defined |
Transaction code |
MRRL |
Activities