Tuesday, March 21, 2006
Web Services Pipeline | SAP's Agassi Unravels The Meaning Of NetWeaver
Web Services Pipeline SAP's Agassi Unravels The Meaning Of NetWeaver: "CRN: At the last SAPphire conference, SAP made it abundantly clear that NetWeaver is critical to the company's product and marketing strategy. But NetWeaver provides so many functions, like business integration, business intelligence, composite applications and RFID support, that it's really hard to know what NetWeaver actually is and what it means to your partners and the partners of IBM, Oracle and other infrastructure companies.
AGASSI: If look at what SAP does really well, is we take non-core processes that are essential to run your business but not necessarily differentiate it. They are called best practices. Best practices are things that all companies need to do. Order to cash. Inventory management. Things of that nature. And we let you do them in a package that's out of the box. That's the classic SAP applications.
Now look at core processes, which require you to come in and build something that's differentiated. When we looked at core and non-core, one of the things that we realized is things that you may view as core today may be seen as non-core three years down the road. Things that differentiate you and allow you to capture market share, a few years down the road your competitors are pretty much doing the same things. But if you've built these two in context on two separate islands, you will still need to maintain the code you wrote for these core processes for ever and ever and ever. "
AGASSI: If look at what SAP does really well, is we take non-core processes that are essential to run your business but not necessarily differentiate it. They are called best practices. Best practices are things that all companies need to do. Order to cash. Inventory management. Things of that nature. And we let you do them in a package that's out of the box. That's the classic SAP applications.
Now look at core processes, which require you to come in and build something that's differentiated. When we looked at core and non-core, one of the things that we realized is things that you may view as core today may be seen as non-core three years down the road. Things that differentiate you and allow you to capture market share, a few years down the road your competitors are pretty much doing the same things. But if you've built these two in context on two separate islands, you will still need to maintain the code you wrote for these core processes for ever and ever and ever. "
