Are these steps correct for ALE configuaration ?

Question

1.An ALE Configuration we have to do five steps
a)Define logical System (SALEsending and receiving system logical systemdefine logical system)
b)Assign client to the logical system( SALEsending and receiving systemlogical system Assign client to the logical system)
c)We have to define port at (WE21)
d)GENERATING PARTNER PROFILES(WE20)
e)Define target system for RFC calls (sm59)
f)Creating Distribution model (BD64)
g)WE42 for creating process code.
h)Send Data ( bd10)
i)Get Data(bd11)
j)BD51
k)WE57
We have to repeat the FIRST 6 steps for each of the sender and receiver and those are compulsory. I am not yet clear about the last 5 steps.
E.g. our sender is 200 and receiver is 400
So for each of them we have to do the 5 steps twice.

Answer 1

folow the link
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
which will givw u the steps for ale configuration
steps are
. ALE->Sending and Receiving Systems->Logical Systems->Define Logical System. a. Here you add the name of the logical system for the distributed system. To make them easy to find I like to name them based on instance/client so in the case of the system listed above I would call it DM7200. This naming convention makes it easy to follow in various systems.
2. ALE->Sending and Receiving Systems->Logical Systems->Assign Client to Logical System.
a. In this step you assign your logical system to a particular client. WARNING: DO NOT CHANGE THIS IF IT IS ALREADY CONFIGURED!!! That holds especially true on an FI system as it cannot be changed once it is set. Make sure to discuss this with the Basis team before entering the data.
3. ALE->Sending and Receiving Systems->Systems in Network->Synchronous Processing->Determine Target System for RFC Calls
a. This area allows you to tell SAP where to make RFC calls based on the logical system. That means that when I want to look up Vendor information in cases like infotype 194 and 195 where a function module is called that I can tell the system where to go to find that information. To configure this you should make sure that the system where the financial information will be kept is listed.
4. ALE->Modelling and Implementing Business Processes->Maintain Distribution Model and Distribute Views
a. In this step we will define where the FI data comes from and what data we expect to receive. We will also define the system that will be receiving the payroll posting and what data we will be sending that system.
b. SAP Recommends the following list of messages to be received from the financial system:
i. COACTV-IDoc for cost center/activity type
ii. COAMAS-Master activity type
iii. COELEM-Cost Element Master Data
iv. COGRP1-Cost Center Groups
v. COGRP2-Cost Element Groups
vi. COGRP5-Activity Type Groups
vii. COSMAS-Master Cost Centers
viii. CRECOR-Core Vendor master data distribution
ix. CREMAS-Vendor master data distribution
x. GLCORE-Master data G/L accounts (CORE IDoc)
xi. GLMAST-Master data G/L accounts (master IDoc)
xii. PRCMAS-Profit center master record
xiii. RCLROL-Reconciliation ledger rollup
c. To add these messages you can follow the steps listed here:
i. Go into change mode by clicking on the pencil/glasses button or Distribution model->Switch Processing Modes via the menu
ii. Click on the Create Model View Button
Fill in the data for your model. Below is my example.
iii. Now it is as simple as adding message types. Click on the Add message type button and enter the required data. The sender is the FI system and the receiver is the Payroll system. Tip: Once you add the first message type if you select it before adding the next message you will only need to fill out the message portion and not the sender and receiver
iv. Now we need to build the partner profiles so that the systems know where the distribution model needs to get or put things. To do this go to Environment->Generate Partner Profiles.
Enter the partner system you want to use and press execute or F8.
This screen shows the successful creation of the partner profiles. If you want to see them can go to transaction WE20.
v. Now we must send the model to the other system. To do this use menu path Edit->Model View->Distribute
Now I should be able to see this model in my FI system, in this case, DM3. I can take a look at this via transaction BD64 in the other system
You'll notice that the coloring on the messages and models is in gray. This indicates that the model is maintained in another system.
d. We also have to configure the model for posting to the other system. In this case we will be using BAPI's and not message types. SAP recommends the following BAPI's:
i. AcctngServices.DocumentDisplay, Accounting: Display Method for Follow-On Document Display
ii. AcctngEmplyeeExpnses.Post, Accounting: Post G/L Acct Assignment for HR Posting
iii. AcctngEmplyeeRcvbles.Post, Accounting: Post Cust. Acct Assignment for HR Posting
iv. AcctngEmplyeePaybles.Post, Accounting: Post Vendor Acct Assignement for HR Posting
e. For the most part the steps are the same as above but it is slightly different because you use the Add BAPI button instead of the Add Message Type. BAPI's are case sensitive so you'll need to be exact.
<REMOVED BY MODERATOR>
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 2:27 PM