‎2010 May 19 11:54 AM
Hi Everyone,
I have an issue to look into. There is an Outgoing Idoc (Msg type PAYEXT and Basic Type PEXR2002). Some of the segments are missing some data and I have to find out why. In the event module configurations we have defined a Z function module which is responsible for changing data in this Idoc. I have to debug this Idoc now to find out why some segments are not populated properly.
I would be grateful to all of you if you can let me know how to stop at break point.
Thanks a lot!!
SA
‎2010 May 19 12:41 PM
Hi,
1) put an explicity break point in your function module "break <userid>".
2) Go to transaction with generates the IDOC
3) Before saving the transaction activate debugging using '/h' in command.
4) Save the transaction
5) When the system is in debug mode, Select the menu option "Settings -> Update debugging".
In the message bar the message "Update debugging switched on" will appear. Press F8 to continue
execution. Processing will stop at the function module where you have created the explicity
break point.
Regards
Vinod
‎2010 May 19 12:47 PM
Hi
have you test to put a break-point in your function module?
in the process is in background you can't avoid it to go in background:(with classic debugger)
-when you save or F8, activate debugging: /h
-go to the menu SETTINGS
-Activate SYSTEM DEBUGGING/ UPDATE DEBUGGING/IN BACKGROUND TASK: DO NOT PROCESS
and after let's go debugging, it's stop when the process discover the break-point
Best regards
‎2010 May 19 1:47 PM
Hi Sachin,
Save the trasaction and get the object key (if u r an ABAPEr, ask the object key from functionals).
Pass the object key in selection screen of the program RSNAST00 and also other parameters. when ur executing it, execute in debug mode and see. You can see how the idoc is beeing created here.
--
Reddy