Skip to Content
avatar image
Former Member

Idoc to RFC loopback

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?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • May 16, 2013 at 09:40 PM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • 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

  • avatar image
    Former Member
    May 22, 2013 at 10:44 AM

    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

    Add comment
    10|10000 characters needed characters exceeded