ALE Application Link Enabling introduction

ALE is an R/3 technology for distribution of data between independent R/3 nstallations. ALE is an application which is built on top of the IDoc engine. It simply adds some structured way to give R/3 a methodical means to find sender, receiver, and triggering events for distribution data.

Make Use of ALE for Your Developments :

Transfer master data for material, customer, supplier and more to a different client or system with BALE Copy your settings for the R/3 classification and variant configurator to another system, also in BALE Copy pricing conditions with ALE from the conditions overview screen (e.g. VV12 ).

Distribution Scenario Based on IDocs:

ALE has become very famous in business circles. While it sounds mysterious and like a genial solution, it is simply a means to automate data exchange between SAP systems. It is mainly meant to distribute data from one SAP system to the next. ALE is a mere enhancement of SAPEDI and SAP-RFC technology.

ALE is an SAP designed concept to automatically distribute and replicate data between webbed and mutually trusting systems .

EXPLANATION :

Imagine your company has several sister companies in different countries. Each
company uses its own local SAP installation. When one company creates master
data, e.g., material or customer master, it is very likely that these data should be
known to all associates. ALE allows you to immediately trigger an IDoc sent to all
associates as soon as the master record is created in one system.

Another common scenario is that a company uses different installations for company
accounting and production and sales. In that case, ALE allows you to copy the
invoices created in SD immediately to the accounting installation.

ALE defines a set of database entries which are called the ALE scenario. These tables contain the information as to which IDocs shall be automatically replicated to one or more connected R/3-compatible data systems.


To conclude ALE is not a new technology. It is only a handful of customiing settings
and background routines that allow timed and triggered distribution of data to and
from SAP or RFC-compliant systems. ALE is thus a mere enhancement of SAP-EDI and SAP-RFC technology.

Example :

Let as assume that we want to distribute three types of master data objects: the
material master, the creditor master, and the debtor master.

Let us assume that we have four offices. This graphic scenario shows the type of
data exchanged between the offices. Any of these offices operates an its own stand
alone R/3 system. Data is exchanged as IDocs which are sent from the sending
office and received from the receiving office.

(110)

RELATED LINKS

ALE PART 6
ALE PART 5
ALE PART 4
ALE PART 3
ALE PART 2
ALE PART 1
CROSS APPLICATIONS IN ABAP
ALE IN BRIEF