topic Re: outbound idoc in Application Development and Automation Discussions

outbound idoc

Former Member — Tue, 29 Apr 2008 06:26:17 GMT

I am getting error status as 29 for outbound idoc.what might be the reason?how to overcome this problem?

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 06:32:48 GMT

IDoc status 29: Missing or incorrect partner profile

To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners.

If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:

Define the missing partner profile.

Resend all existing IDocs, which the system has not yet been able to send.

For this error, the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user.

You trigger subsequent sending of the IDocs that contained errors from the inbox.

On subsequent transmission, the incorrect IDoc is flagged with status 31 and copied to a new IDoc, which is enhanced with data from the partner profile and transferred to the asynchronous RFC.

I hope it helps.

Thanks,

Vibha

Please mark all the useful answers

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 06:45:58 GMT

status code 29 related to error in partner profile..so check your partner profile consistency using RSECHK07 program...you may get the solution where you did wrong.

Regards.

Dara.

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 06:48:43 GMT

i have created the custom idoc for this i followed the following steps

1.created 4 segments

2.created idoc

3.created logical message type

4.linked message type with basic idoc type.

whether that is sufficient for a custom idoc

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 06:54:15 GMT

No..you have to distribute the idoc ...

after 4 steps do...

5)create one model view using BD64...assign message type and logical systems...

6)generate partner profiles

7)distribute the model view

Regards,

Dara.

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 07:05:54 GMT

status-26:syntax error in idoc(segment cannot be identified).for what reason this error occured and how to resolve it?

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 07:13:22 GMT

run the program RBDOUTPU and give the idoc number ...

go to WE19 ..give idoc number ...reprocess...

Regards,

Dara.

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 07:14:04 GMT

Error code 26 means the IDoc has an inappropriate syntax. The tree structure of an IDoc is defined in WE30 and tells the IDoc engine if a segment is mandatory and in which sequence the segments are organized. If you try to build an IDoc that does not abide by this template the engine throws a syntax error with status code 26.You can deactivate the syntax check in the partner profile definition (WE20).

I hope it helps.

Thanks,

Vibha

Please mark all the useful answers

Re: outbound idoc

Former Member — Tue, 29 Apr 2008 10:09:55 GMT

You can get the list of status description from table TEDS1. Status 29 says 'Error in ALE service'. Get in touch with the basis team to verify the ALE config.