You are on page 1of 1

How to solve.Idoc Error 30.

IDoc status 30: The IDoc is not transferred to the asynchronous RFC
Although the partner profile is defined and the IDoc has been constructed, the IDoc cannot be transferred to the asynchronous RFC. The IDoc is not
sent, and there is no official entry in the RFC valuation (/nSM58) for the relevant subsystem.
You trigger transmission of the IDoc using report RSEOUT00. To start the report manually, choose Tools -> Business Communication -> IDoc Basis ->
Test -> Outbound Processing from IDoc (/nWE14), or schedule a regular job in background processing for this report.
Check the outbound processing mode for the IDoc in the partner profile.
Outbound processing mode 2: The system sends the IDoc immediately
Outbound processing mode 4: The system collects IDocs that have been created and sends them in packets of a predefined size.
IDocs are not intended to be sent directly.
For multiple idocs in stat 30 : Before submitting the program to RSEOUT00 .first get the idoc's which are having status 30 from EDIDC based on the
basic type and message type.
Now execute RSEOUT00 with multiple idoc's via selection-screen. Now u will get popup once but for multiple idocs processed at a time .

Status 30 in the IDoc can normally only occur if outbound mode is set to 4.

You might also like