cancel
Showing results for 
Search instead for 
Did you mean: 

How EOIO processing works with FILE to RFC dapter? Pls help!

gopalkrishna_baliga
Participant
0 Kudos

Hi Experts,

I have a FILE to RFC scenario.

FILE ---> XI ---> RFC(R/3 System)

In the sender FILE communication channel I have setup QOS as EOIO. After reading the file, XI sends the file data to RFC function module in another R/3 system. The RFC function module is Async that is, there is no Export parameter. It only has import or input parameters. Also in RFC receiver communication channel there is no option where I can provide QOS as EOIO.

Will the RFC function module process the input request message using EOIO that is, using a Queue?

Do I have to do something in RFC function module so that it receives and processes the input request in EOIO?

Thanks

Gopal

Edited by: gopalkrishna baliga on Jul 22, 2011 10:28 AM

Edited by: gopalkrishna baliga on Jul 22, 2011 10:49 AM

Accepted Solutions (0)

Answers (3)

Answers (3)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

You dont have control our inbound or target system. YOu can specify EOIO only in the sender system. Also as others mentioned you might have to change RFC to Proxy.

Former Member
0 Kudos

Hi,

What Debashis said is correct. No need to maintain QOS(EOIO) in the receiver side. You need to maintain it in sender only. Then the messages will be processed as EOIO in PI.

Regards,

Raju

gopalkrishna_baliga
Participant
0 Kudos

Message gets processed in EOIO in PI is fine. Buy what about in receiving system? Will it process the same way?

Thanks

Gopal

former_member854360
Active Contributor
0 Kudos

Hi Gopal,

RFC adapter does not support EOIO at all.

You have to change that scenario to ABAP proxy.

see stefans reply

Former Member
0 Kudos

Hi Gopal,

Instead of going with RFC adapter, go ahead with Proxy at the receiver side. That would help you in performance wise also.

Thanks,

former_member854360
Active Contributor
0 Kudos

Hi Gopal,

You do not need maintain EOIO in receiver, only in sender.

RFC adapter does not support EOIO at all.

You have to change that scenario to ABAP proxy.

see stefans reply

You may also check this doc

http://help.sap.com/saphelp_afs64/helpdata/ja/b1/c5ef41a0b99d39e10000000a155106/frameset.htm