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.

Similar Messages

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

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

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

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

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

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.

Shipment IDOC stuck in status 03, having segments 86,255

Hi experts,
We have a small issue in the idoc being sent to partner.
An outbound idoc is stuck in status 03 , the idoc is from a shipment and has
448 deliveries in it. The idoc is with the 86,255 number of segments.
Idoc details:
Basic type SHPMNT05
Extension
Message type SHPMNT
The idoc is having all the deliveries of the shipments in the segments
E1EDL20.
Do we have any specific limits for : 1) Max Number of segments an idoc can
hold.
Please let me know. How we can over come this problem and send the idoc
successfully to partner.
Thanks in advance.
Regards,
Ram

Hi,
Process with program RBDMOIND to bring the idoc from status 03 to 12, and check the SM58 also.
1. Status 03 indicates "idoc ready to pass to port".
2. Status 12 indicates " Dispatch ok" means data transfered through port.
Thanks,
Asit Purbey.
Edited by: Asit Purbey on May 27, 2009 4:28 PM

Idocs stuck in tRFC queue - why?

We had an issue where 2 Idocs looked like they where sent from our
logistics box to our HR box, but in reality, they were stuck in the tRFC
queue in our logistics box.
The idocs were created 2 days ago and were never processed. When I found
them in SM58, I executed them and they were sent and processed
successfully.
Why would those idocs get stuck in the tRFC queue? Shouldn't the queue
auto-process those idocs?
thanks,
robert.

Hi..
Normally this will happen when you Set the "Collect IDOCs" Option in the Partner profile Outbound Message type.
In that case these IDOCs will be dispatched only when the RSEOUT00 program runs in Batch or Explicitly.
If you set "Transfer Immediately" option in Partner profiles then they will be dispatched Immediately.
reward if Helpful.

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

IDOCS stuck

Hi All,
I have infopackage running in BWP side which fetch data from R/3 side via IDOCS.
In BWP System the infopackage is stuck for hrs, usually get over incouple of minutes. Its an IDOCS issue.
1) In RSMO i am trying to refresh but not a single PSA is proceeding.
2) I dont have access to Tcode BD87 in R/3 side so cant check stuck IDOCS in that system.
3) From BWP i choose the PSA and went to Transact.RFC -> in the source system, but here i dont find any LUWs stuck, as here no stuck text status are in red,it says Transactional Recorded.
I am not able to find any other feasible option, can anyone have some other soloution to this issue.
All suggestion are welcomed.
Regards,
Amit.

Hi,
Check the RFC connection between BWP and R/3.
From R/3 side check the IDOC status and also check t-rfc qeuue..
Regards
Praveen

Idoc stuck in status 3 , Total number of segments : 086255

Hi experts,
We have a small issue in the idoc being sent to partner.
An outbound idoc is stuck in status 03 , the idoc is from a shipment and has 448 deliveries in it. The idoc is with the 86,255 number of segments.
Idoc details:
      Basic type       SHPMNT05
      Extension
      Message type     SHPMNT
The idoc is having all the deliveries of the shipments in the segments E1EDL20.
Do we have any specific limits for :       1) Max Number of segments an idoc can hold.
Please let me know. How we can over come this problem and send the idoc successfully to partner.
Thanks in advance.
Regards,
Ram

Hi,
Check with the packet size you have mentioned in the outbound parameters.. May be by increasing the packet size it may accommodate more records in one idoc..
or
Otherwise there may be a possibility that it may accommodate only 65535 segments.
Thanks&Regards
Sarves

Idoc stuck in trfc queue

Hi,
I have requirement where the idocs are sent to external (non sap) system, now when system is down or for some other reason the idocs gets queued up in trfc queue(SM58) , now when the system is up and running these idoc gets passed to the external system without any particular sequence, i.e. suppose for HR data there is 2 idoc for same employee and the IDOC1 should go before IDOC2 , then this not happens when the trfc queue(SM58) is cleared.
I wanted to know how to mantain this idoc Serialization so that the idoc go in sequence, i have gone through some idoc Serialization document but i think its useful when both system is receiveing system is also SAP.

duplicate post, locked.
Thomas

Sm58 IDOC stuck

Similar Messages

Maybe you are looking for