sending a message from R3 to XI RFC Sender Adapter

[Former Member]

Hi,

RFC Sender Adapter is properly configured on XI side.

Destination on R3 side is working ok.

What I don't understand - where do I define remote function on the XI side?

So, when I make a call from R3 side

call function 'func' destination 'blah'.

it goes to XI, invokes this 'func' and passes to it parameters/tables/whatever.

In my understanding, for XI to be able to pass such a message to integration engine, this function must be defined somewhere.

Any ideas?

Thanks, Stepan.

[udo_martens]

Hi Stepan,

you import the function module to the Repository where it is only a message type / an interface. The source system of the original function module doesn't matter, after the import you can delete the module.

The source code of imported RFC will be discarded. This task will be taken by your mapping and routing.

Regards,

Udo

[Former Member]

Thanks Udo, I'll try.

Looks a bit weird though.

[MichalKrawczyk]

hi,

>>>>my understanding, for XI to be able to pass such a message to integration engine, this function must be defined somewhere.

the RFC call is not passed to the WAS of the XI

but to the Integration engine so in a way

the "RFC adapter" handles the call

that's why you don't need any RFC on the XI site

you only need a function on the R3 site

but when it leaves R3 you can start thinking

about it as a message (and not a RFC)

used just to pass values

Regards,

michal

[Former Member]

So, you mean that name of the function can be just anything?

[MichalKrawczyk]

hi,

the function has to exist only on the r3

site so not anything but a normal FM name

then you import it into XI (just the structure)

(with the same name)

Regards,

michal

[Former Member]

Well, could be great if you shed some more light

How do I do the actual import?

[sam_raju]

Hi Stepan,

All the SAP Interfaces(metadata for RFC,IDOC) can be imported into your own SWC or SAP SWCs like SAP APPL or R/3_Basis and so on. These RFCs and IDOCs must exist in the backend R/3 before you can import them.

The Best practice is to import these interfaces into SAP SWCs to avoid any redundancy.

To import SAP Interfaces into your own SWC, you have to choose the radio-button "Import of RFC and IDocs from SAP permitted" and provide all the connection info to Backend R/3. This creates a node "Imported Objects" in your SWC.

When you select this node XI makes a connection to Backend R/3 and lists all the RFCs and Idocs available in that system. You have to select your specific RFC or Idoc from the list and import it. The Structure of this imported RFC or Idoc will then be used in the mapping.

Hope this helps.

Rgds,

Sam Raju

[Former Member]

Hi Stephan,

When you defined your sender RFC channel, you gave the system details for the "RFC metadata repository Parameter" right....

This is the system which the XI sender channel will use as its RFC repository...

So..the function template(interface) need to be created on the system given above...

Do the import from there...

Thanks,

Renjith.

[Former Member]

Hi,

Check this blog,

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

[Former Member]

As I wrote, destination is configured. I read this blog 3 times, it says nothing about function to call.