Introduction to EDI and ALE:EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.EDI is also called paperless exchange.Advantages:Reduced Data entry errorsReduced processing timeAvailability of data in electronic formReduced paperworkReduced CostReduced inventories and better planningStandard means of communicationsBetter business process

EDI has two process1. Outbound process2. Inbound process

Outbound Process:1.Application document is created.2. IDOC is generated3.Idoc is transferred from SAP to Operating system layer4.Idoc is converted into EDI standards5.Edi document is transmitted to the business partner6.The Edi Subsystem report status to SAP

Inbound Process:1.EDI transmission received2.EDI document is converted into an IDOC3.IDOC is transferred to the SAP layer4.The application document is created5.The application document can be viewed.

IDOC:IDOC is a container that can be used to exchange data between any two processes.Each IDOC is assigned a unique number for tracking and future reference.IDOC consists of several segments, and segments contain several fields.IDOC contains the following three types of records...1. One Control Record.2. One or many Data Record3. One or many Status record.In IDOCs the following terms are to be known.PORT:Port is used in the outbound process to determine the name of the EDI subsystem program, the directory path where the IDOC file will be created at the operating system level, the IDOC file names and the RFC destinations.

RFC Destination:Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.

Partner Profile:Partner profile specified the various components used in an outbound process (Partner number, IDOC type, message type, Port, Process code), the mode in which it communicates with the subsystem (batch or immediate) and the person to be notified in case of errors.

Message ControlUsed in pricing, account determination, material determination, and output determination. The message control component enables you to encapsulate business rules with out having to write ABAP programs.TO Process IDOCS the following TCODES will be used.On both sides:Logical System Names SALESetup RFC destinations SM59Port Destinations WE21In Source system:Segment Creation WE31Basic IDOC Type Creation WE30Message Type Creation WE81Assign Message Type To Basic IDOC Type WE82Distribution Model BD64Writing Report Program SE38Partner Profile WE20Message control NACECheck IDOCs WE02, WE05In Destination System:Creating FM SE37Assign FM to Logical Message WE57Define I/P method for Inbound FM BD51Create Process Code WE42Generate Partner Profile BD64IDOC processing in the same instance of R/3 Clients.For example two clients in the same R/3 instance.Client 900.Client 800.To transfer the data between two clients the table structures and their data types should be match.