Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

SAP is Boring 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It is frightening to think that a significant proportion of the world's large corporations and government entities are running their operations using SAP's product. I had the misfortune to participate in a SAP implementation at a $700 million manufacturing company a few years ago. One of the more banal stupidities of SAP was that all of the shortcut acronyms were based on German-language phrases; great if you are German but hard to remember otherwise. Another outrage was related to a training class that

    • One of the more banal stupidities of SAP was that all of the shortcut acronyms were based on German-language phrases; great if you are German but hard to remember otherwise.

      Welcome to the rest of the world.

      Sorry, but I can’t feel much sympathy for you there. :-)

      I have no trouble making sense of the predominantly-English world of programming, but living in Germany, I see plenty of people struggle with it in exactly the way you describe. The only difference is that language-wise, the tables are

      • I know it's unfair to expect everyone else to code in one's own language. However given the cost of the product the fact that much of the core technical documentation isn't available in the customers languages is a bit much.

        Even if you exclude the language issues, SAP is very poorly written and a lot of the customer extended code is even worse. SAP themselves don't even encourage good coding practices, it's very much an attitude of cut'n'paste is best - thinking is not required...

        --
        -- "It's not magic, it's work..."

        • However given the cost of the product the fact that much of the core technical documentation isn’t available in the customers languages is a bit much.

          Oh yeah, no argument at all about the docs.

          • As a counterexample, my understanding is that Novell in its heyday put a lot of emphasis on something they referred to as "localization", which I believe meant adapting the software and documentation to the language of their target markets. The idea being that they were likely to sell more product if language/cultural issues were minimized. Of course, we all know that Novell put together great products but couldn't market them literally to save their company.

            SAP of course does its selling to C-level executives who couldn't care less about the nitty-gritty details of whether the product is all that well put together. Companies bought ERP because "everyone else is doing it, we don't want to be left behind."

            • Having a good product is a sure fire way to go bust...

              Look at Microsoft: mediocre products, grossly overpriced and huge profits. Admittedly they have often been given their monopoly by the incompetence of their competitors and/or their own dirty tricks, but you do get the feeling that the crap will inherit the profits...

              --
              -- "It's not magic, it's work..."
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.