7 Steps For ALE Configuration

7 Steps For ALE ConfigurationALE configuration normally involves the seven basic steps which are :1. Creating users for ALE Transfer

2. Creating Logicalsystem and assign the client

3.Creating the RFC

4. Configuring Distribution Model

5. Configuring and checking the port

6. Configuring and checking the partner profile

7. Creating the message typeThe steps to configure and use it is mentioned below :Notes: 105 is Sender and 800 Receiver System For Example1.Create Users for ALE transfer in both receiving and sending client/systems.Create users in both the client/systems giving the same user name and proper authorizations. We need to use these user ids to logon through the remote connection and perform the IDOC transfers.

2. Creating Logical Systemso Create logical systems for both sending and receiving systems in both systems.o Login to Client 105 (SENDER)o Go to T. CodeSALEo Expand Sending and Receiving Systemso Expand Logical Systemso Click on Define Logical Systemo Click on New Entrieso Create Logical Systems with naming convention 'system name'+'CLNT'+client no . For example for sending system ex: SSPCLNT105o Create Logical Systems with naming convention 'system name'+'CLNT'+client no ex: example for receiving system ex SEDCLNT800o Save and come backo Click on Assign client 105 to Logical system SSPCLNT105o Now, logon to client 800, repeat the same above process to create logical systems SEDCLNT800 and SSPCLNT105o Save and come backo Click on Assign client 800 to Logical system SEDCLNT8003. Creating the RFCso In client 105, Go to T. Code SM59o Expand R/3 Connectionso Enter RFC Name as SSPCLNT105 (give this name same as that of logical name created in step1 so that the ports are automatically created)o Connection Type as 3o Language as ENo Give the logon details for client 800 (usually, we create a new user with proper authorizations for this ALE data transfer)o Click on Remote logon button to test the RFCo Now, go to client 800 and repeat the same process to create the RFC connection to client 105, giving logon credentials to client 1054. Creating Customer Distribution Model

(we usually create this in the original system(sending system) and then distribute it to other systems. The actual creation of the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender system, a receiver system and message types to exchange between those systems.)

o In Client 105, Go to T. CodeBD64o Click on change and Create model view buttono Enter the short text and Technical name as ZSSP_SEDo Select the model and click onAdd Message TypeButton,o Give the Sender as SSPCLNT105, Receiver as SEDCLNT800,o Give Message type as required, Ex: 'HRMD_A' for HR Module.(usually Message types given by SAP are available for a particular module, see this using tcode WE81, if not create a message type first)oNote:If we are performing this data transfer task for all modules at a Customer site, then we will need to use the appropriate message type and create a new Distribution model.o Select the above model view & click on Environment -> Generate Partner Profileso Select Transfer IDOC Immediately and Trigger Immediately radio buttonso Click on Executeo You should get a list in green color which means it executed successfully.o Back to main screen, select the model viewo Click Edit->Model view->Distributeo Click on continueo You should get a list saying model view is distributed successfully.5. Checking the Porto In client 105, Go to T. CodeWE21o Expand Transactional RFCo Find the port from the list which is created using BD64 for SEDCLNT800 (Receiving system) RFC Destination.

6. Checking the Partner Profiles.o In client 105, Go to T. CodeWE20o Expand Partner Type LSo Select the Partner profile SEDCLNT800o Double click on Message Type (For Ex: In HR Module, HRMD_A in Outbound parameters.)o Check Receiver Port is assigned correctlyo Check the Basic type as your Basic IDOC object.o In the sending system, select the option to transfer IDOCs immediately.o By default, in the receiving system IDOCS are bunched together and received.7. Creating the Message Typeo Message type defines the 'meaning' of data. It is just a logical entity that gets connected to the Idoc type (in tcode we82) or gets connected to the distribution model (in tcode BD64)o If necessary create a new message type. In client 105, go to tcode we81.o Click on change, continueo Click on New Entries button

o Give message type in customer namespace Z* and description

oSave and back