Problem with Custom idoc sending

[Former Member]

Hi Experts,

We have created partner profile and port for receiver system, our idoc is Z (custom) idoc.

but the problem is here, when we are sending that idoc from R/3 system, it is in Yellow position with message number 30. How we can solve this problem.

Is there any other configuration required for Z (Custom) idoc.

Please help,

Regards,

Study SAP

[Former Member · Accepted solution]

Hi,

Check the partner profile in your system...

The problem might be with the output types...so run RSEOUT00 program...

thanks,

Madhu

Edited by: Madhu on Jul 1, 2008 12:35 PM

[Former Member]

Check Output Mode in partner profile..

set it to Transfer IDoc Immd...

If you set it to Collect IDoc, then you have to manually trigger IDocs from WE19

[Former Member]

Hi All,

Thanks for reply,

I need to send the idoc Automatically from R/3, I do not need to send that Mannually.

Ouput mode is already set for Transfer IDOC Immediately.

How I can do the same, is any other setting is also required for Z (Custom) idoc,

as my standard idocs are going fine from the same configuration, the problem is only with Z (Custom) idocs.

Regards,

Study SAP

[Former Member]

HI,

The problem might be with the output types...so run RSEOUT00 program...

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.

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

Thanks,

Madhu

[former_member537867]

Hi,

Plz do run program RSEOUT00 or transaction code BD87 to convert this IDoc from status 30 to 03.

And also:

Go to Tcode WE14 and execute

give the IDoc Number and Execute

then the Status will be changed to 03

Check this link for more information.

http://help.sap.com/saphelp_nw04/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm

U will find the solution here

http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm

An add on

Regards,

Vinod.

[Former Member]

First create segments and message types and idoc types. Then assign that idoc type with message type throguh WE82. Port can be coonfigured through WE21 and partner profile can be configured throguh WE20 and RFC destination can be configured throguh SM59.

The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.

Please check if the user id/Password that you have given has all the authorization.

Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.

There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..

regards

kummari