**** PLEASE HELP *****

[Former Member]

Hi people, I am puzzled with this problem and can’t figure out what is going on. I am doing ABAP for about 5 years and it never happened to me. This is what happening. I have a simple ABAP print program which prints barcode labels. The execution is controlled by the output type from delivery document. The output type is controlled by the access sequence which I setup in customizing. When I created this output type to print this barcode labels, I assigned a printing program and a form routine (which is just a sap script form). To make a long story short everything works but I can’t stop at any breakpoint in debugging mode that I put inside that program. I tried almost everything (system debug, ABAB debug) you name it, but my program never stops at the assigned breakpoint, or any other breakpoint that I put in it). Is anyone ever had this problem please help.

[former_member182371]

Hi Oleg,

i´m interested in the process of printing barcode labels for express shipping carriers through transaction VL02N.

could you please provide some hints or advise on how to do this?.

Best regards.

[Former Member]

HI Oleg,

Is your output type defined to trigger immediately upon save or is it only creating a NAST output record?

If it is creating a NAST record, then there is nothing in the transaction that you can do to debug. You need to go into the debugging of the RSNAST00 program for your output message with the appropriate selection values for output type, object number etc.

Regards,

Srinivas

[christian_wohlfahrt]

Hi!

In addition to John: earlier set break-points don't work anymore, but you can set new break-points online, when you are in update-task-debugging session (e.g. break at function module). Also statement 'break username' might help.

Regards,

Christian

[Former Member]

Usually if you are creating an output when a delivery is created or changed breakpoints only work when you turn on UPDATE Debugging. This is because Output is issued in Update task when the transaction commits.

If the above method does not work try activating the SAPScript debugger in SE71 and issue an output this would start SAPScript debugger if you are able to successfully generate an output. In SAPScript debugger to make sure you are setting your breakpoints in the correct program check value of &SYST-REPID&.

Hope this info helps you..

Shashi Reddy

[Former Member]

Thank you, but I tried this already, nothing seems to work. This is strange. I checked everything and it still wouldn’t stop at my break points. I am creating the output on the handling unit level, do you think this may cause the problem?

[Former Member]

There are some parameters called <b>DEBUG_MODE</b>, which is either enabled/disabled. The BASIS guys would have more idea on this.

Clarify one doubt of mine : Does /h work ?

Regards,

Subramanian V.

[Former Member]

Hi Oleg,

Although you have switched on update debugging you can't use the F8 (Continue to cursor); you have to step into each function module called in update task and step out until you get into the function module which processes the output (probably RV_MESSAGE_UPDATE). This is the module which in the end calls your processing program and you should be able to stop there now.

Regards,

John.

[Former Member]

Have you tried using the following statement ?

  BREAK SY-UNAME.

Regards,

Anand Mandalika.

[Former Member]

Generally i use.

break-point.

try this, it works definitely as it worked for me many a times.

Thanks and Best Regards,

Goutham.

[Former Member]

/h work fine, it is activating my debugging session. When I go to VL02N and pack the material into the handling unit the output type is created and ready to print. At this point I want to step trough the code of the printing program which calling sap script form.

[Former Member]

/h work fine. I also switched update mode on in settings. It is activating my debugging session. When I go to VL02N and pack the material into the handling unit the output type is created and ready to print. At this point I want to step trough the code of the printing program which calling sap script form. The SAP SCRIPT form is triggered by the access sequence VV62. I put a breakpoint into the function module but it didn't stop there.

[Former Member]

/h work fine. I also switched update mode on in settings. It is activating my debugging session. When I go to VL02N and pack the material into the handling unit the output type is created and ready to print. At this point I want to step trough the code of the printing program which calling sap script form. The SAP SCRIPT form is triggered by the access sequence VV62. I also put a break point into the function module, but it never stops there ither.

[Former Member]

Hi,

Have you tried with VL74 reprint transaction? You should able to stop via this transaction.

Shelva

[Former Member]

This is good, you are right on target. I tried and it did stop at my breakpoints.

Thank you so much.