ALE IDOC

Former Member — Tue, 15 Apr 2008 09:30:57 GMT

Hi all,

i want to send material through idocs from client 205 to 206. but problem is that i m not getting that which message type shud give in outbond procees and which in inbond proces??

can anybody help me or can send step by step procedure ?

its urgent.

regards saurabh.

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 09:36:09 GMT

use MATMAS

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 09:42:20 GMT

Message type for the same is : MATMAS

Basic Type is : MATMAS04

create entry as outbound for this message type in 205.

create entry as inbound for thes message type in 206.

reward points, if helpful,

sandeep kaushik

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 09:53:50 GMT

hi...

i assigned message type matmas but now when i m going to distribute model view then its giving error message that is ' RFC destination for synchronous communication (message type SYNCH) Partner profile LS RECVR206 SYNCH does not exist)'

so plz. help me how wud i remove this problem.

regards saurabh.

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 09:55:49 GMT

ADD message type SYNCH and idoc type SYNCHRON

it is compulsory

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 10:16:23 GMT

hi dear,

thanx for reply but tell me where we add this message type synch and synchron, is it added in outbond of seding server or in inbound of recieving server? wud we have to assing both message matmas and synch in outbond of sending system??

plz. do reply its urgent.

regards saurabh.

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 10:20:58 GMT

you need to add it in outbound

reward if useful

Re: ALE IDOC

Former Member — Tue, 15 Apr 2008 10:29:35 GMT

Hi,

1.We will provide the inbound and outbound same message Type i.e MATMAS.

step by step procedure:

u can check these :

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2a1dd5d3-0801-0010-ed8d-bd797ed922cb

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/200dd1cc-589e-2910-98a9-bb2c48b78dfa

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 satyam03

1. SETUP LOGICAL SYSTEM: To do this follow the following steps

Tools -> Business Engg ->Customizing.

Click Enterprise IMG button.

Cross Applications -> Distribution (ALE) -> Basic Configuration.

Set up ‘Logical System -> Maintain Logical System.

Click New Entries Button (E.g. WalMart100 receivin system)

(Walmart200 sending system)

Enter two logical system names and their description.

Save

Comeback to IMG setting screen.

2. Now you have to allocate the created logical systems to respective clients.

WalMart100 assign to client 100

WalMart200 assign to client 200

To do this, do the following.

Click Allocate logical system to the client.

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 WalMart100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter WalMart200.

Save

Back.

Come back to the IMG settings screen.

Now define the RFC Destination. Do the following.

Click Cross Application -> Distribution (ALE).

Click on communication.

Execute RFC Destination.

Click R/3 connections. (Expand it).

Put cursor on R/3 connection.

Click the create button.

Enter WalMart100 in RFC destination box.

Connection type 3

Give a description for the RFC destination.

Language E.

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

Client : 100

Password: Enter the client logon password.

Save.

In target machine box enter cysap03 (This is the system

name)

Save.

Click on test connection and remote logon to verify.

Click on Back button.

Position your cursor on R/3 connection.

Click on create to do the above process for WalMart200

logical system for client 200.

Click on the back button.

Click on the distribution customer model.

Execute Maintain customer distribution model directly for

creating the customer model.

Put your cursor in Maintain customer distribution model directly box.

Click Choose.

Specify the source logical system (WalMart200) and give a

customer model name. (ModelMar10)

Click on create icon.

Select the target logical system (WalMart100) from the list.

Click on create message type.

In the resulting screen, in log message type enter MATMAS.

Click on transfer.

Save.

Back to IMG setting screen.

Click distribute customer model.

Select generate partner profiles and click choose.

In customer model box enter the model name that you

created (Modelmar10)

Click execute button.

You should get a screen mentioning successful creation of

customer model in green color.

Click back button

Select distribute customer model and click choose.

In the resulting screen enter customer model (Modelmar10)

Receiving logical system (WalMart200)

Click execute.

You get messages :

copy with RFC destination WalMart100

model data sent successfully.

Click back.

Now execute R/3 and login to client 100

Execute transaction SPRO.

Click Cross applications -> Distribution ALE

Communications -> generate partner profiles.

Enter the customer Model (Modelmar10)

Execute

Base unit of measure as PC

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

Click Save.

Come back to the first screen of the session

Logistics -> Central Functions -> distribution

Master Data -> Material -> Send.

Enter the material name. (Mat1000)

Message type (Matmas)

Logical System (WalMart100- target logical system)

Click Execute.

Switch to Client 100 session to verify.

Logistics -> Material Management -> Material Master.

Material -> Display -> Display Current.

Give the name of the material (Mat1000)

Click select views button.

You should get select views screen for the given

material.

Regards,

Kumar(Reward if helpful).

topic ALE IDOC in Application Development and Automation Discussions

ALE IDOC

Re: ALE IDOC

Re: ALE IDOC

Re: ALE IDOC

Re: ALE IDOC

Re: ALE IDOC

Re: ALE IDOC

Re: ALE IDOC