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
Showing results for 
Search instead for 
Did you mean: 
Read only

tRFC error status

Former Member
0 Likes
1,249

Dears,

I am getting the error "RfcAbort: get_idoc: file(IDOC TYPR) exist,..." at SM58 transaction and I can't find anything here about that message error.

I have checked the WE02 transaction and the Idoc was created, the RFC destination that the Idoc should be sent is working fine.

Testing the partner at IDOC transaction no problem was found.

The message error at SM58 is incomplete, is there any other transaction that I can check to clarify what would be happening?

Thanks for your attention.

Best Regards!

Anaer

1 ACCEPTED SOLUTION
Read only

ThangaPrakash
Active Contributor
0 Likes
896

Hello Anaer,

In the menu options goto EDIT --> Debug LUW.

Also Goto --> QOUT scheduler --> click on the respective destination and check the connection test.

Regards,

TP

3 REPLIES 3
Read only

ThangaPrakash
Active Contributor
0 Likes
897

Hello Anaer,

In the menu options goto EDIT --> Debug LUW.

Also Goto --> QOUT scheduler --> click on the respective destination and check the connection test.

Regards,

TP

Read only

0 Likes
896

Hi Thanga, thanks for your response.

I had already tested the connection and it is working fine.

When I tried to activate the debug option I get the error message "You cannot debug type T connections".

Is there any system log that I possibly could check to get more detais of SM58 errors?

Thanks in advance!

Anaer Lima

Read only

Former Member
0 Likes
896

Dears,

I got it sorted out by changing the message type defintion at transaction WE20.

Thanks again!