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