IDoc of output mode 2 is hanged in state 30 for some time

[Former Member]

Hi to all

I would like to apply to your experience about IDoc processing.

After I create an IDoc via <b>"MASTER_IDOC_DISTRIBUTE"</b>, the IDoc created is hanged for some time before it is dispatched. During the hanging time it stays in state <b>30</b> (IDoc ready for dispatch (ALE Service)) and in control records there is an "S" message of code "SAP" with message number "006" and ID "B1". After the hanging time, my IDoc is dispatched successfully.

When I trigger a test output with the <b>"Standard Output Processing"</b> functionality of the transaction <i>WE19</i> the new test IDoc is immediately dispatched.

I guess the problem should not be due to the adjustments of the partner profile or the port definition since <i>WE19</i> uses the same.

I have used <b>RSEOUT00</b> but still my IDoc is hanged for some time.

My port type is <b>XML</b> and the file is a bit large. In my partner profile:

- <i>Transfer IDoc immed.</i> = <b>'X'</b>

- <i>Output Mode</i> = <b>'2'</b>

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

[johan_geraedts]

Use transaction BD87, so you can force to status 03.

[ssimsekler]

Hi Johan

Thanks for the input. Sorry for not stating in my question before but I had tried that and it gives the same message and the state remains at 30.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

[Former Member]

Hi Serdar,

I've not used the XML port. What happens to the Idocs? Are they written down to the application server as an XML file?

Or are they transferred via RFC/HTTP? If so, what is catching them at the other end in your case?

Cheers,

Brad

[ssimsekler]

Hi

I have figured out the problem. I was testing the process with a FM which was calling "MASTER_IDOC_DISTRIBUTE". Since I was not leaving the FM test framework, the lock for the IDoc was not released which caused the IDoc not to be dispatched. An explicit 'DEQUEUE_ALL' within the FM solved the problem exactly.

<b>And Brad,</b>

The XML file is written to the application server. You define the path and the naming while defining the port. We plan to send the XML file via RFC.

As another aspect, in our project, for another integration issue, they used tRFC, as far as I know, to send IDocs to the partner system which has an IDoc parser written with Java.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>