Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Timeout when processing IDocs

Former Member

‎2007 Sep 13 8:43 AM

0 Likes
933

Hi,

I have a problem when I process IDocs in CRM 5.0 system. The IDocs of BP are sent via middleware into my system. When I use BD87 to select some IDocs, it often to be timeout. And if I use report RBDAPP01 to process IDocs as a background job, it often took long time and not finished.

I have looked at process via SM51, and found the progress seems to stay at program "SAPLBUBA_4" or "SAPLBUD_MEM".

Do anyone know the cause of this problem? And how to solve it?

Thank you very much for your help!

Best regards,

Long

3 REPLIES 3
Read only

former_member404244
Active Contributor

‎2007 Sep 13 8:51 AM

0 Likes
581

Hi,

Instaed of sending bulk of idocs ,break them and schedule the program RBDAPP01..say there are 2000 idocs to be processed..

For exmaple create a variant of say 1 to 1000 and then schedule the program RBDAPP01 and once again crerate another variant with 1001 TO 2000 and then once again schedule RBDAPP01..Now in this case 2 jobs will shedule with 1000 idocs...

Regards,

Nagaraj

Read only

Former Member
In response to former_member404244

‎2007 Sep 13 8:56 AM

0 Likes
581

Hi Nagaraj,

Actuall even I process 500 IDocs, it would be timeout. The timeout occurred when executing first step "Data is being selected".

So what's the reason?

Best regards,

Long

Read only

bruno_esperanca
Contributor

‎2013 May 22 12:40 PM

0 Likes
581

Hi Long,

Any news on this? Did you manage to overcome this issue? In my project I'm having a similar issue. There was a timeout problem so the interface team "fixed" it by splitting the IDocs. The problem is that now some employees sometimes are not created in CRM. I don't know where the problem is coming from but I suspect they didn't perform the split very well...

Thanks.