7 ms·
This is a good time to remind everyone of the rules of SAP integration: 1) Your company processes MUST adapt to SAP processes. That's it. You can try customi
by theshrike79 4y ago
This is a good time to remind everyone of the rules of SAP integration:
1) Your company processes MUST adapt to SAP processes.
That's it.
You can try customising SAP to fit your processes, but you will just waste time and hundreds of millions of money and then you will fail.
Lidl spent almost a decade and 500M€ on its SAP project, but didn't follow rule #1: https://www.henricodolfing.com/2020/05/case-study-lidl-sap-debacle.html https://www.henricodolfing.com/2020/05/case-study-lidl-sap-d...
- simonjgreen 4y agoThis is really rule 1 for any core LOB/BIS/ERP system, not just SAP
- ThePadawan 4y agoI was a developer on an ERP developed in-house once. In that case you're off.
- danuker 4y ago> You can try customising SAP to fit your processes So you are paying hundreds of millions to get a canned, pre-packaged, inflexible solution? Why is SAP still in business? Is it solely customer misinformation?
- _glass 4y agoNo, as in the article mentioned, there is so much configuration that you can do. It has it's own programming language, and nowadays a lot is processed in the backend. It helps a lot when implementing new things on top. It provides for you already an entity model, and you can easily add your own tables (which most customers do). Migration to a new schema is my favorite part that I miss when I develop in other systems. For everything there is a tool that grew many years and is really battle tested.
- zxienin 4y ago> Why is SAP still in business? Very hard to throw/replace ERP. It might happen but it‘ll take decades for global SAP installed base to shrink seriously. > Is it solely customer misinformation? SAP (and other „enterprise sales“ players) sold to CIO with „account relationships“. Then software is shoved down the throat of business users.
- AmericanChopper 4y agoI once consulted for a place that had one seperate ERP for each acquisition or merger they’d had in the past few decades. They all had projects in progress to decommission/merge them back down to one, but they were never able to turn a single one of them off.
- theshrike79 4y agoYou can customise it, but you do need to stay within limits. If you go too far, a SAP version upgrade is no longer a drop-in operation, but rather a year long project of porting all your changes to the new version. If you stay as vanilla as possible, upgrades are a lot easier.
- taway19920706 4y agoThis. SAP has no restrictions on how much you customise it - you can customise and extend to your heart's content. The problems come during upgrade - SAP has very mature tooling to manage upgrades but a customer who has veered too far from standard will need to rework their customisations to fit the new version. Many many customers have been burned by this over the years - being too trigger happy and customising/building their own extensions rather than using the out-the-box functionality. Packaged software exists for a reason, don't use it like a PaaS to built your own solutions. SAP is now pushing customers to "keep the core clean" and stick to standard as much as possible, which is definitely a move in the right direction.
- kazinator 4y agoFun with your comment: s/SAP/Debian/g s/mature/so-so/ s/customer/sucker/
- taway19920706 4y agoHey, keep your hands off Debian! :P (I say this as as retired Debian developer)
- tomaaron 4y agoThis is hilarious.
- rjzzleep 4y agoIt's the same reason why Jira is so popular. CIOs recommend it to each other, because nobody wants to admit they made a mistake and that it wasn't as easy to integrate in the end after all. It's like getting a nose surgery and telling all your friends to get one as well. In most cases people look worse afterwards. It's funny to see people here defending SAP, because the way I see even the smaller shops that did bend to SAP's will ended up with much of the same problems but with less much to address them and on top of that, much like other enterprise grade ERPs they had to spend a lot of money on infrastructure to process only a few RPS while struggling with high availability.
- tut-urut-utut 4y agoNo, Jira is popular because it's flexible. You can customize Jira to fit any process. That flexibility comes with a price tag, which is performance. SAP is a complete opposite, a truly inflexible “my way or highway” type of system.
- KptMarchewa 4y agoGoing to copy my older comment: One very large video game studio has tons of automation for Jira. Imagine someone deciding to add new weapon. The automation creates 100s of tasks for concept artists, 3d artists, animators, sound artists, software developers with complex dependencies better those. Most importantly, automation creates multiple QA steps for each element of completed work. The same exists for levels, enemies, quests and tons of other elements. I would not be surprised if a lot of studios had similar workflows.
- Matl 4y agoThat may be true for certain industries, but a lot of shops work on CRUD apps and use Jira in its fairly stock configuration. Linear or something like that could do the same job for them just fine.
- KptMarchewa 4y ago
- Phurist 4y agoHow to say that you lack experience running a successful business without saying you lack experience running a successful business.
- rvba 4y agoThe competition is generally worse. I tell it as someone who saw few different products offered by the competition. This doesn't mean that SAP is good. Also this doesn't mean that there isn't space for someone who could do it better by starting with a clean state (what sounds easy, but is actually very, very hard to pull off). First you should know that the market for ERP systems is very wide. There are LOTS of various companies that offer their ERP systems. Also a lot of those "ERP" systems are "enterprise resource planning" in name only. The smaller ones often are focused on one thing only: bookkeeping, warehousing, invoicing, purchase management, salary calculation. Often they started as something that does one thing (usually: bookkeeping) and then more and more stuff was added on top -> as requested by customers. There was this old theory, that at some point each peace of popular software becomes so big that it can handle email. And guess what, SAP can send emails too. Tons of those other ERP systems can send email too. Different thing is if they really should. The smaller ERP solutions often dont scale well (they cannot handle too many "things" e.g. millions of invoices, millions inventory SKUs, 20 different countries..) or are too simple / not flexible enough to actually customize. With those smaller systems, you can understand them (e.g. the whole system has few thousand tables), but this comes at the surprising cost of lower flexibility, because in order to handle the complicated business cases you have to recreate the complicated logic as well. SAP was used by so many big companies that a lot of the complicated logic is already there in its 'standard' (and as others pointed out: if you want your life easy, you should adjust your company to the standard, instead of trying to customize). Different thing is that you need a consultant to even know that those features exist. And as you can imagine SAP is so big that even the consultants can only focus on a certain part. [also I personally knew a situation where consultants wrote a custom extension for something that was available in standard -> they didn't know standard SAP standard well enough..] I kind of disagree that a typical configuration of SAP has 20 000 tables. The ones I knew usually had 50 000+ and those were just few "modules". Using SAP terminology you have modules like FI (finance: bookkeeping), CO (controlling - financial reporting), FI-AA (asset accounting -> think list of assets the company owns), SD (sales & distribtion - e.g. issuing invoices). There are lots of those modules and usually the consultants know "their" module + the finance module. Because at the end the FI (finance) and CO (controlling) modules are always on the top -> you want to register the things that happen in financial ledgers and make some reports out of it. For example: the consultant that sets up invoicing for you will know SD module (to set up the actual layout of invoices - how it looks like when you print it, the process flow etc) and FI (to help you configure that the invoices land on correct sales accounts). Someone else sets up the PM (plant management) module. Someone else handles access rights / authorization (small ERP systems often struggle at this part - and often "everyone can see everything" what is a big no-no in times of GDPR and just batshit insane when we think about corporate espionage). A lot of complication with SAP comes from the fact that it can do things as per laws of different countries (please note: not necessarily out of the box, usually you need configurations and external add-ons). For example if you want the taxes calculated by the system for USA, Germany, Poland and Japan - then SAP can do it for you. The system (after painful configuration) will calculate the sales tax / VAT tax and also provide data to calculate CIT (I am not sure if any company calculates corporate income tax out of the box, I always saw an expert from SAP to some data/warehouse and a magic Excel file on top). Also laws change all the time, so system has to change all the time. Even the basic stuff gets complicated once you need to handle it at scale + for many countries e.g. you want to issue the invoice, you need to use the correct tax type (e.g. VAT in Europe), the correct tax rate (e.g. like 50++ rates per each country), then you need to handle things like invoice corrections, exchange rates, handling exchange rate differences, withholding tax. And it is like this with >everything<. Every business activity that can be handled can be cancelled/reversed, what makes the logic of everything convoluted (e.g. when you reverse the invoice 3 weeks after it happened you need to use the correct exchange rate as per each country's law), because the bigger the company the more probable is that they will do something that shouldnt happen. SAP can handle this at scale. Other thing is that there is a big moat. The process of setting up any ERP system takes at least months and generally years. The article explained it quite well. You need to migrate data to the system, check if it works, see if can handle your cases, train the users (the training part often is ignored, so lots of features are not used). Often the companies also dont have anyone to help with customization AFTER the migration, what is another big problem. It is public knowledge that more than 50% of ERP implementations fail. There is also some degree of economy of scale. People who used SAP at one company have it easier to use at another. Although devil is in the configuration details. But at least they dont need to relearn the interface (that is awful in most ERP systems). In a typical big company at some point you need to have your own in-house ERP administrators, who outsource parts of requirements to external sources and deal with the easier stuff on its own. The smaller systems are often inflexible for that - source code is not available. Different thing is if you want to handle the SAP source code with comments in German (yes, that's how it looks in some places; table and column names are German abbreviations too). Speaking about incumbents: I read that there is some "magic" open ERP system (forgot its name - maybe it was OpenERP), that has just under 20 tables that supposedly can handle everything, but I never looked much into it. Perhaps 20 tables with 1000+ columns each (maybe still better than 50 000 tables with 10 columns each). And to end it: ERP systems are like elephants. Once you set it up and it "kind of" works, then you dont want to touch it. You dont want another few years spent putting lots of effort on your tooling. You want to deal with actual core business part of the business. The article also pointed it out -> the quote that in some markets being able to implement the ERP better than the competition is the competitive edge is quite true. There are lots of companies with very very bad ERP, or multiple systems that dont talk with each other. What makes reporting hell. (not that reporting in SAP is easy) And without good reporting, the decisions are taken too late, or not at all.
- TacticalCoder 4y ago> Why is SAP still in business? Is it solely customer misinformation? The lock-in is huger than huge. I don't think a single company on earth managed the art of locking in customers as well as SAP. Does anyone ever drop SAP? I don't know: the cases have to be exceptionally rare. It's a racket. Highway robbery. This kind of behavior brings in a lot of revenues. I personally do think the sale to the customer is complete and total misinformation. And once you've fallen for it, there's no way out.
- appleflaxen 4y agoWhat are the fundamentals of "SAP processes"? Can you provide any detail?
- appleflaxen 4y agoThis was in the case study linked elsewhere: > Lidl based its inventory management system on purchase prices. The standard SAP for retail software uses retail prices, and fearing the group could lose a competitive edge by compromising, Lidl declined to change, so the software was instead adapted. https://www.henricodolfing.com/2020/05/case-study-lidl-sap-debacle.html https://www.henricodolfing.com/2020/05/case-study-lidl-sap-d...
- ReptileMan 4y agoThe main is to hire hordes of extremely expensive sap consultants
- sascha_sl 4y agoI've known one place that did bend SAP to their will, and they were stuck on a soon to lose support version despite having almost 100 SAP developers on staff (almost half their entire IT)
- tut-urut-utut 4y agoWith 100 mildly competent developers on staff (although not with SAP developers) a company can develop in house everything they need to run a business in a period of time that is shorter than what is needed for a typical "SAP adjustment".
- panick21_ 4y agoIt really boggles the mind. What can be so complex that you can not do it in 300 person years of development time plus the cost of SAP. Specially with the tools that exist in open source. Amazing databases, data modeling systems, libraries to integrate into literally everything. It think the bigger problem might actually be to define the process you want to implement. What are the specifications, what of your existing system is actually needed and what isn't. Rather then the actual implementation of those processes in some digital process. I have a friend who work himself up from worker in a warehouse to team leader and now SAP something something manager. And from the story he tells me I am mostly constantly confused. The whole environment feels incredibly foreign.
- mopsi 4y ago> It really boggles the mind. What can be so complex that you can not do it in 300 person years of development time plus the cost of SAP. Build a inventory planning and tracking system for a company that operates in every country in the world and has to issue and receive invoices, customs documents, waybills etc in hundreds of formats, currencies, languages and accounting standards. And you are right that the biggest problem is definining processes and data types. Whatever waybill system a 100-head HN Rust and JS crack commando comes up with, you can rest assured that there's some authority somewhere that wants an item displayed differently, so you either patch this and many other edge cases until your codes becomes an unworkable spaghetti, or you go back to the drawing board countless times and ship nothing, or you outsource it to SAP and the likes who have spent decades coming up with a working solution (even if it's not that elegant).
- suction 4y agoIsn't it the most rational thing to assume that a company that is extremely experienced and successful at analyzing business processes and digitalising them will know better than any newcomer with less resources and less experience who operates mainly on "we're disrupting for the sake of it" swagger? Telling SAP that you want them to change their ways to accommodate your brilliant idea is akin to a layman telling a brain surgeon how he wants his surgery done.
- wheels 4y agoAgain, as I noted elsewhere in the thread, I worked in R&D at SAP for 4 years (16 years ago), but I have no deep love for it. But I do have some understanding of where it fits in the landscape. What you've said is absolutely true, but it's mostly a feature, not a bug. Once you get big enough to need SAP, it's actually useful to put your business processes on a standardized platform. It's painful, always mind bendingly expensive and often fails. But few companies want to be innovative in their business processes. It's actually better to move to "the standard" since it makes processes more understandable across different ginormacorps, which is useful for the upper management sorts that tend to move between them. There's virtually no competitive advantage to having unique business processes. There are many folks that even will say that that's the advantage of moving to SAP is it makes the internal mechanics of the company work a lot like every other giant company.
- tut-urut-utut 4y agoI have to disagree here strongly. You are just saying, that a company that became big enough, so it can afford SAP, should drop their way of doing business, drop the processes that made it big in the first place and go through a painful and expensive process where it will become just another SAP shop, with zero competitive advantage. Telling that losing your uniqueness and being like “everyone else” will actually become your competitive advantage is something that only SAP can come up with. If you already grew big, you won't grow bigger by adopting SAP. You can stagnate at best, as shown a million times in the real world. Companies that still want to grow just don't use SAP. Period.
- wheels 4y agoSorry, but that's just not borne out by data: almost all of the Fortune 500 companies use SAP (something like 80-90%; probably the rest use Oracle, which isn't significantly less painful to move to).
- primax 4y agoThe average age of companies on the S&P is 18. That's just about long enough to start being killed by SAP
- cromka 4y ago> In April 2017, SAP even awarded Lidl a prize for being one of their best customers. I found this hilarious.
- mkl95 4y agoIt's even more hilarious after you read this https://news.ycombinator.com/item?id=30853778 https://news.ycombinator.com/item?id=30853778
- baxtr 4y agoHundreds of millions is actually the lower end of the spectrum. For most big companies it’s usually above the billion USD mark.
- markmark 4y agoMy first job out of college in the late 90s was in a large division of a larger company (about 80k employees at the time) that was being spun off in the hopes of selling it. As they were going to be made a stand-alone company they needed their own ERP etc and went with SAP. After two years and $50M the dotcom crash killed any chance of selling the new company and it was absorbed back into the mother ship and SAP was thrown away.
- gHA5 4y agoThat article says Lidl/Schwarz has abandonded SAP and gone back to their custom system. That surprises me because I have a friend who does SAP consulting for them.
- panick21_ 4y agoUsually those processes end with having both running.
- jiggawatts 4y agoReminds me of large government departments where some idiot in the IT architecture team says: "Woah there buddy! Why do you think it's safe to assume that Microsoft Office is what we're going to use? What if we decide to use Open Office?" That's maybe one or two words away from a literal conversation in a huge meeting with dozens of high-level IT staff overseeing an org with 30K staff and a petabyte of existing Microsoft Office documents. Boggles the mind that some people think this way, but they do. Like... imagine an electrician wiring a new office building having a debate about which frequency and voltage to use. "Don't make assumptions!"
- colonwqbang 4y agoThere have been tons of innovation in the field of electrical engineering since the standard voltages and frequencies were fixed. New installations are made to a better standard than older ones, while still maintaining interoperability. They don't blindly stick to the status quo without ever questioning if there's a more cost-efficient option like big-corp IT departments tend to do.
- jiggawatts 4y agoSo if you were building a 40-storey high rise office building and the sparky you hired decided to install electrical outlets that were all 400 Volts and 30 Hz, you'd be fine with that? "Why stick to the status quo?"
- achenet 4y agoI think a better analogy would if the sparky decided to use a new type of wire with better conduction than standard copper. As GP comment said, there has been innovation in the electrical engineering space that maintains backward compatibility. So if Open/LibreOffice could actual deal well with MS Office formats, for example, whilst removing the annoying bits (cost, telemetery, UI[0]), then yes, it might be wise to move on from the status quo. [0] in practice I don't think the OpenOffice UI is better than the MS Office, but in theory some people could prefer it
- 4y ago
- tootie 4y agoI feel like you could search and replace "SAP" with "Salesforce" in this thread and everything would still be perfectly accurate.