Idoc to RFC loopback

[Former Member]

Hi,

I am trying to send Idoc messages back to PI.

I have created an IDoc receiver channel which is sending Idoc to an RFC destination type T which is created in PI only.

Other field like port etc are taken from some SAP system.

This RFC destination type T has a program ID created.

I also created an RFC sender channel which listens to this program ID in PI. I also provided IDOCFLATTOXML module details in advanced tab parameters.

Now when I try to trigger Idoc so that RFC channel reads it back, it see error in sm58:

Use IDOC Adapter for FM IDOC_INBOUND_ASYNCHRONOUS.

This is not supported

When I check RFC sender adapter, it throws error:

"Error in processing caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: Use IDOC Adapter for FM IDOC_INBOUND_ASYNCHRONOUS. This is not supported by RfcAdapter."

Is there any way it can be achieved?

[Former Member]

Anirudh Vyas wrote:
Hi,
I have created an IDoc receiver channel which is sending Idoc to an RFC destination type T which is created in PI only.

For tRFC , you would need to create RFC destination of type 3  and not of type T

Regards,

Krishna

[ambrish_mishra]

Hi Anirudh,

Can you explain your scenario so that we can understand the design and requirement. I guess you are sending an IDoc to SAP and trying to get it back in PI and want to convert into flat file.

Ambrish

[Former Member]

Its more of a dare.

I am trying to send an Idoc from PI via Idoc Receiver Channel. And then trying to catch the same the Idoc via a RFC Sender Channel.

I am trying to catch that message back using a RFC dest type T using a common program id.

[Former Member]

Hi Anirudh,

First of all IDoc does not support Synchronous communication. Thats why you are getting below:

"IDOC_INBOUND_ASYNCHRONOUS".

Are using IDOC_AAE or ABAP IDoc adapter? In IDOC_AAE, you can make Sender IDoc to work as Synchronous using Modules, but not sure at the Receiver end.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/25/requestresponse-bean-for-idocaae-...

[ambrish_mishra]

Hi Anirudh,

IDoc is asynchronous communication as Abhijit has pointed out.

IDoc and RFC operate differently and you won't be able to send it back through the RFC adapter.

My question is what is the requirement or are you just trying to do something innovative

Hope it helps!

Ambrish

[Former Member]

Hi,

This is not a synchronous scenario.

I am trying to check if an Idoc sends a message to RFC destination type TCP IP, can RFC sender channel pick that same message via that program id?

I am trying to figure out why it should not work.

regards,

Anirudh.

[ambrish_mishra]

hi Anirudh,

For IDoc, you need an RFC destination of type 3 and Port configurable in IDX2 in PI.

As I said before, IDocs and RFCs operate differently. For an RFC to be able to send message to external system, it has to be remotely enabled and configuration needs to be done in ECC to send the message to PI via RFC destination of Type T.

I do not think the RFC adapter can pick up the same message via that program id because one LUW can trigger only if some workflow set up or configuration is done and that has to be explicit.

Hope it helps!

Ambrish