We often come across the terminology ALE, EDI & IDOC in various project. This tutorial will cover some of the basic concepts of Electronic Data Interchange(EDI), Application Link Enabling(ALE) & intermediate documents (IDOC). Today, ALE, EDI IDocs are used in most SAP applications to transfer messages (information) from the SAP system to other systems and vice versa.ALE, EDI, and IDocs are crucial for connecting systems, streamlining processes, and ensuring efficient data exchange within the SAP ecosystem, ensuring successful implementations and seamless business operations.
Table of Contents
What is ALE?
ALE stands for Application Link Enabling and is a technology for remote connections that enables business processes to be decentralized by linking decentralized systems.
It is fairly simple to synchronize several SAP structures using ALE so that they contain the same data objects at any time. Master data (customers, suppliers, GL accounts, cost centers, …) or transaction data (FI documents, purchase orders, etc.) may be these objects. ALE supports mass data transfers between systems and selective data transfers of objects modified after the last transfer to allow synchronization.
What is EDI
EDI stands for Electronic Data Interchange is defined as the exchange, by electronic means, of structured data according to agreed message standards between computer systems. Structured data is similar to a plain and straightforward way of displaying a document’s data material, be it an invoice, purchase order, or any other form of document
The electronic computer-to-computer exchange of business records that can be processed by computers in a standard format. Electronic Data Interchange (EDI) is about doing business and making transactions electronically with your trading partners. EDI includes most items that are usually done using paper-based correspondence, such as placing orders and carrying out financial transactions with suppliers.
Electronic Data Interchange (EDI) is a standardized format that allows one company to send information electronically rather than on paper to another company for the electronic exchange of business information. Trading partners are called business organizations that perform business electronically.
The basic EDI principle is to convert data from one format to another. There are many standards that are used, with ANSI X12 (American Standard) and EDIFACT being the most commonly used (European Standard). Most conversion work is done with EDI software. Packages can be used to convert a flat-file format to a regular EDI file that deletes all blank spaces and uses standard codes and qualifiers to separate field values.
The method by which the computer system ensures the correct interpretation of the information is specified Since R/3 Release 2.2x, SAP has provided support for EDI and continues to develop its solution, realising the importance of EDI as a key business enabler early on.
The Electronic Data Interchange component in SAP consists of an Intermediate Document (IDoc).We can use the interface for the below-described way
What is EDI Standards
EDI is an electronic business document exchange between business partners’ computer systems using a common format over a communication network. For electronic data interchange, Two commonly used standards are ANSI ASC X12 and EDIFACT for transmitting information electronically. ANSI ASC X12 is a committee consisting of members of major organizations, government agencies and EDI software companies that determine EDI knowledge-sharing requirements and guidelines.
UN/EDIFACT stands for the United Nations EDI for Government, Commerce and Transport and was developed in 1985 using ANSI X12 and UNTDI as basic standards (United Nations Exchange Data Interchange).
ANSI X12 identifies business papers as transactions and each transaction is defined by a three-digit number, e.g. 880-Purchase Order, 885-Purchase Order Recognition.
How does it work?
The method is straightforward and simple, seen from a high-level perspective: a sender system selects the data that needs to be transmitted, packs it in a standard format and sends it to one or more receiving systems. It unpacks the standard format and records the data when a receiving device gets the data.
In reality, in this process, 3 layers are involved:
- An application layer that selects and records R/3 data.
- A distribution layer that filters and transforms information.
- A communication layer that ensures the actual communication in a standard format of records generated.
Thanks to a so-called distribution model that determines the transmission rules (who sends what to who?), the senders and receivers are decided. All the systems involved (either as the sender or receiver) must be familiar with the concept of the distribution model and must therefore exist on all those systems.
Data Sending:
- The computer system functions as a repository for data.
- EDI collects knowledge from current programmes for computers.
- Transmits paperless, computer-readable telephone-line papers.
Data Receiving:
- It is directly fed into a computer system.
- Processed and interfaced with internal software automatically.
- Time Processing
- Achieved in minutes.
- No re-keying whatsoever.
- No shuffling of documents.
- No attendant charges for preparation and distribution of manual papers.
What is IDOC in SAP?
IDocs stands for intermediate Documents. An IDoc is essentially a data container used to share data between any two processes that can comprehend the data’s syntax and semantics.
In most SAP applications, IDocs are usually used to transfer message information from the SAP system to other systems and vice versa. While there is a lot of documentation available on IDocs, because of their technical nature, it is difficult for a practical consultant to understand such documents. Although the IDoc principles are not supposed to be completely understood by a practical consultant, an attempt has been made to collect the minimum required knowledge that one needs to be aware of in order to deal with project/support issues on IDocs..
IDoc is a SAP entity that brings, in the form of an electronic message, business transaction data from one device to another. IDoc is an acronym for Document Intermediate. An IDoc is intended to transfer SAP data or information to other systems and vice versa. The transition from SAP to a non-SAP system takes place through subsystems of EDI (Electronic Data Interchange), while ALE is used for the transfer between two SAP systems.
In the SAP system or in the EDI subsystem, IDoc can be activated. This depends on the way IDoc is sent and is thus referred to as Inbound IDoc and Outbound IDoc. IDoc is triggered in SAP in the event of outbound flow via document message control, which is then sFor inbound flow, EDI converts partner data and IDoc is created in SAP. After the IDoc has been successfully Posted , the Application Document is posted/ created to SAP.
What are the advantages of EDI
- Reduced data entry errors during manual processing
- Reduced cycle processing time, distribution in real-time,
- Availability of electronic format data
- Lowered Paperwork
- Reduced costs
- Inventory reduction and better preparation
- Standard means of communication
- Better Method for Company
- Competitive gain
What is IDOC type in SAP?
There are two type of Idocs type in SAP
What is Outbound IDOC in SAP
Outbound Idoc Messages- Sending messages such as an order confirmation through Electronic Data Interchange (EDI) to the third-party system. Outbound Messages used for sending EDI messages. In the outbound processing, document data is written to IDocs and sent to the receiving system.The following outbound EDI messages are available in Sales and Distribution:
- Sending Quotation information
- Sending Order Confirmation
- Order Changes request
- Delivery Creation
- Shipping Notifications processing
- Sending Invoice information to the third party, etc .
What is inbound IDOC in SAP?
Inbound IDOC messages –Inbound IDOC messages are used to receive such as a sales order request through EDI from the third-party companies. In inbound Idoc processing, IDocs are transferred to the IDoc interface and stored in the SAP System. Data from the document is produced in a second phase. In Sales and Distribution, the following inbound EDI message types are available:
- Receive inquiries for customer
- Receive sales orders Request
- Receive Sales Order change request
- Receive forecast delivery schedules
- Received credit memos
- Receive delivery creation notifications from from external agent suppliers,etc
What is the IDOC status in SAP?
There are many status lists for Idocs, Outbound IDOC status starting with 01 to 42 status. Below the list of all Outbound status codes.
| IDoc status | Direction | Processing level | Description |
| 01 | Outbound | IDoc Interface (SAP) | IDoc generated |
| 02 | Outbound | IDoc Interface (SAP) | Error passing data to port |
| 03 | Outbound | IDoc Interface (SAP) | Data passed to port OK |
| 04 | Outbound | External system/EDI subsystem | Error within control information of EDI subsystem |
| 05 | Outbound | External system/EDI subsystem | Error During Translation |
| 06 | Outbound | External system/EDI subsystem | Translation OK |
| 07 | Outbound | External system/EDI subsystem | Error during syntax check |
| 08 | Outbound | External system/EDI subsystem | Syntax check OK |
| 09 | Outbound | External system/EDI subsystem | Error during interchange handling |
| 10 | Outbound | External system/EDI subsystem | Interchange handling OK |
| 11 | Outbound | External system/EDI subsystem | Error during dispatch |
| 12 | Outbound | External system/EDI subsystem | Dispatch OK |
| 13 | Outbound | External system/EDI subsystem | Retransmission OK |
| 14 | Outbound | External system/EDI subsystem | Interchange Acknowledgement positive |
| 15 | Outbound | External system/EDI subsystem | Interchange Acknowledgement negative |
| 16 | Outbound | External system/EDI subsystem | Functional Acknowledgement positive |
| 17 | Outbound | External system/EDI subsystem | Functional Acknowledgement negative |
| 18 | Outbound | IDoc Interface (SAP) | Triggering EDI subsystem OK |
| 19 | Outbound | IDoc Interface (SAP) | Data transfer for test OK |
| 20 | Outbound | IDoc Interface (SAP) | Error triggering EDI subsystem |
| 21 | Outbound | IDoc Interface (SAP) | Error passing data for test |
| 22 | Outbound | External system/EDI subsystem | Dispatch OK, acknowledgement still due |
| 23 | Outbound | External system/EDI subsystem | Error during retransmission |
| 24 | Outbound | External system/EDI subsystem | Control information of EDI subsystem OK |
| 25 | Outbound | IDoc Interface (SAP) | Processing despite syntax error (outbound) |
| 26 | Outbound | IDoc Interface (SAP) | Error during syntax check of IDoc (outbound) |
| 27 | Outbound | IDoc Interface (SAP) | Error in dispatch level (ALE service) |
| 28 | Outbound | IDoc Interface (SAP) | IDoc sent to ALE distribution unit retroactively |
| 29 | Outbound | IDoc Interface (SAP) | Error in ALE service |
| 30 | Outbound | IDoc Interface (SAP) | IDoc ready for dispatch (ALE service) |
| 31 | Outbound | IDoc Interface (SAP) | Error – no further processing |
| 32 | Outbound | IDoc Interface (SAP) | IDoc was edited |
| 33 | Outbound | IDoc Interface (SAP) | Original of an IDoc which was edited |
| 34 | Outbound | IDoc Interface (SAP) | Error in control record of IDoc |
| 35 | Outbound | IDoc Interface (SAP) | IDoc reloaded from archive |
| 36 | Outbound | External system/EDI subsystem | Electronic signature not performed (timeout) |
| 37 | Outbound | IDoc Interface (SAP) | IDoc added incorrectly |
| 38 | Outbound | IDoc Interface (SAP) | IDoc archived |
| 39 | Outbound | IDoc Interface (SAP) | IDoc is in the target system (ALE service) |
| 40 | Outbound | IDoc Interface (SAP) | Application document not created in target system |
| 41 | Outbound | IDoc Interface (SAP) | Application document created in target system |
| 42 | Outbound | IDoc Interface (SAP) | IDoc was created by test transaction |
Similarly, inbound IDOC status starting with 50 to 75 status.Below list of all inbound status codes.
| IDoc status | Direction | Processing level | Description |
| 50 | Inbound | IDoc Interface (SAP) | IDoc added |
| 51 | Inbound | SAP application | Application document not posted |
| 52 | Inbound | SAP application | Application document not fully posted |
| 53 | Inbound | SAP application | Application document posted |
| 54 | Inbound | SAP application | Error during formal application check |
| 55 | Inbound | SAP application | Formal application check OK |
| 56 | Inbound | IDoc Interface (SAP) | IDoc with errors added |
| 57 | Inbound | SAP application | Test IDoc: Error during application check |
| 58 | Inbound | IDoc Interface (SAP) | IDoc copy from R/2 connection |
| 59 | Inbound | IDoc Interface (SAP) | Not used |
| 60 | Inbound | IDoc Interface (SAP) | Error during syntax check of IDoc (inbound) |
| 61 | Inbound | IDoc Interface (SAP) | Processing despite syntax error (inbound) |
| 62 | Inbound | IDoc Interface (SAP) | IDoc passed to application |
| 63 | Inbound | IDoc Interface (SAP) | Error passing IDoc to application |
| 64 | Inbound | IDoc Interface (SAP) | IDoc ready to be transferred to application |
| 65 | Inbound | IDoc Interface (SAP) | Error in ALE service |
| 66 | Inbound | IDoc Interface (SAP) | IDoc is waiting for predecessor IDoc (serialization) |
| 67 | Inbound | IDoc Interface (SAP) | Not used |
| 68 | Inbound | IDoc Interface (SAP) | Error – no further processing |
| 69 | Inbound | IDoc Interface (SAP) | IDoc was edited |
| 70 | Inbound | IDoc Interface (SAP) | Original of an IDoc which was edited |
| 71 | Inbound | IDoc Interface (SAP) | IDoc reloaded from archive |
| 72 | Inbound | IDoc Interface (SAP) | Not used, only R/2 |
| 73 | Inbound | IDoc Interface (SAP) | IDoc archived |
| 74 | Inbound | IDoc Interface (SAP) | IDoc was created by test transaction |
| 75 | Inbound | IDoc Interface (SAP) | IDoc is in inbound queue |
How are IDOC triggered in SAP?
IDOC can be triggered using a functional module or using the program. If it is a typical Outbound IDOC, the FM IDOC OUTPUT ORDERS is likely to produce it.
There could be a custom program that could use the FM MASTER IDOC DISTRIBUTE to produce the standard as well as custom outbound IDOC. If you place a breakpoint on the FM and attempt to generate the IDOC, you will be able to trace the program using the call stack.
What is the SAP IDOC interface?
Standard SAP interfaces provide options for connecting external systems to SAP which we call as a interface.SAP interfaces allow data exchange with the SAP system for any other applications and other solutions.
How do I process an IDOC in SAP?
Generally, there is various IDOCS processing program available in the standard SAP. Which schedule as background jobs as per processing status and timing defined by the administrator. We can process docs manually if required using transaction code BD87
How do I find the IDOCtype Documentation?
We can get SAP IDOC documentation using transaction code WE60, For instance, for the invoice, we want to know Information such as compulsory and optional segments, the minimum and maximum number of segments, etc.
Hope this article helps you to understand EDI, ALE & IDOC basic concepts.We will cover IDOC configuration in the upcoming post..Here are a couple of other articles that you check
