ES Implementation Vs ABAP

[venkatesh_r]

Hi,

What is the technical difference between ES implentation(OO) and normal ABAP implementation?

What is the advantage of ESOA if ABAP implementation can solve the business needs?

Regards,

Venkatesh

[gaurav_modgil]

Hi Venkatesh

Enterprise SOA Began as an Effort by SAP to make its Solution More Process Oriented, Thus enabling business network transformation and operational excellence at the same time.What we mean by Process oriented is that we concentrate more on the Business Process in Question, rather than the individual system which answers a portion of out business requirements. Most of the Time Business requirements are not restricted to a Single Module.

For a Sales Person to work effectively, not only does he need to create a sales order in R3, but he needs to look after the customer complaints etc (CRM Jumps in), Also he needs to be aware of his own performance (BI jumps in).

Older transaction based approach was not fulfilling this complex interrelated requirement. The End user had to devide the business process into a series of transactions, and most of these in comples systems reside on different servers.

As of ESOA all the Systems Define the Operations as Services declared in ESR. Any Business application makes use of these services from one or more System as per the requirement. The following diagram makes understanding this scenario easier.

By Centralizing the Services at one Location (ESR) we get to concentrate more on the core business process in question.

Even Today at the Bottom ABAP implementation solves the business needs. The Only Diffrence here is that these indipendent implimentations(tcods) are published as services and used in composite applications.

Hope this answers your question

Cheers

Gaurav

[Former Member]

Differences between eSOA and ABAP Development.

1. eSOA is system/language independent for integration with other systems. All communication happens using SOAP and wsdl.For the exchange of data CCTS (Core Component Technical Specifications) guidelines are followed.

In ABAP, the programming language rules the capabilities.

2. In eSOA development, UI can be from any technology. The power of SAP may run only in the background.

In ABAP, the frontend is also ABAP / Dynpros.

3. In eSOA managing (creating and maintaining) the services is more cumbersome than straightforward ABAP coding.

4. ABAP may be plain or Object Oriented. eSOA is Business Object Oriented; i.e. the objects have business related meanings.

Advantages of eSOA

1. Faster composition of new Applications that may be needed

2. Greater flexibility in changing processes owing to legal/ business related changes

3. Easy decoupling of UI from Functionality and replacement of UI

4. Easy elimination/addition of new process steps

5. Lower TCO for the customer in the long run

6. Ability to innovate in Business Processes

7. Open Standards and easy integration with other applications

8. Better ability to do business over the internet by providing Self services to buyers, suppliers and partners