ALE setting

[Former Member]

What are ALE setting exactly?and how to go about it?

[Former Member · Accepted solution]

Application Link Enabling (ALE) is a mechanism for the exchange of business data between loosely-coupled R/3 applications built by customers of SAP, the enterprise resource management program. ALE provides SAP customers with a program distribution model and technology that enables them to interconnect programs across various platforms and systems.

The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP com

IDOC

http://msdn2.microsoft.com/en-us/library/ms942196.aspx

Idoc configuration Required~

in R/3

1) RFC destination pointing to XI

2) WE20 Partner Profile entries

in XI

1) RFC destination pointing to R/3

Go thru this -

Go thru these for Idoc to XI scenarios-

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm

These will be the Configurations needed in your R3,

1. SM 59 - Create an RFC destination for your XI .

2. We21 -- Create a port for XI

3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.

Configuration on XI

1. IDX2 - Import IDOC metadata.

For eg : Lets assume the R/3 system and Xi system are QZA and X7A.

In XI :

Step 1 : In SALE Tcode :

a)Create Logical systems for R/3 and XI.

EG : (QZACLNT100) and (X7ACLNT100).

b) Assign the logical system of XI to Client.(X7ACLNT100)

Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab

Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.

Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.

In R/3 :

Step 1:

In SALE Tcode :

a) Create Logical systems for R/3 and XI for

b) Assign the logical system of R/3 to Client.(QZACLNT100)

Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.

Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.

a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.

b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.

c)In Menu Bar EDIT->Generate Partner Profile.

Click on that and press Execute .

This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .

d) Click EDIT->MODEL VIEW->Distribute.

This shall distribute the model and you can see the distribution mode aslo getting created in XI system.

This configuration shall surely help u out as it worked out for me.

Configurations required for IDocs in R/3

In your XI system, you need to do the following.

1. Create a RFC destination to your R/3 system

2. Create a port in IDX1 of your XI system and use the RFC destination in step1.

3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.

4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.

5. Import the business system and you can use it in your configuration scenario.

Please also refer below links for details.

Go thru this-

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38...

Regards,

Shweta

[former_member189440]

CONTENTS

Distributed processing 2

Introduction 2

Reasons for Distributing Processes 2

Existing Technologies for Data Distribution 2

Disk Mirroring 2

Online Distribution Using Two-Phase-Commit Protocol 3

Distributed Updates to Replicas 3

What should be the ideal distributed environment. 3

SAP’s solution for Distributed environment 3

Benefits of ALE 4

Data exchanged between distributed SAP system 4

ALE Architecture 4

Outbound processing 4

Components used in Outbound ALE process 5

Triggering Outbound ALE process 6

Difference between EDI and ALE process 6

ALE configuration steps for outbound processing 6

Outbound business scenarios 7

Distributed processing

Introduction

Fig 1.0: Two distributed SAP system Exchanges relevant data.

Two sap systems exchange data with each other at appropriate points to stay synchronized. Distributing a process does not enhance any application functionality. Then, Why Distribute?

Reasons for Distributing Processes

· Geographical Location

· System Capacity

· Data Security

· Political and business reasons

Existing Technologies for Data Distribution

Various technologies or techniques offered by database vendors are based on the structure of data and not the business rules.

Disk Mirroring

Its like Disk Copy changes occurring in a database are simultaneously propagated to another disk that maintains a mirror image of the main disk’s contents. This technique has bad effect on OLTP transactions and it cannot encapsulate business rules for copying only specific data.

Online Distribution Using Two-Phase-Commit Protocol

The database design dictates where a table resides , and the database management system manages queries and updates to these tables. Two-phase-commit protocol guarantees that related tables across system are updated in one logical unit of work.

In this technique segregation based on the semantics of data is not possible. For example, you can not specify that a material master for your Asian subsidiary should be created on system B, whereas a material master for the U.S. unit should be created on system A.

Distributed Updates to Replicas

In this technique the system allows you to maintain redundant data across multiple systems. This technique require same version of database and operating system components on the systems involved in the process.

What should be the ideal distributed environment.

· System should understand the syntax and semantics of the data

· Distribution of the data should be based on business rules and not on database replication techniques

· Distributed system should be able to maintain its autonomy while being integrated with other distributed system

· Distributed system should able to handle different data models.

· Receiving system should handle its own problem and not tie up the sending system and vice versa.

· In spite of network failure , system should maintain continued operation. Changes made to either system should be synchronized after the network connection is restored.

SAP’s solution for Distributed environment

SAP introduced ALE to support integration of distributed systems.

ALE is not based on any database replication techniques. It is based on application-to-application integration using messaging architecture. A message defines data that is exchanged between two processes

In ALE, data is exchanged using IDOC containers.

Benefits of ALE

· Integration with Non-SAP systems

· Reliable distribution

· Release upgrade

· Autonomy

Data exchanged between distributed SAP system

Distributed SAP system exchange three types of data ………

a) Transactional data : sales orders, purchase orders, contracts, invoices, GL posting.

b) Master data : Material master, customer master, vendor master, employee master

c) Control data : Company codes, business areas, plants, sales organizations, divisions, distribution channels.

Transactional and master data are distributed using ALE interface. Control data is transferred using CTS (Correction and Transport System).

ALE Architecture

ALE architecture consists of ………..

· Outbound process

· Inbound process

· Exception handling

Outbound processing

Step 1 : Identify the need for sending an IDOC

a) Start outbound program (Application starts outbound program)

Step 2 : Generate Master Idoc. (Outbound ALE program does this task)

a) Read document or master data from database

b) Format it into IDOC format ie. Generate master IDOC in memory

Step 3 : Generate the communication IDOC. (ALE service layer does this task)

a) Generate & store the communication IDOC for each recipient

Components used in Outbound ALE process

· Customer model

· Idoc Structure

· Selection Program

· Filter objects

· Conversion rules

· Port definition

· RFC destination

· Partner profile

· Service programs

· Configuration tables

Customer model :

In customer model you identify the systems involved in a distribution scenario and the messages exchanged between the systems

Filter objects :

In distributed environment, each recipient of data may have different requirements for the data being distributed. Filter objects remove unwanted data for each recipient of data.

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 tRFC port, which transfers data in memory buffers.

RFC destination :

In Ale , the RFC specifies information required to log on to the remote SAP system to which an Idoc is being sent.

Partner Profile :

A partner profile specifies the various components used in an outbound process (logical name of the remote SAP system, Idoc type, message type, tRFC port, the packet size of an Idoc, person to be notified in case of errors.

A partner profile is created for each SAP system that you communicate with, and a record exists for each message sent and received from a system.

Partner Profile :

SAP provides sevice programs and configuration tables to link these programs and configuration tables and provides various customizing options for an outbound process.

Triggering Outbound ALE process

· MM/SD transactional data

Ø Message control technique

· FI/PP/HR transactional data

Ø Do not use message control techniques. Application program takes care of

generating IDOCs.

· Master data

Ø Stand alone programs for example BD10/BD11 for material master

Ø Change pointers

Difference between EDI and ALE process

The EDI process transmits Idocs to an EDI subsystem using flat file format. The ALE process transmits Idocs to an SAP system via memory asynchronous communication.

ALE configuration steps for outbound processing

· Setting on source system

· Basic Setting

· IDOC Administrator

· General IDOC interface

· Communication Setting

· Logical system

· Allocate client to the sending logical system

· RFC connection

· Port definition

· Basic configuration for distributing data

· Maintain distribution model

· Generate partner profile

· Distribute customer model

· Maintain workflow setting

· Setting on Target system

· Create partner profile on target system

· Execution

· Start outbound program through application

· View IDOCs

Outbound business scenarios

ü Normal ALE interface : Exchange data object such as material master

between two systems to its full extent using

stand-alone program.

ü Normal ALE interface : Exchange data object such as material master

between two systems to its full extent using

change pointers.

ü Reducing Idoc types : Exchange data object such as material master

between two systems for desired information.

ü Filtering : The filtering techniques creates a subset of data at

run time. Filtering can remove certain segments

from an IDOC or complete Idoc for distribution to

specific system

ü Conversion : The conversion techniques converts data in certain

fields of the IDOC from their local meaning to a

global meaning for distribution.

ü Version Change : Idocs and segments are version controlled. The

system can be configured to distribute a specific

version of an Idoc or a segments to a destination

system.

ALE Implementation Methodology

ü Analysis Phase

ü Preparation phase

ü Setup phase

ü Testing phase

ü Execution and Verification phase

Analysis Phase

ü Study the integrated process

It is very important to understand the business process. The online help provides detail description of the business process. IMG points to the customizing options available in the process. And the reference model can help with process flows and component descriptions.

ü Identify process boundaries in the distributed system

Process boundaries define the business functions that take place on each system.

For example, a contract is created on central system and purchase order against contract is created on another system.

ü Identify data flows

One of the system is owner of the data is responsible for creating, maintaining, and distributing it to the other system. For the data flows you should be able to identify the various transactional and master data exchanged between system.

ü Study the system limitations

For example, if a sales order is being entered in a single integrated system, the system calculates delivery dates and carries out credit checks instantaneously. If, however, the systems are distributed, a real time availability check performed in another system may not be supported.

ü Deciding on customer Enhancements

There may be gaps between the business needs and standard SAP functionality. If gaps can not be filled with one of the customizing options , you can use user exits. For example, if you may need to populate the data in extended Idoc through user exit.

Preparation Phase

ü Identify central and Decentral systems

Identify the SAP systems involved in the process. Assign logical name to each system.

ü Identify Lists of Idocs and Messages

A list of Idoc types and Messages should be identified for each type of data exchanged between the systems.

ü Identify workflow parameters

Identify user ID, position, workcenter etc for handling errors associated with the business process involved.

ü Identify list of control objects

For example, Customizing object for Company code is V_T001.

Setup Phase

ü Identify Lists of Idocs and Messages

These settings are specific to business scenario being implemented.

ü Message control setting to propose ALE output

ü Configure ALE components

ü Maintain basic ALE infrastructure

ü Maintain customer distribution model

ü Distribute the customer model

ü Generate the partner profile

ü Make workflow setting

Testing Phase

ü Test ALE setting

ü Test Control data setting

ü Test application setting

Execution and Verification Phase

ü Execute the application program to trigger the ALE process

ü On Sending system

ü Make sure that application document posted

ü Check the IDOC and make sure it was posted to port successfully

ü On Receiving system

ü Check the IDOC and make sure it was posted to port successfully

ü Make sure that application document posted

Support Phase

ü Monitor the system on an ongoing basis and identify and fix the problems.

[Former Member]

Hi SwatiKulkarni,

For more info ,

http://help.sap.com/saphelp_erp2005/helpdata/en/78/21768451ce11d189570000e829fbbd/content.htm

Thankyou,

[Former Member]

Enterprises are increasingly looking to deliver real business benefits by integrating their systems and processes both within their organizations and between organizations.

Hence SAP and non-SAP systems require frequent communication,tight integration and (usually) high levels of data exchange.

SAP has come up with the concept of ALE (Application Linking and Enabling).

ALE has three prime entities, which participate in the message exchange process:

SAP R/3 system

ALE converter (inclusive of its sub-components)

External non SAP R/3 system

To ensure that the inbound function module is called using ALE, a number of ALE settings (table entries) need to be made.

[Former Member]

It is very simple

Ask a BASIS Consultant !!!

It will be simple for him...

[Former Member]

Dear Swati,

To ensure that the inbound function module is called using ALE, a number of ALE settings (table entries) need to be made. To get to ALE outbound processing settings choose Tools IDoc Interface/ALE Development.

The graphic below gives an overview of the relationships between the settings. Each row represents a field; the row "Error events" represents five fields. Only the relevant fields of each table are listed. The columns represent the following (bold entries represent primary key fields):

· The fields that are read from an inbound IDoc’s control record

· The six IDoc fields that determine the process code to be used

· The attributes associated with the process code

· The attributes associated with the inbound function module

· The fields used to check that the function module is registered in ALE

Relationships Between the Fields in IDoc Control Record and the Tables Containing ALE Inbound Settings

Regards

Azahar

[Former Member]

Hi swati,

Chk out this link:

http://help.sap.com/saphelp_erp2005/helpdata/en/78/21768451ce11d189570000e829fbbd/content.htm

[Former Member]

Hi,

Just check out the links below:

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm

hope this will help you

Regards,

Sushama

[Former Member]

Hi Swati

check out these

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

Regards

Pratibha

[Former Member]

Hi

ale means application linking enabling...used to link idocs for different r/3 sys

For File to IDOC,

in R/3

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using we21

4.create partner profile using we20

in xi

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using IDX!

for IDOC to FIle

R/3 side

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using we21

4.create partner profile using we20

5.distribute busynessmodel using bd64

for xi side

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using IDX!

4.create partner profile using we20

ALE configuration for pushing idocs from SAP to XI

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

IDOC testing using WE19

/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi

File To IDOC - Part1 (SLD and Design):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

File To IDOC - Part2 (Configuration):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&

File To IDOC - Part3 (Steps required in XI and R3):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&

SAP R/3

R/3 to XI

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (We21)

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Create Partner Profile (WE20)

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

XI to R/3

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

[Former Member]

Hi,

Steps

SAP XI

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (IDX1)

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Load Meta Data for IDOC (IDX2)

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

SAP R/3

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (We21)

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Create Partner Profile (WE20)

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

In SLD – System Landscape Directory

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.

Ts for Third Party (Logical system):-

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

BS for Third Party (Logical system):-Enter the XI logical system name.

In Transaction SALE

Define and Assign the logical system name.

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Regards

Seshagiri