Executing Idocs if stuck

Hi All,
When the data is moved fom ECC to BI, the idocs are getting stuck and hence the process is getting delayed.
One way to clear this queue would be loging to ecc side and then executing the LUWs.
Is there any other way to clear the idocs from the queue or excecute them.
Please do put in your thoughts on this.
Thanks in advance,
Veena A

Veena,
I hope there are so many threads available about this. Search with key work "BD87". You can find somany.
Executing LUW's is while transfering data after the extraction process. That is done in SM58 transaction.
But the IDocs could be stuck before the extraction. To find out whether there are any IDoc stuck in the source system, go through the following steps.
Go to TCode BD87 in the Source System.
In the selection screen, input the following values.
Partner system: <BW/BI Logical system name>
IDoc Status: 64 (IDoc ready to be transfered)
Message type (Optional): Most of the times it will be RS*
Execute the transaction, it will show you if any IDocs are in 64 status. Expand the node and select the IDocs that are in 64 status, Click on "Process" button in Appl tool bar.
If you look at the details in the Data Load Monitor (RSMO), also you can find out the OLTP IDoc number. That is pretty easy to process the IDoc from the source system.
Regards,
Shashi

Similar Messages

How do I execute IDOC for message type LOIPRO

How is it possible to execute IDOC using message type LOIPRO which I have configured with change pointers? Change pointers are using object ORDER.
I am looking to only generate IDOC for production order changes / updates that meets the criteria set by the change pointers. If something in the order changes, but that field is not being looked at by change pointers, I don't need IDOC to pick up that order.
I don't want to have to run RCCLTRAN or RCCLORD on a scheduled job. Only need to have activity if change pointers are activated. Am I going down the wrong road using LOIPRO ?

Hi Bob,
Could you please guide me through the process of creating/triggering a change pointer based LOIPRO? Your help much appreciated.
Tabraiz

IDOCs are "stuck" in the transaction IDXP

Hello,
I have a problem: IDOCs payment fornecedres are "stuck" in the transaction IDXP. I do not know exactly what is happening, but I release the IDOCs in IDXP and then they get stuck in the transaction SMQ2.
In transaction SM58 has an error log "Command to tRFC / qRFC: Execute LUW again.", Which is the same that appears in the log SMQ2.
The only thing I got is that the identifier field "package" is not filled in within the IDOC IDXP, but do not know if this influences into something.
Has anyone experienced a similar problem and could help me?
Thank you.
Edited by: fernando.mbernardi on Jan 9, 2012 2:26 PM

Hi,
It has nothing to do with Package filed,
please check below things...
Check if the Idocs are configured to process immediately in the partner profile.
Check if the Queues are scheduled to run automatically.
Check if the connection between the servers are working fine thru sm59.
Thanks...
Sukarna

Storage Issue in Database while executing Idoc to Jdbc scenario

Hi,
I am testing an Idoc to JDBC scenario. The scenario executes correctly, but the number of records getting stored in the database are not equalling the data present in the Idoc.
Eg: If the Idoc has data for around 75000 records to be saved, only around 50000 records are getting saved in JDBC SQl server database.
Please let me know what could be the issue and how to resolve it.
Regards
Kiran.

Check the output XML in XI;ie, the output of your mapping. Does it have the same number of records as the Idoc? if no the issue is in the mapping.
Regards
Bhavesh

Idoc getting stuck up in SM58

Hi All,
Previously we have created one outbound Idoc. we were passing data to external system via XI. it was successfully reaching to external system.
now we have added one more segment to existing Idoc. after processing doc, in WE05 transaction, Idoc status is showing as 03 i.e. data successfully passed to port. the issue is that the Idoc is not getting passed to external system i.e. XI . In SM 58, the Idoc is getting stuck up. it gives error message as below,
EDISDEF: Port SAPCAG segment defn Z2WY_SV_DLR000 i n IDoc type ZWY_SV_SPG_
Message no. SR053
Please let me know if anybody has idea on this.
Thanks,
Chandra

Hi Chandrashekhar,
If you are using XI/PI, go to IDX2 transaction and see whether the idoc is re-loaded successfully with new segment. If not, just delete the idoc and load it again for the port you are using. I think this should fix your problem.
Thanks,
Adithya K

Confirmation IDOCS are stuck with BBP_CO_WE

Hi experts,
We are building SRM 7 with ECS. We are connected to ECC 6 EHP4.
When we create CF, IDOC is not transmitted to backend.
In RZ20 we have those logs :
Backend goods receipt errors | Status attribute | BBP_CO_WE
In ECC inbound IDOCS are not there
It seems the problem is related to ECC config.
Any idea to be able to send IDOC?
Many thanks in advance.

Hello,
So, your IDoc is not in error.
Check the 'Outbound Options' tab for message type MBGMCR of R/3 backend Partner Type in WE20 transaction.
In frame dedicated for 'Output Mode', radio-button "Transfer IDoc Immed." should be selected.
Execute same check for message type SYNCH.
Regards.
Laurent.

Workflow; Trigger to execute IDOC matmas update

Hi
I do not know workflow at all. Is is possible to trigger a execution of an program using workflow as soon as there is a create/change of an material on the Materials master?
Message was edited by: Giovanni Baumann

Hi James
Thanks for your reply.
Your suggestion is as good as updating the dimension manual in Dimension excel sheet & processing. This processes will update the new data in mbr table . So in this approach following two steps involves
Step-1 u2013 Customer fills temp table or customer update dimension manually & processes it. Both the action will trigger package
Step-2 u2013 Data also need to be updated in data source i.e flat file. This task is performed by ETL team
Only when both of these task are performed that data source & BPC will in sync.
But what I want is only one step i.e. Step 2. This mean that when the data changes, the ETL team make necessary change in data source & this change should trigger the package. To do this I need to write cmd command to trigger the package.
I hope my situation is more clear to you know. Kindly let me know if you have any solution.
Regards,
Rahul

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 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.

Reclaiming stuck execute threads

Does anyone out there know of a setting in WLS 7 where you can tell it to reclaim
an execute thread that has been stuck for a while? There are settings to detect
stuck threads, but I would like it to reclaim (kill stuck one and create a new
one and add back to execute queue) that stuck thread after a set amount of time.
Will it already do this on its own; am I just not waiting long enough?

Hi Chris,
"Chris" <[email protected]> wrote in message
news:3eb143e6$[email protected]..
Does anyone out there know of a setting in WLS 7 where you can tell it toreclaim
an execute thread that has been stuck for a while? There are settings todetect
stuck threads, but I would like it to reclaim (kill stuck one and create anew
one and add back to execute queue) that stuck thread after a set amount oftime.
In Java there is no way to "kill" a stuck thread, and there is a good
reason for this.
The feature you are taking about is for diadnistic purposes
and should be used as such.
Will it already do this on its own; am I just not waiting long enough?If it's really stuck, you have to get a thread dump and find out
why thread stuck. You can get a thread dump by pressing
<Ctrl+Break> in Widows shell or sending kill -3 to the server
process under Unix.
Regards,
Slava Imeshev

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

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

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 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

Executing Idocs if stuck

Similar Messages

Maybe you are looking for