break point

[Former Member]

Hi Experts,

What is the differece between session break point and External break point which we can see in SE 38 screen in ECC6.0

regards

[former_member196299]

hi Ravi ,

There is a small difference which could be easy to understand :

External Breakpoint can be started from outside the SAP GUI (e.g. WebDynpro)

Session breakpoints are used if you start a programm or something like that in SAP GUI.

If external debugging is not active, you habve to activate it in SE80 Utilities->External Breakpoints.

Also make sure that in your Settings the correct debugging user is set:

Utilities->Abap_Editor->Debugging.

These informarions are from experts of the forum ..

Regards,

Ranjita

[Former Member]

Hi,

Sesssion break-point means it is valid for only for that session. if u comeout of that session no break-points exists.

If it is external break-point it will be there until unless u delete it.

Assign points if useful.

Regards

(YUGANDHAR.P)

[Former Member]

Hi,

External break point means you can use that from outside of SAP GUI also .which is specific to user and valid for limited time(2hrs).where as session break point is active till that session is active.

reward if needful...

[Former Member]

Hi

<b>Displaying Fields from External Programs</b>

You can also display the contents of fields from external programs if you know the names of these. To do so, enter the program name in parentheses before the field name: fieldname(programname).

Special Types of Field Display

• As in the program source code, you can make offset and length entries for character-type fields. If, for example, you enter sy-datum+4(2 ) in the field display, the current month of the system date is displayed under Field contents.

• If you specify an integer in angle brackets after the name of an internal table, the content of the line that corresponds to the integer is output. The entry itab[4] , for example, displays the fourth line of the internal table itab . If the integer exceeds the number of current table lines, the table will be flagged as unknown.

• With data references, the content of the referenced data object is displayed if an arrow and asterisk are appended to the name of the reference. r->* displays the content of the field that is referenced by the data reference r .

• If you double-click a data or object reference under Field contents in the default display mode, all the attributes and field contents of the referenced data object are displayed in the next screen (data references). The attributes and values of the current instance of all referenced classes and interfaces are output under object references. 7<cl> , for example, displays all the values of the seventh instance from class cl .

• The headers of strings, internal tables as well as data and object references are displayed if you place an asterisk at the beginning of the name. For example, the header of the internal table itab is displayed in hexadecimal format if you enter *itab in the field display. The field contains zeros if a table does not have a header.

• If you place an ampersand at the beginning of the name, the reference of strings, internal tables as well as data and object references are displayed in hexadecimal format. The entry &s tr, for example, displays the reference to the string str .

<b>Transferring Breakpoints to HTTP and Update Sessions</b>

If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.

If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.

<b>Reward if usefull</b>