Requires Free Membership to View
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial DirectorIDocs are a universal transport format to exchange data between SAP and external systems. When you process an IDoc, the data is unpacked from the IDoc by stripping the IDoc wrapper, like you take the gifts out of an envelope. Then the data is processed in a conservative way either via BDC, BAPI or some home-made coding.
BDC simulates the data entry via screens by taking the data out of a file and filling the screens automatically rather than having a user to type in the data. BAPIs are function modules that provide a standard API to access transaction data.
Knowing those facts you may understand that performance does not depend on the method you use to inject the data, but rather on the performance of the algorithms behind that process the data.
I am a bit astonished that BDC performs better than IDocs as I would rather expect the contrary. Probably your IDocs make a BDC call themselves instead of calling the processing routines directly.
In order to improve performance you have several options:
1. Buy a bigger machine.
2. Process a single IDoc with RBDMANIN via the performance monitor SE30 to see where the most time is lost. Often it helps adding some index to a table or letting the IDocs be processed on a several box which is not in the load balancing for dialog users.
3. Completely bypass standard processing and invent a slim processor to update the necessary data.
This was first published in March 2005
Join the conversationComment
Share
Comments
Results
Contribute to the conversation