Skip to Content
0
Former Member
Mar 05, 2009 at 04:51 PM

Justifying using Web Dynpro over traditional SAPGUI dynpro

459 Views

.

We are in the process of upgrading to ECC 6.0/Netweaver 7.0. Web Dynpro for ABAP will soon be available to our development staff. I can invision a couple of new projects that "might" benefit for a web type frontend, but not really sure. However, management is asking the question "What's so great about Web Dynpro vs. traditional SAPGUI dynpro?" There would be a lot of developer training needed, both in Web Dynpro, and in OO for our traditional ABAP developers (me for instance) to be able to develop these type of applications. The idea of learning something new seems great to me, (in a gee wiz, look what this can do! sort of way), but that doesn't impress management as the reason to do something. The want business advantages, before spending time and money on stuff.

There is another thread asking this same question that was just closed due to not being answered

I am not sure I could ask it any clearer so I am reposting his question:.

"Hi,

I am new to web dynpro ABAP and therefore have a very basic question.

Assume that a customer wants to implement SAP EEC 6.0.

What is the advantage for the customer and developer to develop and display all custom objects using web dynpro abap and displaying on the web as against developing and displaying in the SAP GUI?

Cheers,

MIck"

I (along with many others I'm sure) would really like to see this question answered.

Thanks