topic Re: problem in ALE configuration in Application Development and Automation Discussions

problem in ALE configuration

Former Member — Thu, 26 Apr 2007 14:52:37 GMT

Hi ,

I am doing ALE configuration to transfer the Vendor information from 800 client to 700

client.

In client 800 while I am creating partner function I am getting

error...Could you please help me to resolve.

In "Generate Partner Profile" (in 800 client)

I have given ....

Model View : "VENDMODEL1"

Partner System : IDES_700

Next screen "log for partner profile generation is displayed"

Partner

No error is displayed here...

But in "port"

the following message is displayed....

System IDES_700 : Port could not be created

RFC destination IDES_700 not specified for system

ides_700

Enter the RFC destination and restart the generation

After creating Model view with Sender and Receiver with Message type as CREMAS

what we have to do...

whether we have to distribute it ..

I am getting error log as ...

Targert system IDES_700 : RFC Destination for Synchronous

communication(message type SYNCH)

Partner Profile LS IDES_700 SYNCH does not exist

please help me in this regard

With Regards,

Sagar.

Re: problem in ALE configuration

Former Member — Thu, 26 Apr 2007 14:54:47 GMT

hi,

RFC destination should be created in both the system. The sender and the reciever should have the RFC system so that they can communicate with each other.

Have you created the RFC system in both the systems?

Cheers

Re: problem in ALE configuration

Former Member — Thu, 26 Apr 2007 14:58:10 GMT

Create RFC Destination using SM59 transaction and specify in your port defination in client 800.

Regards,

Amey

Re: problem in ALE configuration

Former Member — Thu, 26 Apr 2007 14:58:47 GMT

Hi,

RFC destination is not recognizing. check the following link:

http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html

Regards,

Bhaskar

Re: problem in ALE configuration

Former Member — Thu, 26 Apr 2007 14:59:39 GMT

Hi,

Please ensure the RFC destination for both logical system (client 800 and 700) are created in SM59.

Also you can add manually message type SYNCH with IDoc type SYNCHRON in the partner profile (WE20) prior to generate partner profile for message type CREMAS via BD64.

Message type SYNCH is a dummy message type for determination of RFC destinations and IDoc type SYNCHRON is a dummy IDoc type for synchronous communication.

You can setup something like this.

Outbound parameter options:


Field          Value
Message type   SYNCH 
Receiver port  A000000015 (Transactional RFC)
PacketSize     100
Output mode    Transfer IDoc immed.
Basic type     SYNCHRON

Hope this will help.

Regards,

Ferry Lianto

Re: problem in ALE configuration

Former Member — Thu, 26 Apr 2007 16:49:13 GMT

Hello,

Ferry Lianto has provided you with a good solution. The only thing that I would add is that when creating RFC destinations to implement ALE scenarios it helps to name your RFC destinations exactly the same as your logical sytems.

SAP hints at that in the error message you received:

"System IDES_700 : Port could not be created

RFC destination IDES_700 not specified for system

ides_700"

It seems to be looking for RFC dest IDES_700 for system IDES_700.

Regards

Greg Kern