Application Link Enabling (ALE)

It is SAPs Technology to support distributed yet integrated processes across several SAP Systems.
1

Distributed Process
A Distributed process is one in which part of a business process is carried out on one system and part on another. Two systems would exchange data with each other at appropriate points to stay synchronized.

Reasons
     

Geographic Location System Capacity Critical Operations Upgrade Security Political

ALE Advantages
  

Non-SAP Reliability Upgradeable

ALE Architecture
Outbound Process
   

Need for IDoc Generate Master IDoc Generate Communication IDoc Deliver Communication IDoc

Outbound Process components:

Customer Model Idoc Structure Selection Program Port Definition RFC Destination Partner Profile

Customer Model
A customer model is used to model a distribution scenario. In a customer model:You identify the systems involved in a distribution scenario Message exchanged between the systems

IDoc Structure
A message is defined for data that is exchanged between two systems. The message type is based on Idoc structure. e.g. If you are sending material master information to another system, message type is MATMAS is already defined in the system.

Selection Program
Selection programs, typically implemented as function modules, are designed to extract application data and create a master Idoc. A Selection program exists for each message type.

Port Definition
A Port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE uses tFRC port, which transfers data in memory buffers.

10

RFC Destination
RFC: Remote Function Call It is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed. In ALE, RFC specifies information required to log on to the remote SAP system to which an Idoc is being sent.
11

Partner Profile
A Partner profile specifies the Components used in outbound process: Logical name of remote SAP System, Idoc type, message type and tRFC port. Idoc Packet size Person to be notified in case of errors. A Partner Profile is created for each SAP System with which you communicate, and a record exists for each message sent and received from a system e.g. Material master (MATMAS), Customer master (DEBMAS), etc.
12

Sending out the data from our system. The IDOC which is called as Outbound IDOC

Application data

Start a OutBound Program

Step1

Outbound ALE program

Idoc data

Application Repository

Step2

Master Idoc

ALE Distribution Model

ALE Service Layer

Receiver3 Communcation layer Receiver4

Step3 Step4
13

Receiver1 Receiver2

Technical Flow of Outbound Process for master Data

Begin

Objects to be distributed are selected

No
Collect Idocs

Data is read from the database and formatted into IDOC format

YES Execute RSEOUT00 Program Idoc Packets are stored in the ARFCDATA table Execute RSARFCEX,which calls INBOUND_IDOC_PROCESS on the Remote System

ALE service layer is invoked via MASTER_IDOC_DISTRIBUTE ALE Distribution model is consulted to determine recipients Filtering conversion & Version change are carried out for each recipient Communcation Idocs are saved in the database

No
Successful YES Done

14

Outbound Process
Processing In Application Layer Process In ALE Layer


Receiver Determination
 IDoc Filtering  Segment Filtering  Field Conversion  Version Change for Segment  Version Change for IDoc

15

  

Generation of Communication IDoc Syntax Check Dispatch to Communication Layer Call INBOUND_IDOC_PROCESS

Process in Communication Layer



16

Inbound Process
  

Store IDoc Invoke Posting Module Create Document

17

Application Repos itory Direct Input function module Posting Program

RBDAPP01

ALE Service Layer

Application Idocs

Conversion

Filtering

Version Change

IDOC_INBOUND_ASYNCHRONOUS

Communication Layer

Communcation IDOC from remote system

18

Process In ALE Layer

     

Integrity Check Segment Filtering Field Conversion Create Application IDoc IDoc marked for Dispatch IDoc Passed to Posting Program

Process in Posting Module

19

Exception Handling

20

Configuration
IDoc Administration (WE46) ALE Customizing (SALE )
   

Create Logical System (LS) Assign LS to Client Create RFC Assign Port

21

Distribution of Master Data

Techniques
  

Push Change Pointers Pull

22

Basic Configuration


Maintenance of Distribution Model (BD64)  Create Customer Model  Create Message Type  Generate Partner Profile  Distribute Distribution Model

23

Change Pointers
Global Change pointers  BD50-Change Pointers for Segments  BD52-Specify Fields  Check CDHDR,CDPOS,BDCP  Run RBDMIDOC
 BD61-Enable

Fetch
 Maintenance

of Distribution Model (BD64) on Receiver side

24

SAP

NON SAP

Direct Approach Converters

25

Filtering
  

IDoc Level -BD64 Segment Level BD56 Field Level (Reduced IDoc) -BD53

26

Testing
Outbound
  

Partner Profile -RSECHK07 RFC SM59 Distribution Model -BDM5 Partner Profile -RSECHK07 WE19

Inbound
 

27

Performance
Control Points
  

Control Process Timing Control Packet Size Control Multiple Processing Real Time Batch Mode (Use of Control Points)

Modes
 

28

Strategies for Performance

   

Archiving Reorganize Change Pointers ABAP Program Database Performance

29

Thank You
30