ASAP and eSOA: fit or non-fit ?

[Former Member]

When implementing SAP ERP including the likes of CRM and SRM we use package based implementation (PBA) methods, techniques and tools - often based on the 'old' Accelerated SAP (ASAP). With the SAP environment now rapidly turning to eSOA supported by the Netweaver platform, will this still be the right way to go ? SAP eSOA implementations seem to have a lot in common with Custom Software Development (CSD). Should we then turn to methods, techniques and tools used for CSD methods as well ?

What do you think ?

[Former Member]

>>ASAP and eSOA: fit or non-fit ?

in my understnading ..

ASAP is a methodology (it covers various phases of your work, like blueprinting/prototyping, realization/implemenation, releasing/going live etc) it can be applied to any project, whether SAP or nonSAP, eSOA or non-eSOA. it provides accelarators with ready-to use templates for requirement gathering, presentations, testcases etc.

eSOA is framework (may be somewhat similar to design pattern in software engineering) where you implement by providing/consuming webservices or enterprise services. every operation that we implement can be treated as a service at higher level.

in my experience,ASAP and eSOA are fit when used together.. provided we are clear with objective of each of them.

ofcourse they cannot be compared with each other.

thanks,

Madhu.