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

How to debug Inbound ORDERS - Idoc?

Former Member
0 Likes
5,502

Hi Experts,

Pls. clarify one simple doubt that,

My system EDI receives the ORDERS as Inbound Idocs. So, I need to find out/fix the issue related with Header Texts! So, I hv test data like,

1) Idoc #,

2) Name of the User Exit-SE38

So,

1) Shuld I go for WE19 testing tool?

2) or Keeping break-points in User Exit?

3) <b>Mainly, pls. let me know, How to proceed to debug the given Idoc # to fix the issue?</b>

thanq.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
2,859

If you want to debug in Dev or TST system then you can use WE19 Transaction.

Get into WE19 Transaction ,use idoc number -> here click on function module ,use debug mode.

or goto IDOC FM .. IDOC_INPUT_ORDERS -> search like customer-function -> keep break point and now run we19 transaction.

Note : it creates the new idoc number ,so please this method in dev or tst box ,do not use in Production system

Thanks

Seshu

Hi Experts,

Pls. clarify one simple doubt that,

My system EDI receives the ORDERS as Inbound Idocs. So, I need to find out/fix the issue related with Header Texts! So, I hv test data like,

1) Idoc #,

2) Name of the User Exit-SE38

So,

1) Shuld I go for WE19 testing tool?

2) or Keeping break-points in User Exit?

3) <b>Mainly, pls. let me know, How to proceed to debug the given Idoc # to fix the issue?</b>

thanq.

5 REPLIES 5
Read only

uwe_schieferstein
Active Contributor
0 Likes
2,859

Hello Srikhar

Recently I have to deal a lot with Inbound ORDERS IDocs. In case of errors I take the IDoc number, call transaction <b>WE19</b>, then function <i>Inbound function module</i> (= <b>IDOC_INPUT_ORDERS</b>) and start it in <b>debugging </b>mode.

The user-exits you have to look for are most likely in function group <b>XVED </b>(<i>User Exits for SD-EDI</i>).

Regards

Uwe

Read only

Former Member
0 Likes
2,860

If you want to debug in Dev or TST system then you can use WE19 Transaction.

Get into WE19 Transaction ,use idoc number -> here click on function module ,use debug mode.

or goto IDOC FM .. IDOC_INPUT_ORDERS -> search like customer-function -> keep break point and now run we19 transaction.

Note : it creates the new idoc number ,so please this method in dev or tst box ,do not use in Production system

Thanks

Seshu

Read only

0 Likes
2,859

thanq,

I selected <i>CALL TRANSACTION</i> radio button as Back ground! Is it OK?

Am getting the POP-UP with info message(Idoc status is 51),

<b><i>IDoc 0000000007353281 was saved and processed by

Function IDOC_INPUT_ORDERS</i></b>

1) Wht to do?

just curious to know that, pls culd u explain abt., the we19-->appl. tool bar buttons, like,

1) Standard Inboubd

2) Inbound FM

3) Inbound File: looks like, writing to desk top file!!

thanq.

Message was edited by:

Srikhar

Read only

0 Likes
2,859

You need to run in foreground, so it will open the debug editor. Keep a break point in the function module which will help in debugging.

Read only

0 Likes
2,859

Standard Inbound -> when you click on standard inbound it should have green color always if not then

you have fill control records like IDOC-> EDIT Control Record

Inbound Function Module :

Enter function module name -> if you need debug then choose call debug mode .

Inbound File -> you have to give file name ( Application server file name ),you should not use Local server file.

Once you select Inbound Function module then you get idoc number,you can see at WE02 Transaction to see the status

Thanks

Seshu