11-21-2011 7:22 PM
Hello Experts,
We are trying to connect an external system to SAP through iDoc and ALE mechanism.
As a part of iDoc data retrieval process We ran an initial load which created almost 1800 Idocu2019s in 17-18 hours
having around 4million records in them.
We need to improve the above performance and are wondering is this is related to any of the following:
Is it because of server memory or is there any way to speed up Idoc generation process?
How can we decide on the memory requirement based on data we process during initial load?
Is it possible to know how many records are there in evaluation path for particular OU ID?
Any additional comments on the above issue would also be helpful.
Hardeep
Edited by: Hardeep Singh on Nov 21, 2011 8:27 PM
11-22-2011 8:55 AM
Hardeep,
There can be many factors which is causing this. First thing to check, would be the system load at the time of IDoc generation. check SM66 or check with your basis colleague. Next thing would be, the way you create the IDoc & any custom code (in any user exit/BADI) which is causing this delay. You can put some trace or run time analysis (SE30) to check whether any custom code involved in it & which program is consuming the runtime the most. Check the outbound queues as well (WEOUTQUEUE).
Regards,
Gokul
11-22-2011 8:55 AM
Hardeep,
There can be many factors which is causing this. First thing to check, would be the system load at the time of IDoc generation. check SM66 or check with your basis colleague. Next thing would be, the way you create the IDoc & any custom code (in any user exit/BADI) which is causing this delay. You can put some trace or run time analysis (SE30) to check whether any custom code involved in it & which program is consuming the runtime the most. Check the outbound queues as well (WEOUTQUEUE).
Regards,
Gokul