RFC to RFC secnario with Netconnector

[Former Member]

Hello,

I have a scenario with NETCONNECTOR calling R/3 with a RFC directly.

We want to switch this scenario to PI in the middle for some reasons.

But the NETCONNECTOR is not registering on the R/3 system, it is doing direct RFC call without program id.

Does this work with PI also?

How do I have to configure the RFC SENDER adapter? Program ID, values for RFC METADATA fields...????

best regards

Werner

P.S: I thought I remeber a thread with the same question, but I do not find it again.....

[arunneerolil]

If you are making an RFC call to R/3, it is not required to configure any program IDs. This applies to both PI and .NETconnector.

In PI you need to configure a receiver adapter with connection parameters to R/3.

But if the call is from R/3 to PI / .Net connector over RFC, program id needs to be configured. In R3 an RFC destination of type 'T' must be created with a unique program id. The same program id must be used in the PI RFC sender adapter.

arun