Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 


Former Member
0 Kudos

Hi experts,

I want to know about EDI.

1.What is the steps to process edi?

2.What is 830,810,etc., what are all these number represents.That is 810 is invoice..How we send the 810 from external system..I cant understand this.explain me please..

Thank u,

Manjula Devi.D


Active Participant
0 Kudos

Hi Devi,

EDI stands for Electronic Data Interchange.It is mainly an interface which acts as a moderator between SAP and non SAP system.EDI is used to transfer Datas to R/3 from NonSAP system or Other SAP system.

EDI uses IDOC as its interface component.Which mean EDI is a concept and IDOC is like protocol.

EDI is configured in the R/3. It has Outbound folder and indboud folder.

Outbound folder:This contains the data to be send to the nonSAP system

Inbound folder:

This contains the data from the nonSAP to R/3 or SAP system.

status processing

This holds the status of message from SAP to NonSAP and from Non-SAP to SAP. So that if any error occurs in transfereing Message it is easily traced out.

You can refer from this sites

Check the following links

See the below links




Check this for Conversions-


Cn you plz let me know ifyou have any queries

Former Member
0 Kudos


The EDI interface is used to connect an EDI subsystem to the SAP system. EDI subsystems perform all EDI-related tasks such as Converting the data Handling messages or interchanges Communications Managing the partner profiles Monitoring processing. The EDI interface is based on IDoc technology. IDoc technology is independent of EDI standards. All data is exchanged via files between the SAP System and the EDI subsystem. The synchronous RFC (remote function call) is used to define the time of transfer of the files between both systems. Via the EDI interface, the following data can be exchanged:

Outbound IDocs. IDocs are transferred from the SAP System to the EDI subsystem.

Inbound IDocs. IDocs are transferred from the EDI subsystem to the SAP System.

Status report. To inform the SAP System of the progress of processing of the outbound IDocs, the EDI subsystem transfers the status report to the SAP System.

The object of the certification is the technical test of the interface between SAP System and EDI subsystem. The transfer of outbound IDocs, inbound IDocs and the status report are tested. The test is performed for the EDI standard UN/EDIFACT. As an example, the messages used are:

Outgoing order (ORDERS)

Incoming order (ORDERS)

Outgoing order response (ORDRSP) and

Incoming order response (ORDRSP).

benifits of edi

Reduced data entry errors,

Reduced processing cycle time

Availability of data in electronic form

Reduced paperwork

Reduced inventories and better planning

The Outbound Process

1.The application document is created. The first step in the outbound process involves creating an application document such as a purchase order or sales order and saving it in the database tables. This step is no different from the way in which these documents are normally created. It is the following steps that have relevance to EDI. The document is created and leaves some hooks for the EDI process to begin.

2.the IDoc is generated. The application document just created is now formatted to an IDoc format. At this point you can think of IDoc as yet another format in which the application document has been represented. For example, think of how a date can be stored in different formats—imagine a date as a document with three components: day, month, and year. In one case, you represent it as MM/DD/YYYY, a standard American way of representing a date. To make it meaningful for a German partner, you have to represent it as DD.MM.YY. IDocs follow a similar concept of representing information in different ways. The data in the application document format is suitable for the application modules, screens, and internal programs. A document in an IDoc format is suitable for processing by EDI components, as later sections explain in more detail.

3.The IDoc is transferred from SAP to the operating system layer. The IDoc created in Step 2 resides in the SAP database repository. This IDoc document must be passed down to the operating system layer for processing by the EDI subsystem. In Step 3, the IDoc is transferred to the operating system as a text file. The document is still in an IDoc format. The only difference is the medium of storage.

4.The IDoc is converted to EDI standards. The IDoc format is an SAP proprietary format. For EDI purposes, the document in IDoc format has to be converted into an EDI standard format. Third-party software called a translator carries out the transformation process and reports status back to the SAP system. SAP refers to these translators as EDI subsystems, and has certified several subsystems for connectivity to SAP. SAP takes no responsibility for translation. Thus, from SAP's perspective, after the IDoc is delivered to the subsystem, SAP does not have control over the process, but it maintains the status reported by the EDI subsystem.

Caution SAP does not restrict you to using certified systems, but doing so adds assurance of connectivity, compatibility, and support. Because there are many technical and business issues to worry about, I do not recommend exploring non-certified systems.

5.The EDI document is transmitted to the business partner. After the document is converted to an EDI standard format, it is transmitted to a trading partner based on the partner's EDI settings. This step is not part of the SAP EDI architecture, but is mentioned here to describe the complete process from a business perspective.

6.The EDI subsystem reports status to SAP. When an IDoc is under the control of the EDI subsystem, the subsystem can optionally report the state of processing at various milestones back to the SAP system. This mechanism is always recommended because it provides complete visibility of the process from within SAP, and the user does not have to be involved with the intricacies of the EDI subsystem.

The Inbound Process

The inbound process simply reverses the steps of the outbound process.

The inbound process consists of five steps.

1.The EDI transmission is received. EDI documents are received from a business partner via the VAN. These documents are in one of the EDI standard formats. The documents are deposited in a common repository for the subsystem. This part of the process is not part of the SAP EDI architecture.

2.The EDI document is converted into an IDoc. The EDI-specific headers and trailers are stripped off, and the document is converted into an IDoc format suitable for SAP applications. The process is carried out at the EDI subsystem level.

3.The IDoc is transferred to the SAP layer. The IDoc created in Step 2 is stored in a text file at the operating system layer. The subsystem starts an inbound program in the SAP layer. This program reads the IDoc file and creates an IDoc in the SAP repository for further processing.

4.The application document is created. The IDoc received from the subsystem is passed to a posting program. This program creates an application document such as a sales order, purchase order acknowledgment, invoice, or shipment notice.

5.The application document can be viewed. The application document created via EDI is the same as any document created manually in the system: The document can be viewed using standard application transactions. For example, if an incoming sales order was created via EDI, you could view the sales order document via transaction VA03.