4 minute read

Difference between IDocs, ALE, RFC and EDI in a SAP ERP system

Various terms and concepts will crop up when data is exchanged with a SAP ERP system, whether communication is handled via in-house or external systems. This article discusses the relationship between IDocs, ALE, RFC and EDI in a SAP ERP system and points out which concepts to use and where.

IDoc – Intermediate Document

IDocs is the standard exchange format used for importing/exporting data into/from SAP systems. Business data such as master data, invoices, delivery notes etc. may be exchanged with external systems via IDoc interfaces. These external systems may be within your own company or data may be exchanged with systems belonging to other companies.

An IDoc interface has a defined data structure and IDoc processing logic. For more information on the detailed structure of IDocs please see this article.

The SAP term for data exchange with other in-house systems is ALE (or Application Link Enabling). The term EAI stands for Enterprise Application Integration and is also commonly used in non-SAP environments. ALE communication may be synchronous or asynchronous.

Data exchange to other companies is referred to as Electronic Data Interchange, or EDI. EDI communication is message-based and thus always asynchronous.

The figure below shows an example of a scenario with ALE and EDI.


Difference between ALE and EDI
Difference between ALE and EDI

Customers and suppliers are linked to the SAP system via EDI. In-house third-party software such as CRM (Customer Relationship Management), HR (Human Resources) and PDM (Product Data Management) will be linked via ALE.

White Paper - EDI Integration in SAP

ALE – Application Link Enabling

Within the ALE framework, business processes take place across different in-house IT systems. The systems are physically separate, and communication takes place between different Logical Systems (LS).

A logical system is comprised of specific software such as CRM systems. In SAP, a logical system is assigned to a client and has an own system name. Logical systems may be defined in SAP using Transaction BD54, as shown in the figure below.


Logical systems in Transaction BD54
Logical systems in Transaction BD54

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

Specific clients are assigned to a logical system via Transaction SCC4.

A distribution model must be set up to define which IDocs to exchange using which logical system. A distribution model may be defined using Transaction BD64.

ALE is based on RFC (Remote Function Call) for communication.

RFC – Remote Function Call

RFC is another commonly seen EDI acronym and stands for Remote Function Call. RFC a process used to call up a function (also referred to as function module in SAP) in a remote system. Business logics may thus be called up in a third-party system.

In the SAP environment RFC is effectively synonymous with Remote Procedure Call (RPC), but it is also used as an umbrella term for SAP interfaces and protocols used for the implementation of function calls.

A DESTINATION parameter is given when calling up a remote function module in ABAP. The following is an example of a call-up of the STORE_NEW_CUSTOMER function in the CRM4711 system.

  CALL FUNCTION 'STORE_NEW_CUSTOMER'
    DESTINATION 'CRM4711'
    EXPORTING
      customer = cust
    IMPORTING
      crm_customer_id = id
    EXCEPTIONS
      customer_exists = 1

A customer object is passed to this method, to store in the CRM system. The CRM system customer ID number is returned to, for instance, store with the master debtor data in the SAP system.

SAP distinguishes between four different types of RFCs:

  • Synchronous (sRFC)
  • Asynchronous (aRFC)
  • Tranactional (tRFC)
  • Queued (qRFC)

EDI – Electronic Data Interchange

Data exchange with other companies is referred to as EDI (Electronic Data Interchange). Instead of the direct exchange of IDocs, data will first be converted to a uniform exchange format, the so-called EDI format. Well known EDI formats include, for instance, UN/EDIFACT, ANSI ASC X12, VDA etc. and the corresponding derivatives and sub-standards.

An EDI converter is used for conversion between IDocs and the EDI format.

SAP systems do not use logical systems for electronic data exchange, but they define partners. These partners may, for instance, be customers or suppliers. The settings for specific partners are also called partner agreements and configured in Transaction WE60.

Any questions about SAP, IDocs, ALE, RFC or EDI?

Do you have any questions about SAP ERP, SAP SD and the associated EDI processes? Please contact us or check out our chat – we look forward to assisting you!

Alternatively, please see our resources section to check out some of our many helpful webinars, infographics and white papers!

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

EDI_DC40: Understand the SAP IDoc Control Record

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.