This document provides an overview of Application Link Enabling (ALE) in SAP systems. ALE allows for distributed yet integrated business processes across separate SAP systems. It uses message-based integration where IDocs are generated and exchanged between systems. The document outlines the ALE architecture, objectives, processes for outbound and inbound integration, configuration settings, and techniques for exchanging different types of data like transactions, master data, and control data between systems. It also previews a hands-on agenda for demonstrating ALE functionality.

1. Application Link Enabling (ALE)

2.  Distributed Applications
 Why Distributed Applications?
 Application Link Enabling(ALE)
 ALE Objectives
 ALE Architecture
 Outbound Process & Inbound Process
 Overview of IDocs
 Messages
 ALE Configuration Settings (Outbound & Inbound)
 Techniques used to exchange data between the systems
 Hands-On
Agenda

3.  Distribution Process
 A Distribution Process is one in which a part of business process is carried
out in one system and part on another.
 The two systems would exchange data with each other at appropriate
points to stay synchronized. In addition, business process are often
required to keep systems synchronized.
Distributed Applications
Central purchasing
Production Center
Sales Center
Distribution Center

4.  One Central System is not always optimal for unifying the business processes
with integrated applications.
 Reasons for Distributed Systems.
 Geographic Location
 Consolidation
 System Capacity
 Mission-Critical Applications
 Separate Upgrade of Modules
 Data Security
Why Distributing Applications?

5.  SAP introduced ALE as its initiative to support distributed yet integrated
environment.
 ALE allows for efficient and reliable communication between distributed
processes across physically separated SAP systems to achieve a distributed yet
integrated, logical SAP system.
 ALE enables integrated configurations, in which applications are loosely
coupled, i.e. asynchronously and not via a common database.
ALE (Application Link Enabling)
• Message-based Architecture
• Business Scenarios
• Communication Technology
• Tools
• Methodology
ALE Infrastructure encompasses:

6. ALE Objectives
• Scenarios:
 R/3 and R/3
 R/2 and R/3
 SAP and non-SAP systems
• Support for different
application releases
• Integration of distributed applications
– Consistency and synchronization
of distributed data with respect
to available database technology
– Support for the configuration of
distributed applications

7. Distributed Processes
ALE
• PP
• Inventory
management
• Internal sales,
shipping and billing
• Local purchasing
• PM
• Local SOP
• Financials
• Central controlling
• Central SOP
• Information Systems:
• Inventory
• Purchasing
• Sales
• Central purchasing
• Reference system for
Master Data and
Control Data
• Sales, shipping and
billing
• Purchasing of
trading goods
• Inventory management
• Local controlling

8. ALE enables Distribution of
Transaction
Data
Master Data
Control Data
(Customizing)
ALE distribution model

9.  Interfaces with R/3, R/2 and Legacy Systems
ALE Architecture
R/3
R/3
LEGACY
SYSTEM
R/2

10. Flow of Information
R/3 System 1
R/3 System 2
Workflow 'output'
Determine
recipients
Filter/
convert data
Create IDoc
Workflow 'input'
Application functions
Filter/
convert data
Application
data
Application
IDOC
Master-
IDoc
Comm.-
IDoc
Comm.-
IDoc
Comm.-
IDoc
Comm.-
IDoc
Carrier
Application ALE Communica-
tion

11.  At a very high level, Outbound Process involves 4 steps.
 Identify the need for sending an IDoc
 Generate the master IDoc
 Generate the communication IDoc
 Deliver the communication IDoc
 At a very high level, Inbound Process involves 3 steps.
 Store the IDoc in the database.
 Invoke the posting module
 Create the document.
Outbound Process & Inbound Process

12.  An IDoc(Intermediate Document) is a container that is used to exchange data
between any two process.
 The word IDoc represents IDoc type and/or IDoc data depending on the
context in which the word is used.
 An IDoc type represents the IDoc’s definition component, which defines
the structure and format of data being exchanged.
 IDoc data can be seen as the instance of the IDoc type.
 An IDoc type structure can consist of several segments, and each segment can
consist of several data fields.
 An IDoc contains 3 types of records.
 One Control Record
 One or many Data Records
 One or many Status Records
Overview of IDocs

13.  A message represents a specific type of document transmitted between two
partners.
 In SAP, an IDoc can be used to represent several messages or business
documents. (These message should be logically related)
 For example,
 The IDoc (ORDERS05) is used for several messages
 Orders (ORDERS)
 Order Response (ORDRSP)
 Order Change (ORDCHG)
Messages

14.  Outbound:
 Define Logical Systems (both the sending and receiving logical systems)
(SALE )
ALE -> Sending and Receiving Systems->Logical Systems->Define Logical Systems.
 Sender : Maintain Sender LS
 Receiver : Maintain Receiver LS
 Assign Client to Logical Systems. (SALE )
ALE -> Sending and Receiving Systems->Logical Systems->Assign Client to Logical
Systems.
 Client at SAP End : Assign Current working client
 Maintain RFC destination to connect to Receiving System (R/3). (SM59)
 RFC destination : Maintain Descriptive Destination
 Connection Type : 3 (R/3 Connection)
 Target Host : Target system IP Address
 System Number : SAP system Number
 Logon Details : Logon Details of the target system
ALE Configuration Settings

15.  Outbound:
 Maintain Port definitions (WE21).
 Port Type : TRFC
 Port : System generated (A00000??)
 Description : Maintain Meaningful Description
 RFC Destination : RFC Destination Maintained in previous step
 Maintain Partner Profiles (WE20).
 Partner Number : Maintain Receiving Partner
 Partner Type : Maintain Partner Type (LS)
 Message type : Maintain Message Type (Outbound parameters)
 Receiver port : A00000??
 Transfer IDOC Immediately : ‘X’
 Basic Type : Maintain Basic IDOC Type
 Packet Size : 1
 Syntax Check : ‘X’
ALE Configuration Settings

16.  Outbound:
 Maintain Customer Distribution Model (BD 64).
 Sender : Maintain Sender LS
 Receiver : Maintain Receiver LS
 Message Type : Maintain Message Type
 Port and Partner Profiles can be generated automatically by maintaining RFC
destination name same as that of target Logical System. (BD82)
 Inbound:
 Define Logical Systems (both the sending and receiving logical systems) (SALE )
ALE -> Sending and Receiving Systems->Logical Systems->Define Logical Systems.
 Sender : Maintain Sender LS
 Receiver : Maintain Receiver LS
 Assign Client to Logical Systems. (SALE )
ALE -> Sending and Receiving Systems->Logical Systems->Assign Client to Logical
Systems.
 Client at SAP End : Assign Current working client
ALE Configuration Settings

17.  Inbound:
 Maintain Partner Profiles (WE20).
 Partner Number : Maintain Receiving Partner
 Partner Type : Maintain Partner Type (LS)
 Message type : Maintain Message Type (Inbound
parameters)
 Process Code : Process Code that is linked to Inbound
FM
 Syntax Check : ‘X’
 Trigger Immediately : ‘X’
ALE Configuration Settings

18.  Push Method
 Sends Master data to the target system
 Pull Method
 Requests Master data from central system.
 Change Pointers
 Distributes the changes in master data to the target systems using SMD
(Shared Master Data Tool)
 Any changes to the master data item gets logged into certain tables (
Change Document Tables – CDHDR, CDPOS)
 When the change pointer (SMD tool) is active, then it reads the contents
of CD* tables and then the pointer to that change in record gets stored in
the DB tables (BDCP, BDCPS).
 SALE->ALE->Modeling->Master Data Distribution->Replication of Modified
data
 ->Activate Change Pointers generally
 ->Activate Change Pointers for message types
Techniques used to exchange data

19.  Send a Material from iGATE IDES system to iGATE 4.7 system
 TCODE : BD10 (PUSH Method)
 Get a Material from iGATE IDES system to iGATE 4.7 system
 TCODE: BD11 (PULL Method)
 Distribute the changes in Vendor master from iGATE IDES system to IGATE 4.7
system
 Execute the program “RBDMIDOC”. (Change Pointers)
Letz do it!!!