Dear SCN Member,
In order to fully benefit from what SCN has to offer, please register at:
Thank you,
The SCN team
Skip to end of metadata
Go to start of metadata


The purpose of this page is to give an overview of EDI functionality, main configurations, SAP Notes and SAP Documents related.


The following sections will explain some points of EDI functionality, showing configurations and some tips that may help during invoices creation and issue resolution.

Electronic Data Interchange - EDI

Defining ALE, EDI and IDOC

ALE means Application Link Enabling and is used between SAP systems. ALE is generally used to transmit Master Data information as material, vendor, customer, conditions, etc.

EDI means Electronic Data Interchange and is used between SAP systems and external systems. When thinking about MM-IV processes, EDI enables a vendor to transfer invoice information electronically instead of in the form of a printed paper invoice.

IDOC means Intermediate Document, and is used during ALE and EDI processes. An IDoc is generated for each invoice and the system posts an invoice using the data in this IDoc. To obtain more information regarding invoices via EDI, document Invoices Received via EDI (MM-IV) can help.

Most Used Transactions

To work with EDI there are some main transactions, that will be showed below.

To check the customizing, SPRO Path is:


If there is a doubt regarding the structure of the IDOC, a good way to find information is via transaction WEDI. This transaction is for IDoc and EDI Basis, with a very good documentation in the highlighted section showed below:


To check an IDOC, go to WE02, which is the IDoc List:


To check and process an IDOC, it is possible to use BD87 transaction:


To create and process a new IDoc use WE19 transaction, which is the Test tool for IDoc processing.

Just keep in mind that, to process an IDoc, a new IDOC will be created and only then is possible to process it.

This is the transaction:


Partner profiles are obligatory when working with IDOCs, and, to create or to edit one, use transaction WE20:


Obligatory Configuration

It is important to have a partner configured, and to create one, use transaction WE20.

For IV, it is necessary to create a Vendor Partner LI. For this partner is necessary to fill "Message Type" with "INVOIC" (INVOIC01 or INVOIC02) and the field "Process Code" with "INVM" or "INVL", as showed below:


Still under Partner settings, via WE20, ensure "Identification" is filled with the standard MM-IV function, which is IDOC_INPUT_INVOIC_MRM. In order to see this, just double-click in the "Process code" field (showed above) and you will be redirected to this screen:


Tax Code must have a relation between the systems, having a corresponding on the SAP system for the Tax Code from the Vendor.

To create this relation use OBCD transaction.

The "Tax Type" field comes from the Vendor and the "Tx" field is the corresponding on the SAP side:


Also, Company Code must have relation between systems, and this is done via OBCA transaction.

In this case, "Partn.Type" and "PartnerNo" fields must present "CoCd" (Company Code) filled, which is the corresponding on SAP side.

"Comp.code name in the invoice" field comes from Vendor:


There are some details to configure, about how the invoice will be further processed.

For example, in case there is an error, the invoice can be parked; or, system can check tolerances configured before posting the invoice.

To configure these details, go to OMRY transaction:


1) When found a syntax error on WE19 transaction, the issue is on the IDoc from Vendor. So, customer should contact the Vendor informing him about the issue.

2) If there is a business need to park an invoice created via EDI all the times, or, for specific vendors, keep in mind that via standard system this is not possible. But, to attend this need can be used user exit EXIT_SAPLMRMH_014. For more details, check SAP Note 501524 - EDI: Parking incoming invoices by default.

3) If IDOC has multiple references to the same purchase order item, system may raise error M8321 - "Document contains same order item more than once". For example, there is 1 purchase order item with reference to 2 Goods Receipt with the same Delivery Note number. In this case, system will raise error M8321. This is standard, and for more information check SAP Note 103051 - EDI: Multiple reference to same purchase order item. 

Related Content

Related Documents

Invoices Received via EDI (MM-IV) 

Inbound Processing of IDocs Received

Goods Receipt Determination 

Processing EDI Invoices 

Related SAP Notes/KBAs

SAP KBA 1870771 - Not possible to create an invoice via IDOC due to error M8183

SAP KBA 1911683 - Payment Term is not transferred to the Invoice created via EDI process

SAP Note 103051 - EDI: Multiple reference to same purchase order item
SAP Note 394316 - EDI: Check for duplicate invoice not possible
SAP Note 501524 - EDI: Parking incoming invoices by default
SAP Note 506343 - EDI: Determination of a tax indicator
SAP Note 518660 - FAQ: Inbound EDI message in the invoice verification
SAP Note 944164 - EDI: Terms of payment from the first purchase order

1 Comment

  1. EDI is translated to IDOC in SAP. For each of EDI messages, there is a corresponding IDOC message.

    For Supply chain, they key IDOC are

    8. REMADV/PEXR2002