Download source code of Web Dynpro ABAP methods

[Former Member]

Hi Experts,

I would like to download my source coding of Web Dynpro Methods to a local file. But I don't know how to do that. The download to a .txt-file is not the problem. I need help with a step before. Where lies the source code of Web Dynpro ABAP methods? For "normal" ABAP Objects class-method I would use the following code to get it:

DATA: itab_trdir TYPE TABLE OF trdir.
DATA: wa_trdir LIKE LINE OF itab_trdir.

SELECT * FROM trdir INTO TABLE itab_trdir.

LOOP AT itab_trdir INTO wa_trdir.
    READ REPORT wa_trdir-name INTO itab_source.
ENDLOOP.

But in the database table TRDIR there are not the Web Dynpro methods included I think! I would be enough for me to know, how to get filled an internal table like itab_source above with the coding. But can I do that similar with READ REPORT? And which database table have I to use? I tried to use the table wdy_ctlr_compo (methods/events of a web dynpro controller). I wanted to do a READ REPORT with the method names of this table. But that wasn't successful.

Can someone help? I do not want to use SAP Link.

Thanks a lot.

Best regards,

Ingmar

[thomas_jung · Accepted solution]

If you use SAPlink http://www.saplink.org - you can download the entire component.

If you want just the classes, that is a little bit harder. The classes are dynamically generated. There are different tricks to find out what the class names are. You should NEVER directly interact with the underlying classes. However if you just want to view the code in them you can see the class names in the debugger. Also if you want, you can just set a breakpoint within one of the methods and then choose utilities->breakpoints->display . You will see the name of the class where your breakpoint is set. It will be something like: /1BCWDY/4XLHG76LQV8VMTT2GRB2 - however you might find that it is difficult to look at the code from these classes; as we now restrict the ability to pull them up in the class editor. You just get a message that the object does not exist or is not assigned to a package. This restriction is a protection to keep anyone from accidentally changing the generated objects and corrupting the WD Component.