ALE Transfer

[Former Member]

Hi Friends,

How to transfer the data through ALE to the same client.

i mean to say that, say i am in client 400. i want to transfer the data through ALE to client 400 only. Is it possible ?

I came to know that there is a concept like Virtual Client ?

Can anyone kindly help me ?

[Former Member]

Hi Manjunath,

Please check this link

Setting up the ALE Distribution Scenario

http://www.sappro.com/downloads/OneClientDistribution.pdf

In the First step give the Receiver system name as ur system in the distribution scenario.

Best regards,

raam

[Former Member]

Hi Manjunath,

Please check this link

Setting up the ALE Distribution Scenario

http://www.sappro.com/downloads/OneClientDistribution.pdf

In the First step give the Receiver system name as ur system in the distribution scenario.

Best regards,

raam

[Former Member]

Hi manjunath,

Application Linking and Enabling (ALE)

In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients

For our purpose we have two clients

namely Client 100 and Client 200.

System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).

Distribution of Material Master Data Between two Systems

1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)

To do this follow the following steps

Execute SALE Transaction Code

On The Screen Click on Sending and Receiving Systems.

Then Click on Logical Systems.

Then Click Defining Logical Systems.

Click New Entries Button

(E.g. (LG100 sending system)

(LG200 receiving system))

Enter two logical system names and their description.

Save

Comeback to SALE Transaction Code screen.

2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)

LG100 assign to client 100

LG200 assign to client 200

To do this, do the following.

Click Assigning Client to Logical System.

Ignore the message that comes up on the screen.

Select client 100

Click details button on the toolbar icon or press F2.

In the logical system box, enter LG100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter LG200.

Save

Back.

Comeback to SALE Transaction Code screen.

3) Maintain RFC Destination: (TR.CODE:SM59)

(Note: Do Not Create This Step)

Click Create Button on the Screen

On the Screen Maintain RFC Destination i.e LG200.

Enter LG200 in RFC destination box.

Connection type is 3

Give a description for the RFC destination.

Maintain Technical Settings on Details on Technical Settings tab

Target Host as : SAPKDC (NOTE: Save it as a Host Name)

Maintain Logon Details on Logon/Security tab.

Language: EN.

User: MMUSER200 (This is the logon for dist.)

Client : 200

Password: MM1234.

Save.

Click on create to do the above process for Client 200 in

The client 200 system.

4) Maintain Distribution Model.(BD64). (ABAPer role starts here)

Execute Maintain distribution model directly for

creating the model.

Click on change mode button on App tool bar of the Screen.

Create Model View pushbutton on App tool bar of the Screen.

A pop screen will appear in which you specify

Short text as Distribution for MM Data.

Enter Technical Name as LGMODEL.

Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG100.

Receiver as LG200.

Again Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG200.

Receiver as LG100.

SAVE.

On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Logical System as LG200.

Then execute the screen.

Click back.

Again On the same screen goto Menubar and select EDIT.

Again select Model View and then select Distribute.

****LOGIN to client 200.

Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Model View as LGMODEL

And Specify the Logical System as LG100.

Then execute the screen.

Click back.

*******Switch back to client 100 Session.

5) Create Material using MM01 Tr.Code.

Enter the material name as LGMATERIAL

Industry sector as Mechanical Engineering

Material Type as Finished Products.

And then Click on Data Pushbutton on the App tool bar.

Select views.

In the select views box for materials check basic data 1 AND 2.

Click enter icon.

In the next screen that you get

Give the text of the material as NEW MATERIAL.

Base unit of measure as KG.

Gross Weight as 200.

Net Weight as 100.

Weight Unit as KG.

In the description area language (E) and material description.

Click Save.

Now I Created a Material in Client 100 , I want to transfer this data to Client 200.

6) Execute BD10 to transfer the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client100).

Then a Screen will be displayed in which it shows that

1 Master Idoc Generated .. Enter

1 Communication Idoc Generated..Enter.

*******LOGIN to Client 200.

7) Execute BD11 to get the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client200).

😎 Execute Tr.code MM01 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

If not follow these steps.

9) Execute Tr.code WE19( for rectification of errors in client200).

Specify the Existing Idoc Number and Executes it .

A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.

10) Execute Tr.code MM01 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

Now the Material is correctly displayed in Client 200.

11) Monitoring of IDOCS.

Transaction Codes:

IDOC Display of Status: WE 05.

IDOC Date and Time: WE07.

further help:

check url

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/ale/configuration.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapdevelopment.co.uk/training

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FIAA/FI-AA-ALE.pdf

And also u can get lots of inof from the below link.

http://www.sapgenie.com/ale/why_ale.htm

Hope this is helpful to you.

thanks

karthik

[Former Member]

Hi,

We will assume, that we want to send material master data from the current system to a remote system. To simulate this scenario we do not need to have a second system. With a little trick, we can set up the system to send an IDoc back to the sending client.

We will set up the system to use an RFC call to itself. Therefore we need to define an RFC remote destination, which points back to our own client. There is a virtual RFC destination called NONE which always refers to the calling client.

RFC destinations are installed with the transaction SM59.

Create a new R/3 destination of type "L" (Logical destination) with the name INTERNAL and the destination NONE.

Note: Do not use RFC type internal. Although you could create them manually, they are reserved for being automatically generated. However, there is the internal connection "NONE" or "BACK" which would do the same job as the destination we

are creating now.

The next step is defining a data port, which is referenced by the IDoc sending mechanism to send the IDoc through.

Declaring the port is done by transaction WE21.

We will now declare an ALE connection from our client to the partner INTERNAL.ALE uses IDocs to send data to a remote system. There is a convenient transaction to send material master data as IDocs via the ALE.

The set up is done in transaction SALE. You first create a new ALE model, to avoid interfering with eventual existing definitions. Then you simply add the IDoc message MATMAS as a valid path from your client to INTERNAL. In order to send the IDoc, you call the transaction BALE and choose the distribution of material master data (BD10). Choose a material, enter INTERNAL as receiver and go.

To see, which IDocs have been sent, you can use the transaction WE05. If you did everything as described above, you will find the IDocs with an error status of 29,

meaning that there is no valid partner profile. This is true, because we have not defined one yet.

Thanks.

[Former Member]

Manjunath can tell wheather the data which u want to send is between 2 different servers..

ie : server1 400 client to server2 400 client is this the requirement or

within the same server.

[Former Member]

Hi Manju,

Why do you want to transfer the data within the same client of the same server.

All the data is there, if you wanted to send data from one server to another server, then you should create logical systems and assign them to each other.

Thanks,

Mahesh.