5 minute read

What is the SAP IDoc format?

Data exchange with an SAP system

Before we examine SAP IDoc formats, we must first define the phrase SAP system. When we talk about SAP system in the context of this article, we mean SAP ERP. This system used to be known as SAP R/3 (you may still hear SAP veterans use this term today). Later, the term mySAP ERP became the common nomenclature. Today, the term SAP ERP is common. More recently also its successor SAP S/4HANA.

Other systems, such as SAP Business ByDesign or SAP Business One, play no role in this IDoc contribution – there are other data exchange concepts for these systems.


Start screen of an SAP ERP system
Start screen of an SAP ERP system

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

IDocs are used to import data into and export data from an SAP system. Data refers to business relevant information, which is often exchanged with external business partners using electronic data interchange (EDI). This includes information relating to orders, delivery notes, invoices, material master data etc.

XML vs. Fixed-length format

IDocs can be found in two different forms – either as fixed-length format (especially in older SAP systems) or as an XML-based format. In the following we will only discuss the newer XML-based format.

White Paper - EDI Integration in SAP

IDoc documentation

To get an overview of the IDocs currently configured in SAP, you can use transaction WE60. SAP uses EDIFACT-like abbreviations to identify IDocs. Anyone familiar with EDIFACT will be quickly able to identify the different types such DESADV, ORDERS, INVOIC, etc. This is not surprising, since the IDoc structure is based on the EDI standards ANSI ASC X12 and EDIFACT.

The following figure shows transaction WE60 and the example IDoc type DELVRY03.


DELVRY03 IDoc type
DELVRY03 IDoc type

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

IDoc XML schema

The documentation relevant for electronic data exchange can be found in the corresponding IDoc XML schema and the accompanying documentation. After selecting the IDoc type DELVRY03, the corresponding XML schema can be displayed using the menu item Documentation > XML Schema. The XML Schema is the basis for the realization of document mappings – e.g. from IDoc to EDIFACT or vice versa.

The following figure shows an overview of the XML schema of the DELVRY03 IDoc type, using the tree view of Altova XMLSpy. The elements are grouped under a DELVRY03 root element, which in turn contains a header record EDI_DC40 (more on that here) and up to 9,999 delivery header items of type E1EDL20.


DELVRY03 IDoc XML Schema structure
DELVRY03 IDoc XML Schema structure

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

IDoc documentation

To find out what’s behind the abbreviated names of the XML elements, one has to consult the IDoc documentation. The documentation can also be retrieved using transaction WE60. After selecting the IDoc type DELVRY03, the corresponding documentation can be displayed as HTML file by selecting Documentation > HTML Format.

In order to get a complete documentation, the two checkboxes Documentation Output and Field Value Output should be activated in the user settings, as shown in the following illustration. The user settings can be accessed in transaction WE60 by selecting the menu item Goto > User settings.


IDoc documentation export options
IDoc documentation export options

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

The following figure shows the resulting HTML documentation. Using the menu item Documentation > Export one may download the HTML files onto the local hard disk. Other options, such as PDF export, are not available.


IDoc DELVRY03 documentation
IDoc DELVRY03 documentation

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission of SAP SE.

Together with the corresponding XML schema, the structure and semantics of an IDoc can now be decrypted relatively easily.

Transaction WE19 is also very useful for testing IDocs or finding possible values for a certain field. If the IDoc is not yet available in the SAP system, one may use transaction CG3Z to manually upload the IDoc.

How do I make my SAP system EDI-ready?

In order to be able to exchange EDI files with other business partners, such as suppliers or customers, a service provider can be used. The service provider takes care of the correct translation of IDocs to the target EDI document formats as well as the correct delivery of EDI documents to the business partners.

For the realization of the connection between the service provider and an SAP ERP system, ecosio together with EPO Consulting GmbH has developed the high-performance and flexible EPO connector.


Electronic data exchange with ecosio and EPO connector
Electronic data exchange with ecosio and EPO connector

Any questions about IDocs or EDI?

You still have questions about SAP, IDocs or EDI? Please do contact us or use our chat — we’re more than happy to help!

 

SAP ERP and SAP S/4HANA are the trademarks or registered trademarks of SAP SE or its affiliates in Germany and in several other countries. 

most read

Keep on reading

3 minute read

How to create an SAP transaction code

Want to know how to create an SAP transaction code for an existing ABAP program so that you can easily call the program?

6 minute read

How to Set Up and Manage Automatic SAP Jobs

SAP jobs can be used to automate processes in SAP ERP so they can be carried out without user intervention. We explore the key features.

4 minute read

IDoc Status Change in SAP ERP

IDoc statuses are not always the clearest - particularly when errors occur. In this article we explain how to change IDoc status as required.

5 minute read

How Can I Add an Entry to an SAP Table?

In this article we show how to add entries to an existing SAP table - even if it does not have its own maintenance dialog.

5 minute read

Alternatives to the Seeburger PI Adapter

The end of maintenance for the Seeburger PI Adapter is imminent. What alternatives are there and which is the best suited for your business?

4 minute read

IDocs in SAP S/4HANA: The Differences to SAP ECC 6.0

The change to S/4HANA also impacts the format of IDocs. In this article we explore IDocs in S/4HANA and the new and changed elements.

11 minute read

Migration to SAP S/4HANA - 5 Key Considerations

Are you prepared for migration to SAP S/4HANA? Discover the 5 key questions all businesses looking to upgrade to SAP's new ERP system should consider.

11 minute read

Exchange of Electronic Invoices with the SAP eDocument Framework

Companies have to increasingly implement e-Invoicing for different countries. This blog post explains how the SAP eDocument Framework can help you.

2 minute read

How Can You Save an IDoc from SAP on Your Hard Drive?

Wondering how to export IDocs as a file on your local computer? We created a handy guide!

5 minute read

Create and Process UBL Documents with Attachments in SAP

Enable your SAP solution for UBL based e-Invoicing over Peppol. Click here for an example case based on the XRechnung in Germany.

6 minute read

IDoc Processing in an SAP ERP System with Transaction BD87

Companies utilising SAP ERP and exchanging documents need a central tool to manage, view and search for IDocs. Transaction BD87 is the answer.

12 minute read

Understand and Interpret the SAP IDoc Control Record EDI_DC40

A correctly filled control header is essential for the identification and processing of IDocs. We show what settings are needed in SAP.

We use cookies to provide an optimal website experience. You decide which one you want to allow. Depending on the setting, however, not all functionalities may be available to you. Data protection & imprint.