topic Re: error idoc in Application Development and Automation Discussions

error idoc

Former Member — Mon, 07 Jan 2008 11:54:46 GMT

how to handle error idoc

Re: error idoc

Former Member — Mon, 07 Jan 2008 12:03:02 GMT

IDoc status 07: Syntax error in IDoc

On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition defines the syntax of the IDoc. The syntax includes:

The individual segments of an IDoc type

The relationship between the individual segments

How many segments can be sent in one IDoc

Normally, incorrect syntax in IDocs only occurs in testing. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

I recommend only switching on the syntax check during testing of IDocs created yourself. You activate the syntax check via the partner profile for one IDoc type and a one particular partner.

51 -- application document not posted

60 -- error during syntax check for idoc

means while creating idoc partner profile may not be distributed from source to destination BD64 or might be problem in RFC destinations SM59

if helpful reward some points.

Re: error idoc

Former Member — Mon, 07 Jan 2008 12:04:30 GMT

Check the link below:

http://www.erphome.net/pdf/tech/J07.pdf

http://mailman.mit.edu/pipermail/sap-wug/2003-June/009715.html

Regards.

Re: error idoc

Former Member — Mon, 07 Jan 2008 12:06:30 GMT

Hi Shankar,

In transaction SW05, Double click on your IDOC number to go to IDOC display. Then under status record you can see various error .

if you give me brief i can help you out more.

Thank you .

Regards

Ram

Re: error idoc

Former Member — Mon, 07 Jan 2008 13:58:44 GMT

Hi Shankar,

There are many status in which an Idoc could be in error.

Like 02,30....etc at outbound 51,64....etc at inbound side.

For 02 and 30 :

1. Use RBDAGAIN(for 02 Idocs only) and reprocess the Idocs using a back ground job.

2.The Idoc would be in 30 status now.

3.Now use RSEOUT00 to push the Idoc to success state (03)from error.

For 51 status,

1. Use RBDMANI2(for 51status Idocs only) for transactional message types and reprocess the Idocs using a back ground job.

For 64 status,

1.Use RBDAPP01 to push the Idoc to success.

If you can specify the error in particular,I can help you better.

Thank you,

Sravani.