Idoc/RFC receiver adapter

[Former Member]

Hi

I am wrking on XI 7.0. I have R/s system as a recever and I have to use either Idoc or RFC adapter. I followed this blog and I see that for Idoc Receiver adapter we have to create RFC Destination only in XI. However when I did Idoc to File, I have done RFC Destinations in both R/3 system and XI. Is this an error or do we have create RFC destinations in both R/3 and XI.? Nw if am using RFC adapter at receiver side, then also do I have to create RFC destinatin only in XI or both in XI and R/3?

Midhun

[former_member190624 · Accepted solution]

Hi Midhun,

In general we will for Idoc (for asynchronous call) and for RFC(for synchronous call). Let us know your complete scenario (Idoc to Idoc , file to Idoc ,etc.)

However when I did Idoc to File, I have done RFC Destinations in both R/3 system and XI?

You created two RFC destinations(Type 3) . One in backend system to send idoc to XI system. And RFC destination created on XI system is for reading Idoc metadata from backend system and to send back the acknowledgements back to sender system(Optional).

Regards

Hari.

[Former Member · Accepted solution]

I think it's a File to Idoc, there is some confusion if it;s Idoc or RFC at receiver end

[ambrish_mishra · Accepted solution]

For reciever IDoc, an ABAP connection is required in PI system, apart from Partner profile set up in ECC.

Ambrish

[Former Member · Accepted solution]

For File to Idoc, how many RFC destinatins of Type 3 do we have to create? Both in XI and R/3?

Thanks for your help

Regards

[ambrish_mishra · Accepted solution]

Hi Midhun,

I already wrote :

For receiver IDoc, RFC destination (ABAP connection) is required in PI system, apart from Partner profile set up in ECC.

IDocs and RFC operate differently. For IDoc, you need an ABAP connection while RFC works on TCP\IP.

Ambrish

Message was edited by: Ambrish Mishra

[ambrish_mishra]

Hi Midhun,

>>>>>>However when I did Idoc to File, I have done RFC Destinations in both R/3 system and XI.

For IDoc to file, RFC destination is required only in ECC.

In XI, it is required for inbound IDoc scenarios or if acknowledgment IDoc is to be sent to ECC.

For receiver RFC scenario, you don't need to define an RFC destination since you provide the login credentials and system details in the adapter itself.

Hope it answers your question.

Ambrish

[Former Member]

For Receiver Idoc, File to Idoc, how many RFC destinations of Type 3 we need to create? It won't work without RFC destination in XI pointing to R/3 system

Thanks

[Muniyappan]

Dear Midhun,

For Receiver Idoc, File to Idoc, how many RFC destinations of Type 3 we need to create? It won't work without RFC destination in XI pointing to R/3 system.

i believe you are asking in XI side. then you need one. yes it will not work without creating it.

i think you can find all answers in the scn, did you search it?

check below links if you can get the some idea.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e...

http://saptechnical.com/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm

http://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/File%20To%20IDOC?bc=true

Regards,

Muniyappan.

[Former Member]

Hi Midhun,

          In XI when we use IDoc adapter we need to create RFC destination has to be configured in both XI and R/3.

           When we are using RFC adapter there is no need of RFC destination in XI or R/3 as the System details, user authentication will be configured in the channel itself . It is the RFC transport protocoland we will be connecting the system directly from XI.

- Muru

[Former Member]

Hi

I doubt what you said is correct. We have to create RFC Destination of Type T in sender R/3 when RFC sender adapter is used. There we have to mention Registered Program id.

I am not sure whether we need RFC destination for receiver RFC or receiver Idoc

Midhun

[ambrish_mishra]

Hi Midhun,

RFC destination (TCP\IP) is required in ECC for Sender RFC scenarios where you register the program id and provide gateway/program id in Sender RFC adapter. Once the adapter is activated, the program id gets automatically registered.

Hope it helps!

Ambrish