How to generate a WD4A-Component?

[Former Member]

Hi,

is it possible to generate a full WebdynproABAP component from scratch without using the workbench?

For generating ABAP-classic there exist several tools (ie.FunktionModules and methods) to save Dynpros, DDIC tables, function pools and classes in the system and to activate them; are there similar tools for WD4A?

Thanks in Advance

Sebastian

[thomas_jung · Accepted solution]

There are APIs for creating the WDA component. They are used in the workbench and by the SAPlink WD Plug-In. However they are not exposed nor supported for usage outside of the ABAP workbench code. So in practice, there isn't any public API that can be used.

What are you trying to acomplish? Perhaps the dynamic processing opportunities within WD might be enought to fit your needs without going as far as full component generation.

[Former Member · Accepted solution]

hi Thomas,

thanks for the very fast answer,

in the product ishmed (part of IS-H) i develop the PMD ("Parametrierbare Medizinische Dokumentation"). Its a tool to define document categories containing documentation elements.

Technical the admin at the hospital fills metadata tables (similar to the WDY_*-tables) and presses the generate button of the tool. On base of those meta data we create a complete dialog and print application, consisting of DDIC tables, function pools including dynpros and local classes (MVC) and SAPscript-Forms.

Via APIs we have runtime access to

- the metadata,

- the document content (read, check, save...) and

- the UI-properties (where is the focus in the dynpro, make a field invisible...)

The admin can write userexits (form routines or badis) which are called at defined steps in the generated code.

I started to develop a WD4A variant of PMD by using the dynamic processing opportunities you mentioned, it works well (the component builds the context and the ui dynamically), but i would prefer a generated component. This would make my developing process easier in the way that i can build a component for a given doc category using the workbench and then i can compare it with the generated component for the same doc category.

Whats about the performance of the dynamic variant? I had the impression, that the dynamic tools are for 'small' manipulation inside a static component...we have a 'total' manipulation.

So, i hope you understand my interest in this stuff.

As mentioned, i can solve my problems with the dynamic opportunities (very mighty!) but we have to make the basic decision between 'generated' and 'dynamic' solution.

oops...thanks for your patience...the text became a bit long.

kind regards

sebastian

[thomas_jung · Accepted solution]

That is a very complete description - although a usage scenario that is fairly rare I would imagine. I'm afraid for now there aren't public APIs for doing what you describe. There very well may be public ones in the future.

On the subject of dynamic processing, well the WD capabilities for dynamic manipulation are quite extensive (as you commented) and the performance hit is actually not that expensive because the routines are quite efficient. It will never be as performant as a compiled component, but I would be suprised if an end user running the application will be able to tell the difference.

[Former Member · Accepted solution]

Thanks,

at the moment my question concerning our decision is answered.

i watch this forum...to stay informed about generating

sebastian