You can do ABAP debugging from java applications here is how :
-
Check whether your user has debugging authority. Auth. object S_DEVELOP has to contain 'DEBUG'
-
Use su01; ROLES
-
Double click the different roles ->
-
new session will open
-
Choose Authorizations -> Display Authorization Data
-
-
go to the ABAP coding
-
go to the menu Utilities -> Settings / choose tab "ABAP editor " / choose tab "Debugging" check the chek - box "Actv." in the User field enter the user used in the Java logon (not the alias of the user!! e.g. for BRUNO enter "3B1968D7DD1")
-
Press enter or choose OK to get back to your source code
-
If you set your next break-point a pop-up will occur to ask you if you want to set an external break-point or a session break-point --> click external break-point (= former HTTP break-point) -->
if you run you Java application now and the coding with the break-point is called a new R/3 (CRM) window will open and you will see you code in debug mode (may take some seconds)
You can do ABAP debugging from java applications here is how :
-
Check whether your user has debugging authority. Auth. object S_DEVELOP has to contain 'DEBUG'
-
Use su01; ROLES
-
Double click the different roles ->
-
new session will open
-
Choose Authorizations -> Display Authorization Data
-
-
go to the ABAP coding
-
go to the menu Utilities -> Settings / choose tab "ABAP editor " / choose tab "Debugging" check the chek - box "Actv." in the User field enter the user used in the Java logon (not the alias of the user!! e.g. for BRUNO enter "3B1968D7DD1")
-
Press enter or choose OK to get back to your source code
-
If you set your next break-point a pop-up will occur to ask you if you want to set an external break-point or a session break-point --> click external break-point (= former HTTP break-point) -->
if you run you Java application now and the coding with the break-point is called a new R/3 (CRM) window will open and you will see you code in debug mode (may take some seconds)
No comments:
Post a Comment