2008 Oct 22 6:14 AM
2008 Oct 22 6:19 AM
what method you are using..? if it is amessage control, then you can debug using update debugging option.
hi,
how we can debugging outbound idoc's.
2008 Oct 22 6:19 AM
what method you are using..? if it is amessage control, then you can debug using update debugging option.
2008 Oct 22 8:03 AM
Hello,
We can use the Standard Program RSEOUT00 to process an Outbound IDoc. While doing that, you can put a Break Point in the Selection Program / Function Module / If you have coded for any Custom Segments, you can Put a Break Point in the Customer Exits that you've used.
Alternatively, you can put a Break Point in one of the Customer Exit Calls that you've used and while Saving the Transaction, the Processing will automatically go into debugging.
Thanks and Regards,
Venkat
2008 Oct 22 8:29 AM
Hi ,
Execute the program RSEOUT00 and give the output type and set a break-point in the Code what ever u r try to execute.
this is for outbound process..
Regards,
Bharani
2008 Oct 22 11:23 AM
Hi
Here is the way to go:
1.Go to transaction WE19.
2.Give ur IDoc Number
3.Enter /h in the command field.
4.Press Standard Outbound Processing Button.
Cheers,
Hakim
2008 Oct 22 5:18 PM
hi
it depends how you are creating them, if they are created using change pointers then place a break point on the function moudule that creates it, this way you will capture the data in first instance
cheers
2008 Oct 22 5:30 PM
Sorry for the above reply..
thing is we can debug the outbound idoc through RSNAST00 in se38 .
execute the program RSNAST00 . and give the
Output application and Output type.and put a break point in the outbound program . try this way . if u r able to debug try the same thing with check the send again check button .
regards,
Bharani
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |