Difference between File to Proxy scenario and File to RFC scenario

[Former Member]

Hi Guys,

I am little confused with the proxy scenarios. Just need to knw when do we go for proxy scenarios (since we ).

use function modules in this too).

If i have an option of File to RFC / File to proxy , which one is suitable.

what will be an ideal diference between file to proxy and file to RFC scenario

Regards,

Vinithra

[Former Member]

Hi Vinithra,

To put it in simple terms, if you think that there is a RFC function module which can be called at ECC to perform the particular operation you want to achieve, then you can use RFC Adapter but for rest of the scenarios where you anyways need to write logic from SAP PI perspective the approach would be to go for ABAP Proxies.

The main point to understand is that when you have something already existing like a RFC, you need to import that in ESR/IR and then create further design objects like mapping. So here it doesn't make much sense to generate a proxy after importing the RFC but in case you are creating a new Interface directly in ESR/IR, then you can directly generate a proxy from it and then generate the Proxy code which can be easily integrated with PI.

So conclusion: 1. If some standard/custom RFC (already existing) can achieve your task then go for RFC

2. If you start your interface from scratch in ESR go for Proxies.

3. If you need EOIO support at the outbound side , then its not possible by PI RFC Adapter, so go for Proxies.

Best Regards,

Pratik

[Former Member]

Hi

FIrst of all u can go to PROXY for bulk messages i..e. Mainly for ADAPTERLESS communications and complex requirements if standard RFC is not working and if you want to handle complex STRUCTURES because in case of PROXY u can create any time of structure at any way.

Also in process both will cross SM58 TRFC Calls and QUEUES itself but in case of PROXY it can call directly through from PI Integration Engine to R3 Decentralized IE i.e. Adpaterless means without going to Adpater engine since RFC lies on JAVA STACK..

Data posting wise there was no difference but only thing suppose if your standard RFC itself is not handling ur business requirements and if once after posting the data into the RFC suppose if you require agian to do some validations based on plants and some complex business logics and if you want to do or keep a triggering check point only on special conditions in that case

Internally this PROXY Code will first collect the data sending from PI and then internally it can call mulitple funciton modules and it can do any validations and it can play and it can tirgger in special conditions at particular time...

Regards

Amar Srinivas Eli

[former_member472138]

Hi Vinithra,

Proxies are interfaces, which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions. You can use proxies for systems with WAS >=6.20.

XI will communicate in native language with SAP systems via proxies. Proxies uses XML - SOAP based communication for both ABAP and Java Proxies.

RFC/Idoc Adapters will convert one format into another expected/target format, means from SAP standard formats and as well as 3rd party formats to target formats

Hope this gives clarity.

Regards

Pothan