Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Commit in IDOC inbound

Former Member
0 Likes
1,296

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 !

3 REPLIES 3
Read only

soumya_jose3
Active Contributor
0 Likes
690

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

Read only

Former Member
0 Likes
690

Hi

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 ??

Read only

Former Member
0 Likes
690

Thread Closed. Problem was while using Call transaction