ABAP Web Dynpro in ECC 6.0

[Former Member]

Dear SRMers

System information SRM 4.0, R/3 4.6c

With our SRM 4.0 implementation we developed eForms in SRM environment, because BSP(Business Server Pages) functionality was not available in 4.6C.

Currently we are upgrading to SRM 5.0 and ECC 6.0, we have the option of implementing these eForms either using BSP's, ABAP WebDynpro's or ADOBE forms.

So we are planning to move existing eForms from SRM 4.0 to ECC, rather than moving to SRM 5.0.

Please let me know the pros and cons or advantages of doing this or is it better to keep it in SRM instead of moving to ECC 6.0

Points will be rewarded.

Thanks in advance,

Bob

[mr_stirfry]

Hello -

For your question to either keeping in srm (release 5.0) or moving it to ECC (release 6.0) during the upgrade of these systems. depends on what your eform is doing...what is the functionality? is it primarily accessing data in srm or ecc? is data being updated and if so, is it primarily updating srm data or ecc? if the eform is a functionality in ecc and it was just written in srm because of the available technology, may want to port to ecc, but it really depends on the eform and what it's doing and how much it is going to cost to rewrite it in the ecc environment. depending on what it is doing and how it is written...it may work after upgrade or just require minor adjustments, but this depends on how it was written and what it is doing. just needs to be assessed in terms of level of effort, risk, cost, support, available resource, etc. on whatever approach.

In terms of the type of technology if it is going to be rewritten, well, it need to be assessed as well.

=> BSP - If you compare how many standard SAP BSP objects have been written between SAP_BASIS/SAP_ABAP components 620 to 640 to 700...in SRM it's not that much (not too sure about R/3, ECC).

=> Dynpro for ABAP - This is the next gen of Web Enablement from SAP and SRM 6.0 is being re-written using this technology. It is like BSP with the concept of the MVC paradigm; however, more robust and flexiable than BSP.

=> Adobe Forms - Requires additional licensing cost, but if the eform is being used where you want the form to have Abode functionality and look and feel for the type of users accessing the eform, then may want to go with it, but there is other slick functionality with Adobe forms, but are you going to use it...if not, then why incure the additional licensing cost if you are not going to utlize the more advanced functionality.

OK, off of my break. Brain regenerated...

stirfry...today is fried beef.

[Former Member]

Thanks for your insight Stirfry. It was helpful.

Best regards,

Bob