on 04-30-2013 11:17 AM
Hi All,
I am currently undergoing confusion as to when to use Idoc sender and when to use Proxy. Please help me clarify.
Regards,
Shaibayan
Proxy is outside-in approach and Idoc/RFC's is inside-out approach for development.
Its about where you start to build first. In outside-in approach, you start first at PI by creating interfaces and then generate proxy code at the end systems based on the interface created in PI, where as in inside-out approach you start at the end systems by implementing the logic and creating sap interface like IDoc. PI will use this Idoc and then complete the process.
Message was edited by: Anand V D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In addition to above replies, ABAP Proxy uses local integration engine and it can communicate with central integration engine (PI abap stack) seamless and so no adapter is required (in case of sender) and the performance is much better than idoc. It also supports both sync and async. Whereas Idoc is completely async based.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shaibayan,
When you have standard IDOC's available in the ECC system and then needs to transformed and send to end system when ALE configuration is already set, then it is better to go ahead with IDOC sender. IDOC can only be used for asynchronous interface communication which can also be set for acknowledgements.
When you have custom structure when you need to capture the field values from different tables, proxy would be the best solution. Also, this can handle huge volumes of data and the transformation of data be handled inside proxy code itself. Proxy can be used as synchronous interface communication and also we can configure alerts if any failures.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1.Use Idoc adapter if standard Idoc is available to meet the business requirements.
2.Best option is to use a proxy while handling large volumes and developing a custom business processes.The biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will
and should give us a better performance.And proxy is synchronous and Idoc is Asynchronous.
3.Even Idoc passes Adapter engine as it sits on ABAP stack.so performance does not degrades.. the only this is that if standard is available and full filling ur requirement then why to create proxy. If not available then go for Proxy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shaibayan,
both have a good performance (compare to RFC).
If you need a response - if you want to read data from another system - you need to go for proxy; IDoc is always asynchronous.
If you have a kind of standard integration, that means, IDoc trafffic is already configured, then it s much easier to go for IDocs because you dont need to develop in ERP.
/Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chakrabarti,
Based on the business requirement we have to choose either Idoc or proxy.. Proxy is advantageous when going for large volume of data and synchronous calls.. so performance wise it is better than Idoc. you can implement what ever logic you want.. but if there are more fields transformation better go for Idoc.
try search in sdn.. difference b/w Idoc vs proxy.. you will see many discussions..
regards,
Loordh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.