Slashdot Mirror


SAP vs. Oracle, Battle Royale

Mark Brunelli writes "As the battle for business application supremacy heats up, Oracle users are standing by Larry Ellison and Fusion while SAP customers say NetWeaver will lead the way to victory." From the article: "Zoellner, who says he has worked with both Oracle and SAP users throughout his career, believes that the Nucleus Research study cited by deHenry is right on in its conclusion that Oracle's average three-year total cost of ownership (TCO) is 48% lower than SAP's. The business analyst said that the TCO issue is particularly important to companies in developing areas."

21 of 147 comments (clear)

  1. wow by caffeinemessiah · · Score: 4, Interesting

    if ORACLE's TCO is 48% lower than SAP, just how many small countries' budgets does SAP charge for a small installation?

    --
    An old-timer with old-timey ideas.
    1. Re:wow by tyler_larson · · Score: 5, Interesting
      if ORACLE's TCO is 48% lower than SAP, just how many small countries' budgets does SAP charge for a small installation?

      Costs vary (particularly installation and configuration costs), but as a rule of thumb, if your business's income isn't enough to make your state government envious, then SAP is not for you. If all you need is a "small" installation, then you really don't need SAP.

      Though I am interested in hearing what Oracle has to offer; I had thought that SAP was the only player in this field, which is why they can charge so much for such a horrible product.

      --
      "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea...."
      RFC 1925
    2. Re:wow by supersnail · · Score: 5, Insightful

      I have not much experience with Oracle ERP impelmentations. But my experience of both SAP and Peoplesoft is this:-

      It takes more effort and man hours to customise and install these products than is does to write an equivalent system inhouse, and, then you pay license fees.

      The main problem is upper IT management are sold on the "we implement best practice you dont have to change anything" idea. Which collides with the
      real world of "we dont do it that way here" of the business managers.

      The only way to implement these products quickly and cheaply^H^H^H^H^H^H for merely outrageous cost is to implement the vanilla package and change the way the business is run to suit. This usually involves sacking/losing half your business management to force the changes through.

      --
      Old COBOL programmers never die. They just code in C.
    3. Re:wow by molarmass192 · · Score: 3, Insightful

      configured in under a month.

      This would only be possible in a VERY small company rollout and with absolutely no customizations, no legacy data, or legacy workflows. I guarantee you, and yes, I've done several Oracle Apps rollouts, that a company with 1000+ employees has no hope in hell of rolling out a system in anything under 6 months. The average being well over a year. The longest part of these rollouts are getting people to sign off on workflows, the tech piece is a relatively small part of it.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    4. Re:wow by hey! · · Score: 5, Insightful


      It takes more effort and man hours to customise and install these products than is does to write an equivalent system inhouse, and, then you pay license fees.


      Well, it depends. Look at it this way, management is the customer. Your internal IT group is one vendor, SAP is the other. Does the customer really understand what he wants or needs? Probably not; they're focused on other areas. So as a vendor you need to have a market position -- an "elevator pitch". SAP's is pretty good: "we implement best practice you dont have to change anything". This is garbage to the developer's ears, but music to the customer's ears. What they are saying is the customer doesn't have to become an expert in the IT area, they can stick to their knitting and SAP will take care of the strategic IT direction. Lazy? Maybe. Sometimes Lazy == Efficient; knowing when this is so and not so is not a science.

      The next thing on the customer's mind is risk. Can the vendor do it? Well, looking around, pretty clearly a lot of people are have some degree of success with SAP's products. Can the same be said for you? No. While it may not be your fault, clearly the vendor you work for has not solved whatever problem it is to date, so in the customer's mind you're asking for a second chance. Unless you can convince them you're not their father's IT department, forget it. What you need is the one service that as an internal vendor you're not allowed to have: marketing.

      The thing that's never on the customer's mind is how much trouble it is for you. If another vendor makes the decision easy, offers apparently lower risk, then the fact it makes your life hell by making highly paid technologists do dull configuration work, well it doesn't matter. The customer would get rid of you if he could, but he can't figure how, so he may as well put you on work he understands, which is underwriting a safe bet.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  2. Oracle v. SAP? Huh? by ameoba · · Score: 3, Insightful

    It seems illogical to compare TCO of SAP, an established ERP platform, with Oracle, a Database that's in the process of buying the pieces to start their own ERP suite. Maybe in another 5 years when Oracle has their product line put together it would make sense to compare the two.

    Even at that, in the Enterprise market, where 'quality' is judged by 'longevity', Oracle's going to be at a major disadvantage.

    --
    my sig's at the bottom of the page.
  3. wikipedia says sap is... by r00t · · Score: 5, Funny

    2. A small, blunt object used as a weapon, often constructed from a bag filled with loose, heavy objects such as lead shot or coins.

    5. Colloquially, a sap is a weak or gullible person. Also known as dupe; see confidence trick.

  4. TCO by Anonymous Coward · · Score: 4, Insightful

    Why isn't Net present value used as the benchmark for comparing two IT projects? It really is the only one that makes sense because TCO doesn't take into account the interest rate.

    1. Re:TCO by the_womble · · Score: 3, Interesting
      Why isn't Net present value used as the benchmark for comparing two IT projects? It really is the only one that makes sense because TCO doesn't take into account the interest rate.


      Because everyone (i.e. including management) knows that NPVs are very uncertain thanks to all the assumptions that have to be made in order to calculate them.


      As non-IT people are less familiar with TCO they are less likely to be suspicious about the numbers.

  5. SAP == CRAP by autopr0n · · Score: 4, Interesting

    Seriously, how many people have ever had a chance to glimpse into the dark heart of SAP? It's very ugly. Hedious even.

    It might run business well, but it's hardly very extendable or flexible. Given the price you're better off writing your own system, IMO.

    --
    autopr0n is like, down and stuff.
    1. Re:SAP == CRAP by jools33 · · Score: 5, Interesting

      "Seriously, how many people have ever had a chance to glimpse into the dark heart of SAP? It's very ugly. Hedious even.It might run business well, but it's hardly very extendable or flexible. Given the price you're better off writing your own system, IMO."

      5 years ago I think this comment was valid.
      Having worked in SAP for over 10 years I can partially agree with your comments. Historically SAP has been slow to adapt its central ERP system (R/3). However thats not where the battle is being fought at all - and I think you've missed the point of the article. SAP's new platform - Netweaver really isn't one single system - its a complex architecture not a single platform any more. Its this architecture that Oracle is competing against by acquiring as many of the competition as possible and then trying to integrate them into a single solution. SAP have had a smarter approach where they have mostly not bought out the competition (althought thats not the case with MDM or Toptier). SAP have instead realised about 5 years ago the direction where things were heading and I really believe they are several steps ahead of Oracle now in terms of building a full blown Enterprise Services enabled architecture. In my opinion SAP have neglected updating the central (legacy) ERP system (R/3) in favour of building an enterprise services / integration architecture around the old central product - so much so that the old legacy R/3 system isnt really central anymore - the systems around it such as business intelligence, CRM, APO, Xi, solution manager have taken a much more prominent role - and each of these new systems - whilst running on the same base kernels really are completely reworked in terms of the architecture and APIs on offer.
      SAP still have a long way to go - and they could really do with reworking some of those older "hideous" code libraries - particularly on their R/3 platform. With Netweavers Enterprise service architecture - SAP looks to be truly flexible and extensible and leaving its old "hideous" code behind - and I suggest the previous poster take a read on http://sdn.sap.com/ for a more up to date understanding of what SAP today is all about.

  6. Re:Oracle v. SAP? Huh? by TopSpin · · Score: 5, Interesting

    in the process of buying the pieces to start their own ERP suite

    Oracle had a successful ERP platform years before they bought PeopleSoft. ERP is old hat for Oracle. The recent "fusion" work is their attempt to produce a new platform to replace the now rather mature Oracle ERP platform and provide a road for their recently acquired PeopleSoft and JDE customers.

    As far as TCO costs go, I wouldn't be surprised if Oracle was cheaper. The stack is, while highly proprietary, fairly streamlined compared to SAP.

    --
    Lurking at the bottom of the gravity well, getting old
  7. Article makes no sense, unless... by Anonymous Coward · · Score: 4, Insightful

    it's a carefully placed advertisement from the Oracle PR machine. 48%? Gimme a break, no one can determine TOC figures for something as complicated as SAP to that degree of precision.

  8. SAP : Oracle :: American Jobs : Indian Jobs by reporter · · Score: 3, Insightful
    There is another angle to the controversy of SAP versus Oracle. I agree that Oracle products are probably slightly more cost effective than SAP products. The reason is that Oracle has an aggressive, Darwinian work environment in which workers are pressured to produce. During performance reviews, the manager subjects all her workers to a Bell curve.

    By contrast, SAP has a kinder, gentler work environment that is subject to Germany's rules supporting a slightly socialist economy. The German products may not be as good as the American products, but at least, the German workers are happier than their American workers.

    In the SlashDot forum, many participants rail against the brutal competition posed by Indian workers who work for a fraction of the pay and benefits that American workers enjoy. If you are such a participant, then surely you prefer buying SAP products over Oracle products since SAP treats its workers far better than Oracle.

    On the other hand, if you believe that Americans should reduce their salaries to the level of the Indian salary and that Americans should dramatically increase their working hours to the level of the average Indian engineer's working hours, then surely your must prefer Oracle products. After all, the ends (i.e. cheap, high-quality products) justifies the means (i.e. brutalizing the workers).

  9. Re:TCO Why no open source alternative by bit01 · · Score: 5, Insightful

    Its too risky for a big corporation or organisation to develop one... You would need auditor sign offs etc.

    No, this is no different from any business software. ERP is just lots of little packages working together to organise a business.

    And the Oracle and SAP systems are top end...

    Only in the sense of "big money". The actual software itself is bottom end. As pretty much anybody who's used it will tell you.

    for large organisations milllions of transactions a day. Scaleable systems at that size are not built quickly

    FUD. Google, with one of the largest setups on the planet, uses open source software and doesn't seem to have any trouble. Scalability is just a design issue. Like everything else.

    and people want to have a vendor to blame.

    Sigh, more FUD. I'm quite sure that there are plenty of open source companies that would be happy to step up to the plate for an extremely good value maintenance contract (by SAP/Oracle standards) for any set of software a business wanted.

    There are legal issues as well to ensure Sarbanes-Oxley and Basel II compliance.

    No different from any piece of business software.

    I have tried to get my company to look at building an open source System to replace Peoplesoft instead of Fusion... but there is no interest.

    At your company.

    Open source ERP is potentially a large investment that could take a while to get payback on but it is also an area that could be done incrementally. There are a number of open source workflow packages that could form the nucleus of an ERP and there are many open source packages that could be adapted to perform various ERP functions. I'd suggest open source companies interested in this area pick some element of the ERP puzzle and specialise in it. By using open standards your software can then work with other ERP specialists and cover a larger part of the ERP space.

    If anyone does want to start one though - Im in !

    Glad to hear it.

    A big hurdle an open source ERP package would face is to find a businesses where the software could be tested in real life. Very few businesses would be willing to risk their core processes on something untested. Again though, it could all be done incrementally. Likely to be more cost effective and safer than many "big bang" SAP conversions.

    ---

    Don't be fooled, slashdot has many lying astroturfers fraudulently misrepresenting company propaganda as third party opinion. FUD too.

  10. Above the numbers by lucm · · Score: 5, Funny

    Until now I was sure that the only thing with a higher TCO than Oracle was a Sea Stallion helicopter (38 hours of maintenance required for every hour of flight). I guess I never thought about SAP TCO because most of the SAP rollouts I heard about failed.

    Those projects are so incredibly expensive, I have no idea what kind of scale they use to calculate the TCO. Teradollars? I can imagine a board meeting (CIO: "Hey guys, we must make room for 317 Teradollars in the next budget for this SAP thingy. So I guess we'll have to forget about the Winzip licenses for now.").

    Seriously, a friend of mine is convinced that SAP is part of a secret plan to crush the western economy.

    --
    lucm, indeed.
  11. The answer by SuperKendall · · Score: 4, Interesting

    The reason you have not seen an open source SAP is because it's so big and monsterous and hard to figure out what it does, that no-one knows if there's already an open source SAP or not. There could be several right now.

    Only half kidding.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  12. Oracle's lower TCO's reported against SAP by alchemistkevin · · Score: 3, Insightful

    on an Oracle affiliated site! Oh, it's very transparent and connects to well document studies, doesn't it? No? Anyways, we'll just take their word and say SAP's TCO is almost double that of Oracle's similiar offerings!? Similiar? Does anything from Oracle even stack up close to SAP's offerings? Nope! is the one word answer, no matter which camp you belong to, you cannot bring up a product that seamlessly brings together all aspects of a business as SAP does.

    All the modules can be individually customized and presented to the customer for his choosing whenever he wants to use that part of the package.

    No, it's not a battle royale, Fusion, never was and will never come close to where SAP is in the market today.

    High Costs!?!

    What's that, do you say a piece of code is costly just because it initially costs higher!?

    Have you ever worked in a company where SAP was implemented, do some costing for such a company and then come back and post on the cost savings they've had in their departments after implementing SAP, yes a few implementations do go pear shaped but this is generally not the case.

    I don't know about Zoellner's previous jobs but certainly can't find anything on google relating him to know anything that he claims to know about SAP.

    (Disclaimer: I'm an SAP Tech. Consultant)
    (home: http://alternateplanet.net/ )
    (blog: http://alternateplanet.blogspot.com/ )

  13. Silly Arguments by Trojan35 · · Score: 3, Interesting

    Guys, SAP has stuck around and will stick around because it's very hard to learn. You don't realize that sometimes it's more painful to fix a broken system than to live with its quirks. There are good reasons why businesses stick with SAP.

    Further, let's just drop all this OSS nonsense. I believe it would take 10+ years of development for anyone to seriously consider it. Let's say you develop a system. Who is trained on it? What major companies have successfully run it?

    Look how long it's taken Linux to gain acceptance, and Linux is something you can incorporate one server at a time. To move your whole company over to a new database system is not something anyone wants to do unless there's a proven, stable solution. This is just one of those areas where OSS can't compete effectively IMO. OSS isn't the answer to every question, as much as some would like it to be.

  14. Open Source's Big Weakness by simon_hibbs2 · · Score: 5, Insightful

    Ever noticed how all the biggest, most successful OSS projects are basic computing infrastructure projects? They're software written by techies, for techies. Things like compilers, operating systems, networking infrastructure, web server platforms, languages, databases. To write these things all you need to know is protocols, fundamental software architectures and how to program. They are areas where competent techie developers have a large amount of 'domain knowledge' - experience and in-depth understanding of the problem at hand.

    Open Source doesn't work well when the problem domain is an area that few techie developers have knowledge of. Then you need to bring in experts in the required area of expertise who have the time and motivation to contribute to an Open Source solution. Now this does happen, but it's much rarer. Take my employer. We produce engineering modeling design software for cellular mobile telephone networks. Our development team includes a group of very knowledgeable and experienced radio network engineers who do testig and write specs and requirements, include experts in 3G radio technology of which there are not many in the whole world. Without their contributions over the last decade, our software wouldn't be possible. You see a similar thing happening with computer games, which require a considerable, high-quality contribution of art assets.

    Techies have an innate interest in developing technological solutions to problems - if they have an itch it's likely to be a technical one and they are likely to want to develop technical methods of scratching it, which often means software. Artists, radio engineers and specialists from many other disciplines such as accountancy, human resources, etc don't have the same compulsion to develop or contribute towards software based solutions to their problems. It seems to me that corporate integration platforms like those offered by SAP and Oracle fall into the same category. They aren't the sort of problem you average techie is likely to feel any compulsion to solve, and those specialists you'd need to have involved in the development process aren't likely to be interested in doing so. This is where heavy ammounts of corporate funding is required to bridge the gap.

    Now of course this doesn't exclude OSS from the party. For example groups of companies could collaborate to fund an OSS solution to their common problem, but these are likely to be competing companies. We're talking about huge investments of cash here, invested over time spans of 5 to 10 years or more. I think OSS will eventualy start to penetrate into these areas as the software industry matures but I expect this will happen over the long term, like my lifetime for example.

    Simon Hibbs

  15. So much fud by al_broccoli · · Score: 4, Insightful

    If all of the people that had no experience in implementing or supporting SAP or Oracle ERP systems refrained from responding to this article, it would be very quiet in here.

    The fact of the matter is that SAP is a complex beast. I've been working with it, both developing and administering, for about 12 years now. I have no experience with Oracle's ERP product (though I am an Oracle DBA), but I'm sure it's just as sizeable. The issue with most "failed" SAP implementations that I'm aware of, and there have been many, is this - incompetence. Incompetence abounds in the technology industry. It's not isolated to SAP, either. I routinely interview job candidates for Oracle DBA positions, SAP Basis Administration positions, SAP BW Developer positions, and SAP ABAP developer positions. I find one very common thread among the candidates - very few of them know what they're talking about. If you hire them, either as an employee, or as a consultant, and they are the senior technical people on your implementation project, you are bound to fail. Whether it's implementation of the ERP product itself, or an implementation of new functionality. That's not SAP's fault, it's yours.

    In the end, the decision to go with Oracle or SAP should be based upon which product fits best in your environment, if either of them do. Interfaces are a significant part of this decision, and both SAP and Oracle have their strengths which need to be evaluated and prioritized. Supportability is, as well. If you are not willing to pay your senior developers and support staff more than $100K per year to maintain the product, then don't bother, you will likely fail. If the evaluation is done well, and the implementation is managed well, and you take care to hire the right people and retain them, then you will succeed.