Skip to Content
author's profile photo Former Member
Former Member

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

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>


*--Serdar">[ BC ]

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on May 17, 2005 at 10:01 AM

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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.