topic Re: IDOC Timeout in Application Development and Automation Discussions

IDOC Timeout

Former Member — Wed, 04 Apr 2007 01:33:44 GMT

Hi,

I have an IDOC problem and im not sure if it is a performance issue or a customization.

I have a job that runs program RBDAPP01 and processes all IDOCS of status 64.

The thing is the program terminates with a timeout error of maximum runtime exceeded.

The timeout is because of the long idoc processing (more than 600 segs).

Im not sure how to apporach the problem if the IDOC data is in question or a new code should be added. The dumps may be caused in ZXVEDF02 a custom user exit.

I also need to copy an existing IDOC and change the status to 64 so that there is test data that i could work with.

Any Input on this would be greatly appreciated.

Many Thanks.

Re: IDOC Timeout

Former Member — Wed, 04 Apr 2007 01:46:55 GMT

Take one IDoc and run the program RBDAPP01 in background.

If the background job is cancelled for soem reason then either its a customization issue or code (infinite loop etc ) issue.

If it pocesses successfully then it definitely is a performance issue

Re: IDOC Timeout

Former Member — Wed, 04 Apr 2007 03:24:11 GMT

charlesf,

Follow the below steps.

1. First find the program name by Job name.

For this goto sm37-->enter jobname and user name is ' * ' -

> Execute -

>slect your job and press the button "STEP" which is in Application tool bar (OR)

press (Ctrl_shift+F9). You will get the program name.

2. Goto program in SE38 and find the code where the program passing all the IDocs to program RBDAPP01.

Ther you put the LOOP .

Ex: suppose your program is passing the idocs 10000 so that program is going for dump. Instead of that control the idocs passing to 1000 . when Idoc reaches the 1000 call the processing progarm so no dump will occur.

Reason for dump is Basis guys use to set the max.process time of seeion is 30 min. so if you run all idocs it exceeds more that 30minu and will go for dump.

Don't forget to reward if useful.

Re: IDOC Timeout

Former Member — Wed, 04 Apr 2007 09:46:16 GMT

I found the error after a day of debugging, it was a sort statement of an internal table (sized 80005x140) with too much data.

Thank you all for your replies.