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

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

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.

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.

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

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

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.

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

File to IDOC stuck in the queue

Hi Expert,
I have a file to IDOC scenario. I checked in SXMB_MONI, I can see the file coming in. But it just stuck in the queue and won't send out to SAP system. When I checked the SMQ2, it tells me the status is "SYSFAIL'. I have checked my RFC, port, logical systems, profile etc. Just don't know where is wrong. Can somebody tell me what else I need to check? Thank you very much!
Charles

Hi Charles
Check SMQ2 and double click on the queue with sysfail status.
It will show you a new screen with a more detailed error description.
Regards,
Giuseppe

IDOC Stuck up at SMQ2

I am trying to push multuiple IDOCs in IDOC to File scenario. But 1st time scenario is working fine. but next time IDOC is stuck up in queues. When I deleted from SMQ2, it works fine for next immediate IDOC transition and again for further IDOC processing all get stuck up in queue. Is there any idea about it.

hi,
As experts said
from SMQR register/degiester and activate the queues again.
also do you need to maintain the order of idocs.
if not uncheck the maintain order at runtime in ID.
refresh ur cache.
keep the thread updated.
many thanks

Idoc stuck on smq2

I have a scenario where sending idoc from SAP ECC to SAP PI without error, but to reach the SAP PI is not processed, in reviewing the TX SMQ2 the idoc gets stuck and I have to activate them manually to generate the XML, as I can investigate because automanticamnete not processed and remain in waiting to be done manually

Hi Leon,
You need to register and activate the queue by using T-Code SXMB_ADM.
Also check if ithe queue is unlocked.
By using the transaction SMQ2 you can reset the queue's status.
Set IS configuration parameter MONITOR QRFC_RESTART_ALLOWED to value 1.This will initiate processing of messages stuck in the queue
You can run RSQIWKEX to run periodically. It resets the queues automatically.
You have to go to SXMB_ADM. Then click manage Queues and you have to dergister all the queues. After doing this you need to go to SMQ2 and you have to actiavte the queues.
After all this try to re-register the queues in SXMB_ADM ..
Regards,
Rohit

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

IDOCS stuck

Similar Messages

Maybe you are looking for