topic Re: Problem with IDOCS in Application Development and Automation Discussions

Problem with IDOCS

Former Member — Thu, 23 Mar 2006 15:27:36 GMT

Hello, I'm trying to send an idoc from one system to another. Yesterday I could move some idocs but later that day I couldn't move it anymore. I checked the bd87 and the Idocs are with "sent succesfully" status,but I can't see them in the target system. I checked and the connection between both of them are ok.

Can anyone have some informtation how to troubleshoot this?

Thanks

Re: Problem with IDOCS

former_member181966 — Thu, 23 Mar 2006 15:33:43 GMT

Looks like RFC connection is the only thing. Do one more thing, some time what happen your link might be working between system but the login and password for the RFC get expired or locked or change password. Go to Sm59 open up the connection then hit TEST->AUTHORIZATION ( F6 ) . I got this problem so many time . Just wanted to share with you .

Pl.. award the points if it helps you .

Thanks

Saquib

Re: Problem with IDOCS

rainer_hbenthal — Thu, 23 Mar 2006 15:34:47 GMT

Goto SM58 and check if they are stucked up on the t-rfc queue. If so, you can right click and choose Execute LUW to release them.

Re: Problem with IDOCS

ferry_lianto — Thu, 23 Mar 2006 15:38:04 GMT

Hi Scott,

Perhaps there is not enough in tablespace in your target system to receive and process incoming IDoc. Please check with BASIS/DBA to extend tablespace size.

You can archive (SARA) the existing IDocs in target system.

Hope this will help.

Regards,

Ferry LIanto

Re: Problem with IDOCS

Former Member — Thu, 23 Mar 2006 15:54:36 GMT

Thanks, they were in the rtfc queue, after I choose Execute LUW they were distributed succesfully. One final question, why did they get stucked in this queue?

Re: Problem with IDOCS

rainer_hbenthal — Thu, 23 Mar 2006 16:00:53 GMT

rfc users are treated as dialog users. If the target system cant take any more dialog users, logon fails and IDOCS are stucked up in the t-rfc queue. There are some other reasons, but during office hours this is the most error.