extended check

[Former Member]

dear experts,

I am debugging one program return by another developer,

In that he is return like below

DEFINE _break.

set extended check off.

break-point.

set extended check on.

END-OF-DEFINITION.

I didn't understand this, Can anyone help me to understand the same

thanks in advance

karthik

[Former Member · Accepted solution]

Extendended off/on will supress the warnings and error messages

in menu program>check>extended check and execute

it will show any errors in program

to supress those errors we use extended off/on

This statement can only be used for warnings and errors that the program author can explictly exclude as such.

[Former Member · Accepted solution]

Hi chendrasekar,

thanks for the answer, but my doubt is in prg itself breakpoint is mentioned,

so what will happen if we specify like this

[Former Member · Accepted solution]

this is the effect:

This statement defines an unconditional checkpoint (breakpoint). If the program reaches an active breakpoint during dialog processing, program execution is interrupted and the system switches to the ABAP Debugger. An inactive breakpoint will be ignored and program execution will continue with the statement following BREAK-POINT.

Without the ID addition, the breakpoint is always active. If the IDaddition is used, activation from outside the program will be controlled by a checkpoint group.

During background processing and during updating, program execution will not be interrupted. If the ID addition is specified, a breakpoint will always be inactive during breakpoint processing and during the updating process. If a breakpoint is always active, that is, the ID addition is not specified, the entry "Breakpoint reached" is written to the system log during background processing and during the udpate task. After the entry, the program name and the point where the breakpoint took place in the program are also recorded.

the sytax goes like this:

BREAK-POINT { [ID group]

| {[log_text] [AT NEXT APPLICATION STATEMENT]} }.

A breakpoint that is always active is used solely as a test help and is not allowed in productive programs. The BREAK-POINT statement without the ID addition therefore causes an error in the enhanced program check.

****reward if helpful

regards,

madhu