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

SM58 - Transaction Executing causing a Short Dump

Go to solution
Former Member

‎2012 Mar 06 7:18 PM

0 Likes
1,860

Hi Experts,

We have implemented logic to send outbout IDOCs (order response, invoice, delivery dispatch) to a BizTalk server. Most of the time IDOCs are sent out with no issue but there are times we see the transaction on SM58 in a stuck mode - Transaction Executing. If we check ST22, we find entires for short dumps pointing to calling SAP function module ARFC_DEST_SHIP. Does anyone have any idea as to why this is happening? We have met with the guys from BizTalk and our SAP admins. They have checked RFC setups and everything looks good. I really do not believe it is due to the control data on the IDOC since we can run BDA1 later to resend the IDOC and all is good.

Your help is appreciated.

Laura

1 ACCEPTED SOLUTION
Read only

Go to solution
Former Member

‎2012 Mar 07 4:24 AM

0 Likes
1,377

Have you debugged this program from SM58. Go to SM58 go to EDIT and select Debug LUW and try to get where it is giving dump.

Thanks,

Pawan

Hi Experts,

We have implemented logic to send outbout IDOCs (order response, invoice, delivery dispatch) to a BizTalk server. Most of the time IDOCs are sent out with no issue but there are times we see the transaction on SM58 in a stuck mode - Transaction Executing. If we check ST22, we find entires for short dumps pointing to calling SAP function module ARFC_DEST_SHIP. Does anyone have any idea as to why this is happening? We have met with the guys from BizTalk and our SAP admins. They have checked RFC setups and everything looks good. I really do not believe it is due to the control data on the IDOC since we can run BDA1 later to resend the IDOC and all is good.

Your help is appreciated.

Laura

Reply
6 REPLIES 6
Read only

Go to solution
Former Member

‎2012 Mar 07 4:24 AM

0 Likes
1,378

Have you debugged this program from SM58. Go to SM58 go to EDIT and select Debug LUW and try to get where it is giving dump.

Thanks,

Pawan

Read only

Go to solution
Former Member
In response to Former Member

‎2012 Mar 07 11:09 AM

0 Likes
1,377

Hello Pawan,

I tried as suggested but it seems I cannot debug type T transactions. The connection is a TCPI/IP connection. Do you have any other suggestions?

Thanks,

Laura

Read only

Go to solution
RaymondGiuseppi
Active Contributor

‎2012 Mar 07 3:14 PM

0 Likes
1,377

Check SM21 at date/time of dumps. If some deadlocks displayed, then check for OSS note on your system (a patch for database may be required to solve problem)

Regards,

Raymond

Read only

Go to solution
Former Member
In response to RaymondGiuseppi

‎2012 Mar 07 3:56 PM

0 Likes
1,377

Hello Raymond - as suggested, I checked SM21 for anything that occured during that date/time and it looks like this transaction was the only thing. There were no deadlocks.

Thanks for the information.

Laura

Read only

Go to solution
Mantovas
Participant
In response to RaymondGiuseppi

‎2014 Feb 06 8:33 PM

0 Likes
1,377

Hi Laura,

Did you find the solution for your issue?

Thanks.

R.M.

Read only

Go to solution
Former Member

‎2013 Oct 28 6:10 PM

0 Likes
1,377

Have you taken a look at the BizTalk hot fix: http://support.microsoft.com/kb/2845536

We encountered a similar issue and resolved it by implement this fix on the BizTalk side.

Thanks!