What mistakes do orgs commonly make when implementing ERP?

Enterprise Resource Planning (ERP)Enterprise ApplicationsSolutions Architecture
2.3k views5 Comments
Director of Product Engineering & IT in Software, 51 - 200 employees
Not getting company side buy in. Installing comphrensive systems like this requires full buy in by th e primary stakeholders in each department that will be using it. When these projects fail
It’s because departments don’t give accurate requirements / input to the solution to ensure it’s configured correctly and then when it rolls out they refuse to change their ways to adapt to the ERP. 
3
VP of IT in Media, 10,001+ employees
Bringing in too much or not enough historical data
1
PMO Director in Insurance (except health), 201 - 500 employees
Allowing too many requirements and scope creep.  It needs to be a staged roll-out and communication regarding expectations. 
   
1
Chief Executive Officer in Software, 51 - 200 employees
Inadequate Testing and Quality Assurance: Insufficient testing and quality assurance processes can lead to system glitches, functional gaps, and performance issues. Thorough testing, including user acceptance testing, is essential to ensure that the ERP system functions as intended and meets the organization's requirements.
1
CIO, Self-employed
Don’t previous review their processes and orchestration of the activities, adapting, as much as possible, their business routines to the ERP’s best practices.
Moreover joining the master data management in a unique shared service center that will take care of the main data files, cleaning, consolidating, unifying, verifying and assuring the accuracy of those records is another milestone a lot of organizations fail to do.

Content you might like

Conversational CRM is lacking in most CRM applications.

Customer Relationship Management (CRM)Enterprise ApplicationsVendor/Product Assessment

Strongly agree6%

Agree70%

Neutral17%

Disagree3%

Strongly disagree0%

Unsure (explain in the comments)0%


408 PARTICIPANTS
1.3k views1 Upvote

I'm seeking advice regarding a strategy for handling inactive accounts within directories. An auditor has requested a report on enabled accounts that haven't been logged in for over 90 days. While there are various approaches to solve this, I'm uncertain about the appropriate platform. Should this fall under the realm of a log/reporting, making it suitable for a SIEM solution (consolidating logs to generate a report)? Or does it delve deeper into an IAM concern (analyzing user accounts for inactivity and taking action)? Has anyone encountered a similar reporting or compliance scenario? I'm in search of guidance to make an informed decision on whether to approach this from a reporting angle or a more comprehensive IAM perspective. Your insights could serve as a deciding factor/tiebreaker to help me choose the most strategic path to address this scenario.

Enterprise ArchitectureSolutions ArchitectureActive Directory+3 more
Director of IT in Manufacturing, 5,001 - 10,000 employees
Actually I use ISO 27001 framework and I create user access management policy , in this policy you can use access privilege matrix to manage all user in your company, so far we never have issues when we use this policy
Read More Comments
1.9k views1 Upvote2 Comments

How important is it for an ERP software vendor to understand the nuances of your industry?

Enterprise ApplicationsVendor/Product Assessment

Very important22%

Important75%

Not important2%

Unsure0%


163 PARTICIPANTS
490 views

We are about to embark on ECC to S/4HANA migration, and SAP is pushing us strongly towards RISE. They delivered a business case for us, and they are presenting cases of successful RISE migrations. On the other hand, our experience with handing over any support or project execution to SAP (e.g. BTP or SAC Cloud Foundry migrations, Success Factors and Ariba configurations) in the last 2-3 years has been very negative. Can anyone with hands-on experience with RISE share their journey? Contrary to what SAP is showing us, I am interested in challenges and complications that may arise in project execution, particularly in the quality of support they provide during the migration and in BAU. 

Enterprise Resource Planning (ERP)Enterprise ApplicationsIntegrations+17 more
2.5k views3 Upvotes

What are some best practices, including those commonly used in other companies, for managing contingent workers, especially in terms of tracking and verifying time and pay rates for maintenance and construction work? This includes considerations like tracking level (project vs. task), accuracy verification, using data sources (e.g., security card swipes, GPS tracking), and the digital/self-service aspect (what's the difference on mobile or a web app vs. spreadsheet or paper-based). 

Peer InsightsProcurementEnterprise Resource Planning (ERP)+1 more
5.7k views4 Upvotes