how tricks change the way it could work
Many ERP systems do what they do how they do it.
In other words, ERP systems are made up to a certain grade of completeness.
Many use cases can be fulfilled with them. But most systems have their limits. These limits can have different natures.
- missing implementations
- outdated software components
- Licensing including vendor lock in
- complicated structures
- missing concept
- fear of changing key features - never change a running system
- missing knowledge of decision maker's
These limits keep systems as they are, although many users know better ways to handle processes.
Sometimes they begin using Excel sheets to fulfill their demands, without knowing the fact, that so called shadow IT is generated.
When possible, these circumstances bring users to fund tricks. So enterprise aims can be fullfilled. These tricks have in common, that
- there has been an enterprise decision to use it
- maybe money has been invested in creating a trick
- there was no time, so the trick was the only solution
- there was no better way, because nobody could think of it
- vendors like these tricks. they are a way to earn money quickly.
Looking deeper into the use case, the trick seems to resolve, mostly ends in many use cases, that cannot be resolved because the trick is blocking.
So tricks help to solve a big problem thinking in short terms.
ERP is built for long term function. Any trick will bring additional effort:
- table overflows that have to be manually cleaned manually or via scripting solutions
- broken data consistency
- base data out of control