Under some circumstances it may be more interesting to implement new applications using webdynpro rather than the dynpro technology, even though it has to run in the SAP Gui. A good reason is e.g. if the application needs to be able to run from a portal as well or may even be used by external folks. The zero-footprint and html-based character of webdynpro can then come in very handy.
When you run a webdynpro application in the SAP Gui there are limitations though. One of the most significant limiation is that you don't share the same unit of work. It would be bad arguable practice to e.g. use webdynpro for orderline-entry, while using dynpro for the order-header at the same time. Please also refer to https://service.sap.com/sap/support/notes/989286 .[paramters], e.g. SAPEVENTS:DISPLAYORDER?ORDERID=1100. Easier said than done, because from the Webdynpro Java environment links will eventually go through the URL class, which doesn't allow these SAPevents URLs. Because of that e.g. the LinkToURL-control or using a URL in an exitplug don't work for SAPEvents URLs.
