Inbound RFC adapter question

[Former Member]

Hi,

I'm trying to configure this scenario properly

CRM 4.0 <--

---

> XI 2.0 <--

---

> Legacy system

using:

Synchronous <-----> RFC / SOAP <----> Legacy

RFC call Adapter / Connector system

I want to configure the RFC destination on the CRM side using SM59. I've created an RFC destination of type T TCP/IP for the RFC adapter. My question is: what is the program ID?

In the documentation, I found I should put in there the Program ID from my RFC adapter configuration file. Would that be the Rfc2XmbService? I've tried that but when I test my connection, I get an error message saying that the connection could not be established.

I'd really like to know how I can configure a destination on the sender side that points to the right RFC adapter...

Thanks a lot for your help!

Best regards,

Nathalie.

[Former Member]

Hi,

I am new to XI and we want to realize the following scenario in a demo prototype containing

CRM 4.0<>XI 2.0<>Legacy.

Here is the 2 step process to be realized:

1. Receive XML message (SOAP) containing order data in XI

2. Pass the orders data into SAP CRM from XI

We have identified the RFC [CRMXIF_ORDER_SAVE] for order creation on CRM side.

Currently we want to realize a one way communication from

legacy (XML) ---> XI (XML/RFC) ---> CRM 4.0

for sales order creation in CRM.

Could you list the basic steps involved in achieving this scenario like necessary adapters/configuration steps in XI. Do we have to do any custom development to realize this simple scenario. Greatly appreciate your help with this.

Thanks & Regards,

Chandhan.

[Former Member]

Hi Nathalie,

I hv similar issue. can u tell me what is the gateway host and service did u use. in my situation, i'm trying to post a flat file from legacy system via XI into R/3. I hv file adapter configured and working fine. But the message doesn't reach the target system. THe adapter is not able to register the rfc program in the system. Any thoughts.

you can also email me to kpandari@hotmail.com

thanks

pandari

[Former Member]

OK problem solved...

After a restart of the adapter engine, the complete scenario worked fine.