topic Re: Idoc failed in Application Development and Automation Discussions

Idoc failed

Former Member — Thu, 15 Nov 2007 05:01:56 GMT

Hello gurus,

An Incoming Idoc is failed which was supposed to create schedule line in ME38 transaction code.Please tell me the steps how to know where exactly it is failed.

Helpful answers will be rewarded.

Urgent.

Thanks

Nisha

Re: Idoc failed

Former Member — Thu, 15 Nov 2007 05:07:54 GMT

U can check Idoc Status using the T-code WE02 or WE05 ,

and u can find out in Status Record .

Re: Idoc failed

Former Member — Thu, 15 Nov 2007 05:12:18 GMT

Hi Vijay,

Thanx for your reply

I have already seen that.My question is how to know where exactly it is failed.

Thanks

Nisha

Re: Idoc failed

Former Member — Thu, 15 Nov 2007 05:13:51 GMT

Hi Nisha,

Check below links may help in troubleshooting

http://searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html

http://weblogs.sdn.sap.com/pub/wlg/5212?page=last&x-showcontent=off [original link is broken] [original link is broken] [original link is broken]

Regards,

Atish

Re: Idoc failed

Former Member — Thu, 15 Nov 2007 05:14:44 GMT

If the IDOC created then u can check the IDOC status using the transaction WE05 or WE02.

Regards,

Arun.

Re: Idoc failed

former_member404244 — Thu, 15 Nov 2007 05:18:18 GMT

Hi,

First know the trigger function module name for ur message type..U will find it in WE57...Now go to WE19 tcode ,give the idoc number which was failed.then press on execute button..Now in the next screen press on INBOUND FUNCTION MODULE TAB in application tool bar .Now give the FM name thre,then check the check box 'CALL IN DEBUG MODE' and then select the radio button 'IN FOREGROUND' and then press enter .It will take u to the function module ,now debug and check ...

Reward if helpful.

Regards,

nagaraj

Re: Idoc failed

Former Member — Thu, 15 Nov 2007 05:20:03 GMT

Most of the times IDOC status record will have the proper message......or else U can also simulate the same using WE19 by passing same data and debug the the inbound FM to find out why it is failing to create the scheduling agreement.

Regards,

Arun.