Sending IDocs via RFC Adapter

[Former Member]

Hello!

In an itegration scenario, we need to send (non XML) IDocs via RFC to a remote R/3 system (4.6C). As we don't want to get these IDocs persisted on the target system, it's intended to address the remote functions directly.

Now the problem:

- RFC Adapter only works with XML IDocs (so we cannot transfrom back to native IDoc)

- IDoc-Adapter sends native IDocs, but only to IDOC_INBOUND_ASYNCHRONOUS on target system (and the Idocs will be persisted)

In a next step, we also tried to implement a workaround with a local ABAP proxy on the XI system. But it seems, that it's not allowed to call a abap proxy locally on the integration engine.

Has anybody any idea to solve this problem? Maybe I'm thinking too complicated Help is highly appreciated!

Cheers,

Matthias

[Former Member]

Michal,

thanks for your really fast reply!

We want to send for example WHSORD-IDocs. Until now, these IDocs are sent from an warehouse mgmt. system directly into R/3 and are processed by existing functions.

These functions are expecting IDocs as input, and it's pretty much work to change all the functions' input parameters. So we want to reuse these functions. (sorry I forgot in first post)

[MichalKrawczyk]

Hi,

what kind of document you want to post?

most (many) IDOCs use BAPIs so you can

just call the BAPI (RFC) from XI

>>>But it seems, that it's not allowed to call a abap proxy locally on the integration engine.

you can call it on another client on the XI

(which is set as application system in SXMB_ADM)

Regards,

michal