ERP Systems Challenges
The cluster focuses on the complexity, outdated interfaces, customization issues, integration difficulties, and high risks of implementing and using ERP systems like SAP, Odoo, and Dynamics NAV in businesses.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Many ERP systems do this and are open source, look at odoo for example
I have this quote bookmarked, about ERPS:"Most companies spend way too much time and money trying to make software work for their processes. Some of these processes haven't changed in years or even decades. Rather than customizing software to work for your processes, it's often easier to reevaluate processes around modern software."You can have your ERP customized, but you cannot have your cake and eat it (without cost). Ramping up new trading partners, onboarding new s
There is a reason why it all seems so oddly ancient. Rule number 1 - if its not broken then don't fix it. Not the usual hn mindset I know, but you only need to be involved in one bad transition between finance systems to know that it can be a huge shtstorm. Big enough to kill a company. That is why everyone is running ancient mainframe era tech and everything feels like its 10 year behind silicon valley mindset.Its all good & well on a small business scale to DIY and integrate things
At my workplace we use lots of different tools and systems. No one has access to everything because of licensing costs. SAP Business One is the main ERP but to have part numbers added to the database, engineers use a separate ticket system like Jira to instruct the finance people how to do the data entry in SAP. Code is in Gitlab. Docs are in Sharepoint. Every department has their own kingdom and manages documents in Sharepoint differently with access restrictions frustrating everyone. Some docu
Sounds more like they should get a proper ERP and/or HR system to solve this.
This comment doesnt deserve the downvotes its getting. If you ever work in an ERP system you will realize the complexity of tracking cost, inventory management (which is not just simple item, location quantity), purchasing, quotes, lead times, approval processes, BOM data structure, assembly, work orders, sales orders internal/external, etc etc. All these may boil down to basic cost account primitives but making a system that is a ledger then dismissing other solutions and saying you could
Nobody suggested rewriting Excel or even customising libre office. These projects are often ERPs which get customised to the client's requirements. Chaos and ballooning costs often follow for all the usual reasons.
Any ERP will bring you near that.
My wife was analyst in a company that was took over by international corporation. It was hell of two mismatched systems (SAP and internal oracle based system).They "solved" it so: each morning one person imported the data from both systems into huge excel spreadsheet (file had almost 100 MB), then she send the file to person that know how to correct all the duplicated and missing data in a few columns (it wasn't turing-complete process, it was heuristic, cause systems used different subdivisi
You pretty much exactly described my job.I started last year and inherited a horrific ERP system (and ancillary code for things like production scanners).They realised they needed an ERP but they where unlucky in who they got to build it, things I take for granted as simple things to do (an interactive timeline showing job start stop, per user/department in d3) has had a massive impact on how they run things (it surfaced issues around job tear down/turnover).Efficiency against