unable to debug Sales Order output

[Former Member]

Hi,

I am having some problems trying to debug sales orders output. I have a breakpoint which is ignored. I have had a similar problem with purchase orders but I got round this by setting the output to send with transaction own application and then choosing transaction ME9F to run the output manually. I am not sure however how to run the same setup for sales orders (or indeed if this is the same setup as purchase orders)

Would appreciate anybodies thoughts

Cheers

Paul

[former_member181995]

Just run RSTXDBUG in se38 and give give printout you will automatically come in debug mode.

Amit

[Former Member]

Hi

Go to Logistics->Sales and distribution->Master Data->Output->Sales Document

Max

[krishnendu_laha]

Hi Friend,

To debug an output:

1. If it is script, go to SE73, Utilities -> Activate Debugger

2. If it is smartform. go to smartforms, and write code *BREAK-POINT <USER NAME>.

Hope it will help you.

Regards

Krishnendu

[Former Member]

Hi ,

do uknow the driver program ? if yes , then goto that program search for FORM ENTRY.

nace-->application V1--> search for ur sales order output types , processing routines.

regards

prabhu

[ian_maxwell2]

Some outputs are actaully generated asynchrnously via an Update Task. If it is not hitting your break-point then the reason usually is that it is actaully happening in a seperate task (ex. FM in new task, or Update Task FM).

The way that you can debug this is:

1. Go into the sales order, and do a "/h" followed by hitting enter, this will cause the debugger to come up.

2. If you are in the new debugger then goto "Debugger->Switch to classic debugger" (This is just becuase I haven't tried this in the new debugger so I'm not sure the exact menu options)

3. Goto "Settings->Update Debugging", this will turn on update debugging and should give a message at the bottom of the screen saying "Update debugging turned on"

4. Press F8 to let the sales order program continue running. Update debugging will remain turned on until you leave the transaction

5. Do what ever you do to genernate the output and save the sales order. During the sales order save is when update tasks are triggered. By setting update debugging turned on it will actually stop on break points inside the udpate task.

Hopefully this helps. I guess it depends on if it is due to the update task or not, but I know that in the past I've had similiar situations.

~Ian