Hi Suchita,
The way I see it is that they are essentially the same in how they work, i.e. soap calls over http.
So, you could essentially web service enable whatever you want in the Abap CRM backend, that way you'll have webservices all over the place & make it very difficult to manage. But what you really want to do is create a more sustainable environment & one that can be governed & controlled in a better fashion. That where SOA (Service Oriented Architecture) came into the picture. With SOA you have a business object like Customer Management with it's underlying operations (e.g. create customer, maintain customer, delete customer etc...) grouped together in one service. So you call one service & then stipulate what you want to do. Prior to SOA you would have one web service for each operation. In the past, you could have coded one big Abap program to manage all this operations but then you have latency/performance issues. With the SOA approach each operation will have it's own Abap implementation/proxy.
Enterprise Services is SAP's take on SOA. Enterprise Services essentially encapsulate specific operations in a Business Process context. For a better definition read the first paragraph here:
[http://www.sdn.sap.com/irj/sdn/soa]
Regards, Trevor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.