ALE is sap Technology to support distributed yet integrated processes across level SAP System. ALE is sap Technology to support distributed yet integrated processes across level SAP System. A Distributed process is one in which part of a business process is carried out on one system and part on another. Sap Introduced ALE as its initiative to support a distributed yet integrated environment.ALE allows for efficient and Reliable communication between distributed processes across physically separate sap systems to achieve a distributed yet integrated logical sap system. What is the Distributed

ALE have Three Parts n Out bound n Inbound n Exception handling

Outbound. Sending out the data from our system. The IDOC which is called as Outbound IDOC Start a OutBound Program Outbound ALE program Master Idoc ALE Service Layer Application Repository Application data Idoc data Communcation layer ALE Distribution Model Receiver1 Receiver2 Receiver3 Receiver4 Step1 Step2 Step3 Step4

The Technical flow an outbound process for Masterdata Begin Objects to be distributed are selected Data is read from the databa se and formatted into IDOC format ALE service layer is invoked via MASTER_IDOC_DISTRIBUTE ALE Distribution model is cons ulted to determine recipients Filtering conversion & Version change are carried out for each recipient Communcation Idocs are saved in the database Collect Idocs Execute RSEOUT00 Program Idoc Packets are stored in the ARFC Data Execute RSARFCEX,which calls INBOUND_IDOC_PROCESS on the Remote System Successful Done No Yes

n Master IDOC The document or Masterdata to be sent ready from database and formatted into an idoc format.This idoc called as a Master idoc. n Communication IDOC The ALE layer generates a separate idoc from the Master idoc for each recipient.Who is intrested in the data. Separate IDOCs are Generated because each recipient might demand a different version or a subset of the Master Idoc.These recipient specific Idocs are called communcation idocs. n Note : The Master IDOC is kept in Memory buffers until communication IDOCS are generated. Communcation Idocs are stored in database.

Inbound n When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound Idoc. n The process occurs in the reciever system called inbound system. n The inbound process must handle three types of data.Transactional and Master data are received via the ALE interface layer.control data is received via CTS process.

The inbound process using a direct function module Communcation IDOC from remote system Conversion Filtering Version Change IDOC_INBOUND_ASYNCHRONOUS Application Idocs RBDAPP01 Posting Program Direct Input function module Application Repos itory Communication Layer ALE Service Layer

The Technical flow of the inbound process using a direct function Module Begin Remote system calls IDOC_INBOUND_ASYNCHR ONOUS and passes communication idoc to the system Userid is validated & authorizations are checked Data in the control record is validated against the partner profile ALE Services : Filtering conversion & Version change are carried out Application Idoc is saved the databasecs are saved in the database Process Idoc immediately Program RBDAPP01 is Executed Read process code from the part ner profile Process code points to the posting module Yes No Done Posting Module creates the applicat ion document

n Store the Idoc in the Database : First an idoc is received in the system and stored in the database.The idoc goes through a basic integrity check and syntax check.If every thing is fine,the next step is performed. n Invoke the posting Module : The control information in the idoc and configuration tables are read to determine the posting program. The Idoc is then transferred to its posting program. n Create the Document : The posting program reads the idoc data and then creates a document in the system.The results are logged in the idoc.

Exceptionhandling n Any errors occurs while tranfering the data from one system from another is recievingfield by the exception handling process.Errors can be identified by status code generated by the idoc. They are Two Types Exception handling process 1) Outbound 2) Inbound

Outbound Exception Handling Data Transfer NO Execute RBDBOIND Checkbox 12-Data System

0 to 50( error occurrs in Outbound process) n n 01 IDoc created n n 02 Error passing data to port n n 03 Data passed to port OK n n 04 Error within control information of EDI subsystem n n 05 Error during translation n n 06 Translation OK n n 07 Error during syntax check n n 08 Syntax check OK n n 09 Error during interchange handling n n 10 Interchange handling OK n n 11 Error during dispatch n n 12 Dispatch OK n n 13 Retransmission OK n n 14 Interchange Acknowledgement positive n n 15 Interchange Acknowledgement negative

n n 16 Functional Acknowledgement positive n n 17 Functional Acknowledgement negative n n 18 Triggering EDI subsystem OK n n 19 Data transfer for test OK n n 20 Error triggering EDI subsystem n n 21 Error passing data for test n n 22 Dispatch OK, acknowledgement still due n n 23 Error during retransmission n n 24 Control information of EDI subsystem OK n n 25 Processing despite syntax error (outbound) n n 26 Error during syntax check of IDoc (outbound) n n 27 Error in dispatch level (ALE service) n n 29 Error in ALE service n n 30 IDoc ready for dispatch (ALE service) n n 31 Error - no further processing n n 32 IDoc was edited n n 33 Original of an IDoc which was edited

n 34 Error in control record of IDoc n 35 IDoc reloaded from archive n 36 Electronic signature not performed (timeout) n 37 IDoc added incorrectly n 38 IDoc archived n 39 IDoc is in the receiving system (ALE service) n 40 Application document not created in receiving system n 41 Application document created in receiving system n 42 IDoc was created by test transaction

0 to 50( error occurrs in Outbound process) n n 50 IDoc added n n 51 Error: Application document not posted n n 52 Application document not fully posted n n 53 Application document posted n n 54 Error during formal application check n n 55 Formal application check OK n n 56 IDoc with errors added n n 57 Test IDoc: Error during application check n n 58 IDoc-Copy from an R/2 connection n n 60 Error during syntax check of IDoc (inbound) n n 61 Processing despite syntax error (inbound) n n 62 IDoc passed to application n n 63 Error passing IDoc to application n n 64 IDoc ready to be transferred to application n n by test transaction n n

n n 63 Error passing IDoc to application n n 64 IDoc ready to be transferred to application n n 65 Error in ALE service n n 66 IDoc is waiting for predecessor IDoc (serialization) n n 67 Not used n n 68 Error - no further processing n n 69 IDoc was edited n n 70 Original of an IDoc which was edited n n 71 IDoc reloaded from archive n n 73 IDoc archived n n 74 IDoc was created by test transaction