topic Re: Ale / Idoc between two different servers in Application Development and Automation Discussions

Ale / Idoc between two different servers

abdulgaffarmohd — Mon, 08 Feb 2010 09:39:51 GMT

Hi All,

In my scenario i am working on two different servers in which distribution of idoc is carrying out.

(Before this i have worked on same server scenarios with different clients.)

But present scenario i am working with two diferent servers,

like,

i am having 100 client in server A (sender system) and 700 client in server B(receiver system),

i have created all the basic steps like logical systems in both systems,

Assign logical systems to clients in consecutive servers,

RFC's and ports.

while creating message type under model view in server A client 100(sender system ) i can find only 100 client's logical system name, i cannot find the 700 clients logical system name.

due to both clients are in different ip address , does we need to transfer the logical system assign ment transport request to other client.

regards,

Mohd.

Re: Ale / Idoc between two different servers

Former Member — Sun, 14 Feb 2010 13:19:50 GMT

Hello abdul ,

When you configure a logical system for example the same system with a different client (700) it should be configured in the source system (Client 100).

In this way when you can send the relevant IDOCs via the ALE according the model view (BD64) ,the source system (100) knows that the target is the system with the client 700 .

(There is a generic RFC in the background process : INBOUND_IDOC_PROCESS).

Sender : system_100

Receiver:system_700

Message type : MATMAS

Also in order to accept the relevant Idocs in the system with client 700,you must configure a partner profile that will contain in inbound parameters the relevant message type (MATMAS).

I hope it is more understood .

Thank you,

Boaz

Re: Ale / Idoc between two different servers

Former Member — Sun, 14 Feb 2010 15:34:40 GMT

Hi Abdul,

Find the steps below.

1.Go to SALE transaction

2.Define Logical system (Use only the existing Logical systems).

3.Assign client to the logical system. (Never change the existing assignments).

4.Define target systems for RFC calls. (We can do this using SM59 also).(Always maintain same names and descriptions for RFC destinations like Logical system.)

Example:

Logical system in 100: LS_100

RFC destination in client 200 should also be LS_100

Logical system in 200: LS_200

RFC destination in CLIENT 100 should also be LS_200

For a better practice always maintain both RFC destinations in both sending and receiving systems.

Hope this helps.

Regards,

SuryaD.

Re: Ale / Idoc between two different servers

GauthamV — Mon, 15 Feb 2010 04:15:23 GMT

You have to create two logical systems in both servers.Then only you

can assign them in model view in BD64 transaction.

Re: Ale / Idoc between two different servers

abdulgaffarmohd — Mon, 15 Feb 2010 09:33:50 GMT

Hi Gautham,

i understood the basic concept i already created two logical systems in two servers,

but while assigning in model view i am getting error please can you please explain me some major steps in at least in one server

Regards,

Mohd.

Re: Ale / Idoc between two different servers

SuhaSaha — Mon, 15 Feb 2010 09:34:58 GMT

What is the error you are getting in BD64 ?

Suhas

Re: Ale / Idoc between two different servers

abdulgaffarmohd — Mon, 15 Feb 2010 10:04:21 GMT

while distributing in 100 client i am getting error like

Target system IDES800 Model view ALEIDOC has not been updated

Rreason: Distribution model is currently being processed

regards,

mohd.

Re: Ale / Idoc between two different servers

SuhaSaha — Mon, 15 Feb 2010 10:18:29 GMT

This message was moderated.