topic Re: Commit in IDOC inbound in Application Development and Automation Discussions

Commit in IDOC inbound

Former Member — Thu, 26 Mar 2009 14:05:04 GMT

Hi experts !

I m facing a very strange issue ! My function module, which has a BDC, for incoming idoc doesnt commit work on creation of delievery schedule lines by me38. But I tried a test program which uses the same BDC code and it does commit work i.e schedule lines get created!

Please help me in this as I am totally clueless about the same.

The idoc stays stuck at status 62 !

Re: Commit in IDOC inbound

soumya_jose3 — Thu, 26 Mar 2009 17:31:38 GMT

Hi,

In BD87 , give the IDOC number, press F8.

Inside Select that entry again--click on Process button on application toolbar.

Your idoc will be posted and will be in status 53 if success.

If you don't want to process the idoc manually through bd87, you can also change the partner profile in WE20 for the message type to Immediate Processing ( Instead of Collect IDOCS). Then your idoc will be posted automatically and will be in status 53 when it reaches the receiving system.

Regards,

Soumya

Edited by: Soumya Jose on Mar 26, 2009 6:34 PM

Re: Commit in IDOC inbound

Former Member — Fri, 27 Mar 2009 12:56:43 GMT

I tried BD87 but my BDC isnt commiting work, its just gives me weird error messages which dont appear when I try the same values in the test program, i tried even hard coding values in the function module but it is still getting stuck at 51 with a weird error message EKET-MENGE(06) field is longer than its length.

Is there anything special I need to include in my function module for incoming idoc ??

Re: Commit in IDOC inbound

Former Member — Tue, 14 Apr 2009 12:03:01 GMT

Thread Closed. Problem was while using Call transaction