Idocs stuck in sm58

Hi All,
When I triggered Idocs in R3 ,they were stuck in sm58 with status : :000. I'm not able to release it.
I checked with port information, everything is correct.
When I checked with threads in SDN it says to check with authorization of userId in sm59 of R3. if this is
the case then I ll not be able to send any Idocs from R3. But in my case other Idocs are getting triggered,
only the newly created ones are stuck. Kindly suggest sollution to resolve this issue.

Hi,
for checking the metadata you could also have a look here:
http://help.sap.com/saphelp_nw04/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/frameset.htm
Regards
Patrick

Similar Messages

Select one of the installed languages- Idoc stuck in sm58

Hi,
We have observed a strange issue during testing.
Some interface Idocs going from R/3 system to XI got stuck in sm58 with error
Select one of the installed languages
Later it was found that language EN was not specified in RFC destination and in the user profile which was being used in this RFC.
It was fixed and interface was working fine.
What I was not able to understand was why other interfaces were processing Idocs successfully using the same RFC destination?
regards,
Anirudh

Hello,
Are your other interfaces still using the same RFC destination and port to PI , or do you have differnt? if different that could explain your issue.....

Idoc stuck in Sm58 Commit fault: ASJ.ejb.005043 (Failed in component:

Hi All,
We have an IDoc to File scenario and IDoc is stuck in tRFC with the error :Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad
This is the new PI box and IDoc is triggered for the first time.
RFC destination is created for PI Java Stack as we are using ICO.
PI Version: 7.31
Regards,
Mani

Hello,
If you still receive the error after the above recommendations please go to the NWA logs and traces in PI and provide the corresponding error message from the developer trace.
Also check the configuration as per the following link has been done:
Configuring PI 7.30 Java IDoc Adapter
Kind regards,
Sarah

Sm58 IDOC stuck

Hello,
IDOC stuck in sm58 with error No authorization to send IDocs with message type
scenerio is FTP to IDOC. We are using Pi7.1 its simple secenerio can u pls let me know what is case how can we solve this.

Hi Michal
do you not use the "Permitted Agent" then? or does that not have any affect at all???
Specifies the job (person or group of people) to be notified if processing errors occur on the IDoc interface. You can define up to three different jobs:
in the inbound or outbound partner profiles for special partners, messages and direction.
in the general partner profiles for special partners.
in the general IDoc Administration settings.

MATMAS outboud Idoc: problem in SM58

Hi experts,
i have done Idoc to File scenario through SAP PI 7.0 server,
here SAP ECC 6.0 is the sender (MATMAS05- idoc) and Fileserver is the Receiver system and the SAP PI 7.0 is the Middleware system.
created Prtner profiles, customer distribution model view and distributed.
i triggered the IDOC from SAP ECC 6.0 system, (BD10), in WE05it is showing as IDoc processing success, data has sent to port and the status code is 03.
then i checked in tcode SM58, there it is showing under the
user - username
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - PI7CLNT001
Status Text - : : 000
can anybody tell me what would be the problem?
Thanks,
Kumar

Hi,
what kind of connection do you use between ECC and PI - RFC / Proxy? You can check this via SM59.
Is the file reaching PI or does the IDoc stuck in SM58? If it stucks in SM58 - try to reprocess it (hit F6 button).
Also what settings do you use in WE20 for partner PI7CLNT001?
Thanks,
Kai

Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

Hi specialists
I'm trying to send an IDoc to our new PI 7.4 Java Only.
Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.
Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:
The IDoc Destination <blabla> was changed. Refresh the destination instance with
Meldungsnr. SR053
Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.
Thanks a lot in advance for any hints.
Renaud

Hi Iñaki
Great document btw... didn't stumble uppon this before. Thanks.
I carefully went through it but nothing I tried helped.
The RFC destination (PI -> ERP) is working fine.
The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.
BUT still: sending an IDoc from ERP to PI fails with this message in SM58:
The IDoc Destination <destinationName> was changed. Refresh the destination instance with
Meldungsnr. SR053
This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".
So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...
Best regards
Renaud

Idocs stuck in ECC SM58

Dear Experts,
I have an ICO configured scenario where sender is ECC and receiver is a 3rd party application (Sender IDOC_AAE-PI-SOAP asynchronous scenario). Idocs are stuck in SM58 of ECC, connection test of relevant RFC destination is successful.
Error text: Name or password is incorrect (repeat logon)
Please help in resolving the issue.
Thanks and Regards,
Mani

Hi Mani,
Please check the RFC user name and password which you have mentioned in RFC destination with the help of basis team, it will resolve your issue.
Just mail the screenshots to basis team they will help you.
Regards
Bhargava Krishna

In 4.6C, How to delete IDoc stuck?

Hi, experts
after I load more than 20000000 records data from R/3 side, I found out there are too many IDoc stuck in R/3 side use SM58.
How can I delete these IDoc in one time? the T-CODE 'WE11' and the program 'RSETESTD' can not use in my 4.6C system.RSETESTD.

try BD87

Message stucks in SM58

Hi,
i'm trying to send an ALEAUD from XI to IDES (R/3 4.6C). It stucks in SM58: "Screen output without connection to user", what is obvisiously a message from R/3. Do somebody know that error?
Regards,
Udo

Check it out...
https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe">Handle Acknoledgements for IDoc</a>
From...
Yallabandi.

Messages stucked at SM58

Hi,
We have lot of entries stucked in sm58 of our production server. Even after trying Execute LUW/LUWS, these are not processing. Tcode SM50 have most of the dialogue process in waiting status.most of the entries stucked are for WF-Batch user and the user is not locked.
Thanks in advance.
Sudhir

Hi Vijay/Nipun,
Thanks for your replies.I have tried everything like unlocking the queue and refreshing them but nothing worked.This was all performance related problem.Finally we got to know that our target system response was slow, As soon as the target SAP R/3 system got quicker at response, all entries processed within a minute or two.
Thanks again.
Sudhir

Idocs stuck in workflow at status 51

Hi all,
There are lot of Idocs stuck in status 51 in workflow. Work flow error message reads as "Document OvershipCl does not exist". Can someone explain what does this mean and how do we clear these items.
Regards,
Santosh

Hi Santosh
You could also use transaction BD87 for further analysis and processing. This is more interactive. Please select the IDOC and on the left screen the the status record with entry 51 will have the details as to why the IDOC failed. Please correct as required in order that the IDOC will get processed.
Hope it helps. Please do assign points if found useful.
Regards,
Karthik

Reasons why TRFC's get stuck in SM58

Hi
Can anyone give reasons why TRFCS get stuck in SM58.
We have a problem and it isnt as simple as just releasing them manually as it is happening a lot so wondered if there was any tables or log that could be deleted etc
Cheers
Andy

Hi,
Please check the OSS Note 1025249 - Entries in transaction SM58 "hang"
Thanks,
Sridhar
Edited by: Sridhar Kaukuntla on Jun 30, 2009 9:40 PM

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Urgent:Idoc stuck with status 03 in TRFC

My Idoc is in status 03, but it is not reached to destination.
I guess It is stuck in Rfc layer or in some QUEUE.
There was quality system refresh last week here with Production system.
Pelase suggest what seetings need to be changed and where.
in SM58 it give the following error
'RFC address XXXXXXX doesn't exist'
(where XXXXXXX i m not mentioning here for Client security reasons)
is there any program to clear these layers?
Thanks a ton in advance and the answer will be adequately awarded.

hi,
whnevr ur idoc is in status 03 just run the transaction BD75.
the status will be converted to 12 and datawill be passed.
reward points if hlpful.

Process IDOC stuck up in TRFC

Hi,
I have an IDOC that is still being stuck in TRFC Queue. The status shows as '03', but I can see that IDOC in the TRFC queue. It is lying there for a month. I need to process that IDOC manually so that it goes to the other system. Which transaction can be used for that.
I tried with BD87 --- But here u have lot of other IDOCs also in TRFC and I cannot pick up only that one single IDOC from TRFC queue.
Please let me know the entire process.
Regards,
Anirban

Hi Anirban,
Please go to transaction <b>SM58</b> and check if the IDocs are stucked up on the t-rfc queue. If so, you can right click and choose Execute LUW to release them.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Idocs stuck in sm58

Similar Messages

Maybe you are looking for