Addressing ERP Reliability Challenges for Managers

ERP projects keep failing. But not for the reasons you think. In my 25 years of ERP implementations, I’ve seen 50+ projects fail miserably. Here are 8 challenges no one warns you about (and how to overcome them): 1. 𝐀𝐫𝐭𝐢𝐜𝐮𝐥𝐚𝐭𝐢𝐧𝐠 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐌𝐨𝐝𝐞𝐥𝐬 𝐭𝐨 𝐒𝐈𝐬 Most manufacturers assume their SI “gets it.” They don’t. Translating your ops into tech isn’t their job. It’s yours! → Create a “business blueprint” document that outlines critical processes, KPIs, and unique workflows before the SI even starts. 2. 𝐓𝐡𝐞 𝐓𝐞𝐚𝐦 𝐐𝐮𝐚𝐥𝐢𝐭𝐲 𝐯𝐬. 𝐐𝐮𝐚𝐧𝐭𝐢𝐭𝐲 𝐃𝐢𝐥𝐞𝐦𝐦𝐚 Big budgets don’t mean big results. → Instead of bloating your team, invest in a few A+ players who know your systems inside out. → A lean, sharp team will outpace a large, disconnected one every time. 3. 𝐅𝐮𝐭𝐮𝐫𝐞-𝐏𝐫𝐨𝐨𝐟𝐢𝐧𝐠 𝐟𝐨𝐫 𝐂𝐥𝐨𝐮𝐝 The ERP landscape is moving to the cloud, and ignoring this shift is risky. → During vendor selection, evaluate the scalability and adaptability of their cloud solutions. → Focus on modular architectures that can evolve with your business rather than locking into rigid legacy systems. 4. 𝐂𝐡𝐚𝐧𝐠𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐁𝐥𝐢𝐧𝐝 𝐒𝐩𝐨𝐭𝐬 Resistance to change isn’t just inevitable—it’s predictable. → Don’t rely on generic training sessions. Tailor change management initiatives by team and role. → Invest in “process champions” from each department to act as internal advocates and troubleshooters. 5. 𝐃𝐚𝐭𝐚 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 Dirty data leads to bad decisions. → Start cleansing and validating your data before the project officially kicks off. → Run pilot tests on smaller datasets to identify issues early. → Make data governance an ongoing effort, not a one-time task. 6. 𝐔𝐀𝐓 (𝐔𝐬𝐞𝐫 𝐀𝐜𝐜𝐞𝐩𝐭𝐚𝐧𝐜𝐞 𝐓𝐞𝐬𝐭𝐢𝐧𝐠) 𝐌𝐢𝐬𝐬𝐭𝐞𝐩𝐬 Most teams treat UAT as a box-checking exercise. It’s not. → Design UAT with two phases: (1) functional testing to validate individual workflows, and (2) end-to-end testing to uncover interdepartmental gaps. → Simulate edge cases to prepare for real-world scenarios. 7. 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 𝐓𝐞𝐬𝐭𝐢𝐧𝐠 𝐔𝐧𝐝𝐞𝐫 𝐏𝐫𝐞𝐬𝐬𝐮𝐫𝐞 ERP systems can buckle under real-world transaction volumes. → Include stress tests in your performance testing phase to simulate peak loads. → Ensure you test in a near-production environment, not an idealized sandbox. 8. 𝐏𝐨𝐬𝐭-𝐆𝐨-𝐋𝐢𝐯𝐞 𝐂𝐡𝐚𝐨𝐬 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 Most companies think the job ends at go-live. It doesn’t. → Implement a stabilization phase, typically 3-6 months, where a dedicated team handles issues, monitors performance, and fine-tunes processes. → Pre-define escalation paths for quick resolution of critical problems. ERP implementation isn’t just a tech project; it’s an organizational transformation. What’s been your toughest ERP challenge? Let’s discuss below. Follow Shobha Moni to get the best out of your favourite ERP systems.

Don’t confuse deploying ERP with improving capability. This remains one of the most damaging misconceptions in ERP programmes. Nowhere is it more obvious than in supply chain, planning, scheduling, inventory management and master data — the exact areas where capability gaps do the most harm. ERP deployment gives you structure, transactions, and visibility. It does not give you competence, discipline, or better decision-making. But many leadership teams still assume that rolling out “standard processes” and providing user training sessions will automatically improve plan stability, lead times, stock accuracy and customer service. It won’t. If planners struggle to interpret demand, update parameters, or challenge constraints today, they won’t magically improve because the UI is new. If scheduling rules are unclear or regularly overridden, MRP or APS will only generate more sophisticated noise. If master data governance is weak, the new system won’t tidy it up for you — it will just expose the mess, loudly and publicly. In these situations, the ERP doesn’t fail; it simply reveals the capabilities the organisation never built. The uncomfortable truth: capability uplift is behavioural, not technical. It requires knowledge and understanding, clarity of accountability, consistent decision rights, stable and simplified processes, and a performance culture that reinforces discipline every single day. ERP can support that, but it cannot create it. If you actually want capability uplift, not just deployment, start here: 1. Define the capabilities you need, not just the system you’re buying. What does “good planning” or “good inventory management” look like? What skills, knowledge, decisions and behaviours underpin it? 2. Put real owners in place for planning, scheduling, inventory and master data. Ownership means authority, not administration. No uplift happens without it. 3. Simplify the processes before you digitalise them. If the current process is unstable or unclear, ERP will expose that instability. 4. Invest in skills, not just training. Teach planners, schedulers and analysts why they’re doing things, and, at least, expose them to the underlying principles, not just which buttons to press.  5. Build a performance framework that rewards consistency and early correction. KPIs, accountability and governance must reinforce the behaviours you want long after go-live. 6. Treat post-go-live as the start of capability building, not the end of the project. Most organisations pull resources away just as the real work begins. ERP can absolutely enable capability uplift — but only if you are willing to build the capabilities the ERP depends on. Without that, all you’re doing is digitising old habits and giving operational problems a faster route to spread. So, are you deploying a system, or are you actually building the capability that makes the system worth having? #clouderp #MRP #Supplychainmanagement #operations #planning #scheduling #ERP

Is your company planning to shutdown, rip-replace, sunset, or change JD Edwards to any other ERP on the market? Yes? Think twice. What if the problem isn't in the system, but in the process, or even more common: the people? Being frankly here: in almost 25 years of ERP there were not a single customer I worked that didn't use SQL to fix issues in Production on the database. This is a such common practice. But, at the end of the day, what causes such action? Are the processes running in harmony? Are files being detected as already processed to avoid duplication? Are the files being moved to another backup directory? Are you still using files instead of researching a REST connector to get real-time information? Is JD Edwards being used only as a data repository, with 300 other satellite systems plugged in while the financial engine is running? Is your company using high customized applications, batches, and work on a reactive way, by fixing errors when the supplier calls you about a payment that should be processed last month? Is your company paying late fees due to delays in processes, or not getting credits because there's nobody to sign-in to the system and click an option and submit it? Does your system grown organically in a web (always messy) of servers, services, workstations, VMs, without a proper naming convention, without any care? Are you still seeing the "Not Secure" when you open your ERP whether in your network or outside (that's even worse). I'm not even mentioning the internal factors like proper user administration, security, and segregation of duties, making it prone not to audits, but fraud. Sometimes, it's easier to say that's ERP's fault. The ERP isn't "modern enough", or "a Cloud solution" would be much better. Sometimes is easier to blame the system. But there's hope. There are ways to change and reverse every single of these factors - which I think you can identify yourself. With the proper focus, you can change JD Edwards from a reactive system to a proactive approach. Start by rethinking your operations. Start by upgrading, then divide and conquer. Get your best resources and build an innovation team. I'm not saying about AI or Blockchain or shiny tech. No. I'm talking about retiring customizations in apps by using Logic Extensions and Form Extensions on top of a Vanilla application. Did you try the Vanilla process in the latest release? That may have already the fix of your customization. Handling files? I bet you can find REST web services from many providers, so you can skip those. Dealing with EDI? Look for JSON. Running BSSV? Convert it to Orchestrator. Paying for third party schedules? Use the Orchestrator Scheduler. Need a friendly UI, build an Orchestration, use Gen AI to build a simple UI/UX and deploy it as an E1 Page. These are simple actions that if applied, it can change not only the perception of a system, but its efficiency, user adoption and user engagement. Need more advice? Let's talk! #jde

𝗧𝗵𝗲 𝗖𝗜𝗢 𝘄𝗵𝗼 𝗸𝗶𝗹𝗹𝗲𝗱 𝗮 $𝟭𝟮𝗠 𝗘𝗥𝗣 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘄𝗮𝘀𝗻'𝘁 𝗶𝗻𝗰𝗼𝗺𝗽𝗲𝘁𝗲𝗻𝘁. 𝗛𝗲 𝘄𝗮𝘀 𝗷𝘂𝘀𝘁... 𝗯𝘂𝘀𝘆. A few months ago, I watched a manufacturing CIO explain to his board why their Oracle implementation was 4+ months behind schedule... "I've been integrating systems from our recent acquisitions, and dealing with critical bugs in our technology product. The ERP team has been handling things." The "ERP team" was an inexperienced team of business stakeholders making million-dollar decisions. Here's how the timeline usually plays out: Week 1-12: Executive engagement starts strong... CIO attends steering meetings, asks good questions, makes decisive calls on scope disputes. Week 13-28: Business crises emerge. Acquisition opportunity. Major customer complaint. Supply chain fire drill. ERP meetings get rescheduled or delegated. Week 29-52: Project team is now making architectural decisions that will define the next decade of business operations... 𝗪𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗽𝗲𝗿𝘀𝗼𝗻 𝘄𝗵𝗼 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝘀 𝘁𝗵𝗲 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆. The result? Technical success, business failure. I've seen this exact pattern destroy millions in projected ROI that companies expected from their ERP upgrade... Not because the technology failed... Because 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗮𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻 𝗴𝗼𝘁 𝘀𝗽𝗹𝗶𝘁 𝗮𝘁 𝘁𝗵𝗲 𝘄𝗼𝗿𝘀𝘁 𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲 𝗺𝗼𝗺𝗲𝗻𝘁. Here are the three decisions that can't be delegated: → Integration vs. customization trade-offs (affects scalability for 10+ years) → Data migration scope and quality standards (determines operational reliability) → Change management investment levels (drives user adoption and ROI) When these decisions get pushed down to project managers or business teams, you get systems that work perfectly fine... But for problems you don't actually have. 𝗛𝗲𝗿𝗲'𝘀 𝘄𝗵𝗮𝘁 𝘀𝘂𝗰𝗰𝗲𝘀𝘀𝗳𝘂𝗹 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗹𝗼𝗼𝗸 𝗹𝗶𝗸𝗲: The CIO treats ERP leadership like merger integration...  • Non-negotiable calendar priority  • Weekly deep-dives  • Personal accountability for outcomes Because that's exactly what it is: 𝘆𝗼𝘂'𝗿𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 𝗵𝗼𝘄 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘄𝗼𝗿𝗸𝘀 𝗮𝘁 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹 𝗹𝗲𝘃𝗲𝗹. 𝘌𝘹𝘦𝘤𝘶𝘵𝘪𝘷𝘦 𝘢𝘵𝘵𝘦𝘯𝘵𝘪𝘰𝘯 𝘥𝘶𝘳𝘪𝘯𝘨 𝘌𝘙𝘗 𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵𝘢𝘵𝘪𝘰𝘯𝘴 𝘪𝘴 𝘵𝘩𝘦 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘤𝘦 𝘣𝘦𝘵𝘸𝘦𝘦𝘯 𝘥𝘪𝘨𝘪𝘵𝘢𝘭 𝘵𝘳𝘢𝘯𝘴𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯 𝘢𝘯𝘥 𝘦𝘹𝘱𝘦𝘯𝘴𝘪𝘷𝘦 𝘥𝘪𝘨𝘪𝘵𝘢𝘭 𝘥𝘦𝘤𝘰𝘳𝘢𝘵𝘪𝘰𝘯. 𝘐𝘧 𝘺𝘰𝘶𝘳 𝘭𝘦𝘢𝘥𝘦𝘳𝘴 𝘢𝘳𝘦 𝘴𝘵𝘳𝘦𝘵𝘤𝘩𝘦𝘥 𝘵𝘰𝘰 𝘵𝘩𝘪𝘯 𝘵𝘰 𝘭𝘦𝘢𝘥 𝘵𝘩𝘦 𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵𝘢𝘵𝘪𝘰𝘯, 𝘺𝘰𝘶'𝘳𝘦 𝘯𝘰𝘵 𝘳𝘦𝘢𝘥𝘺 𝘵𝘰 𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵. How are you structuring executive accountability for your current implementation?

You have 50 supply chain dashboards, but your line still stopped today because a supplier was 3 days late and nobody knew. Dashboards are dead. By the time your planners log in, refresh the data, and realize a critical component is stuck in transit, the shift is already ruined. A mid-market manufacturer came to us recently with this exact nightmare. They had spent a fortune on a "modern data stack." They had spended hours building Power BI charts tracking inbound freight. But when a Tier 2 supplier missed a delivery window, nobody noticed until the floor operators stared at an empty bin. They spent the next four hours firefighting, re-routing lines, and authorizing premium air freight. When I asked the CIO why the dashboard didn't help, he said: "Nobody checks the inbound freight dashboard until Friday. The shortage happened on Tuesday." This is the reality for 90% of asset-heavy companies. You don't need another dashboard. You need a nervous system. Data is useless if doesn't change behavior. Here is how smart supply chains are redesigning their architecture: 1. Decouple the ERP from Reality     Your ERP assumes everything is fine until a human tells it otherwise. Stop relying on manual status updates. Map the exact gap between when a supplier misses a scan and when your planner finds out. That time gap is where your margin dies.     2. Define the Exception     Stop tracking what goes right. Only track what goes wrong. Define the exact tolerance for latency. If a supplier SLA is 48 hours and they hit 49 hours without an ASN scan, that is an exception. 3. Push the Alert to the Floor     Data must find the user, not the other way around. When an exception occurs, trigger an automated alert directly to the planner's workflow or the plant manager's screen. If a supplier slips, your planner sees it in hours, not on the day the line stops.     4. Tie the Exception to the P&L     Every open PO should carry a risk score, based on supplier history, lead time, and current status. Your planner should walk in every morning knowing which suppliers are likely to cause problems today. Not last week The alert shouldn't say "Truck is late." It should say "Line 4 will starve at 2 PM, risking $40k in unabsorbed labor."     If your data doesn't trigger an action, it is just expensive noise. The companies winning today aren't buying more BI licenses. They are closing the gap between data collection and operational action.

Your ERP didn’t fail because of integration issues. Your ERP didn’t fail because of missing features. Your ERP failed because your people didn’t trust it. Your finance team didn’t trust the numbers. Your ops team didn’t trust the workflows. Your leadership didn’t trust the reports. Most ERP issues aren’t technical. They’re about trust. Here’s what happens when trust breaks down: - Adoption drops to below 40% - Reporting becomes fragmented - Manual workarounds creep back in - Teams build shadow systems in Excel And, then… Blame shifts from “process” -> “platform.” And that’s when your $XX million system becomes a $XX million mistake. But here’s how real trust is built: 1/ Involve users from day 1, not just after go-live 2/ Validate and clean data, trust starts with accuracy 3/ Reinforce quick wins, show the value early and often 4/ Provide hands-on training, and confidence drives adoption 5/  Keep communication open, trust grows when feedback flows ERP transformation is not just about the system It’s about the people using it Fix the trust And the tech will perform Agree?

ERP data will never be clean. And that’s the truth leaders must accept. Leaders keep chasing the fantasy of a perfect ERP. But here’s the reality: 1/. People enter data. People make mistakes. 2/. Processes evolve. Fields change. 3/. Mergers, acquisitions, and reorganisations bring chaos. 4/. Legacy systems leave scars in every dataset. No amount of dashboards, audits, or consultants will deliver “flawless ERP data.” So what must leaders do? Shift mindset. Stop chasing perfect data. Start building for resilient data. That means: 1/. Designing systems that can tolerate noise. 2/. Adding controls to detect and correct bias early. 3/. Creating governance that evolves with operations. 4/. Training teams to question anomalies instead of ignoring them. The strongest enterprises aren’t those with clean ERPs. They’re those who accept the mess and build intelligence around it. Because in the AI era, resilience beats perfection. Always. 👉 Leaders, stop chasing “clean ERP data.” Start investing in governed, resilient, and trustworthy systems. What’s your biggest challenge with ERP data, accuracy, governance, or adaptability?

Most ERP rollouts fail—not because of tech, but hidden roadblocks nobody talks about. Our blueprint for breaking through them ↓ 1. Change Resistance: People fear the unknown. Address concerns early. Involve key stakeholders from day one. Communicate benefits clearly and consistently. 2. Data Migration Nightmares: Clean your data before migration. Map fields meticulously. Test, test, and test again. 3. Customization Creep: Stick to out-of-the-box features when possible. Evaluate each customization request critically. Remember: More customization = More complexity. 4. Training Oversight: Invest heavily in user training. Create role-specific guides. Offer ongoing support post-launch. 5. Scope Expansion: Define clear project boundaries. Use a phased approach. Resist the temptation to add "just one more thing." 6. Leadership Misalignment: Secure executive buy-in early. Establish a clear project champion. Keep leadership engaged throughout the process. 7. Resource Underestimation: Plan for the long haul. Budget for unexpected costs. Don't skimp on expert consultants. Navigating these roadblocks requires experience. We've guided countless businesses through successful ERP implementations. Take the first step toward transforming your ERP rollout into a game-changing success. Let's talk.

Continue.. 4. System-Generated Logs or Audit Trails Definition: System logs that automatically record transactions, changes, or accesses in the environment. Challenges: Volume and complexity of logs. Difficult to extract complete logs without proper tooling. How to Gain Comfort: Log Aggregation and Monitoring Tools: Use log aggregation tools like Splunk or Graylog to capture all logs for a complete record. Sampling and Reconciliation: Perform sampling from the log data, ensuring there’s no break in data flow or missing entries. Timestamp Verification: Validate that all logs have consistent timestamps without gaps that might indicate incomplete population. 5. Change Management Systems Definition: Systems used to manage changes, which often interface with other systems (e.g., configuration management databases, CMDB). Challenges: Incomplete tracking of changes. Data mismatch between systems. How to Gain Comfort: Integration Testing: Ensure that the system is properly integrated with others and changes flow smoothly across environments. Change Reconciliation: Reconcile the list of changes in the system with actual deployments or configuration changes in the environment. Review of Process Controls: Validate that process controls are in place for tracking all changes end-to-end, from initiation to closure. 6. ERP Systems (e.g., SAP, Oracle) Definition: Large-scale systems used for financial or operational processes. Challenges: Complex and customized reporting modules. Risks from user access or configuration errors. How to Gain Comfort: Report Logic Validation: Validate the logic behind any system-generated reports, ensuring they pull data from the correct tables with appropriate filtering. Control Testing: Test automated controls in the system to ensure reports are generated consistently and accurately. Access and Configuration Review: Review user roles and system configuration to ensure that no unauthorized changes to reports can occur. 7. Database Queries Definition: Populations directly extracted from underlying databases using SQL queries or similar methods. Challenges: Complexity of database structures and risks from query errors. Risk of extracting incorrect or partial data. How to Gain Comfort: Query Review: Have an independent review of the SQL queries used to extract the population to ensure accuracy. Direct Data Sampling: Cross-check the extracted population with raw data from the database tables through random sampling. Field Mappings: Ensure proper mapping between database fields and extracted report fields, to avoid data discrepancies. Techniques to Ensure C&A: Reperformance: Reperform population extraction or run a parallel query to validate results. Reconciliation: Cross-check reports or data sources for consistency and completeness. Control Review: Review controls on report generation, user access, and data extraction. Sampling: Test sample records against source data to confirm completeness.

🚀 𝗧𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗶𝗻𝗴 𝗦𝘂𝗽𝗽𝗹𝘆 𝗖𝗵𝗮𝗶𝗻 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝗘𝗥𝗣 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻 In a global manufacturing company, we faced critical challenges affecting production, costs, and operational efficiency. Here's how I turned challenges into measurable success: 📈 𝗣𝗮𝗶𝗻 𝗣𝗼𝗶𝗻𝘁𝘀 ▪️ERP Mismatch: Poorly configured SAP data misaligned with production planning. ▪️Cost Inefficiencies: Inconsistent costs impacting COGS. ▪️Low Efficiency: Underutilized capacity, excessive labor and material usage. ▪️Production Downtime: Suboptimal sequencing increased changeover times. ▪️KPI Gaps: Lack of actionable insights from performance indicators. 📌𝗔𝗰𝘁𝗶𝗼𝗻𝘀 𝗧𝗮𝗸𝗲𝗻 📍Data Alignment: Reparameterized SAP data for accurate production planning. 📍Financial Validation: Partnered with Finance to ensure cost alignment during optimization. 📍Operational Efficiencies: Optimized production sequencing to reduce changeover times. 📍KPI Implementation: Established real-time performance tracking dashboards. 📍Governance Structure: 🔸Weekly follow-ups to monitor progress and prevent deviations. 🔸Monthly accountability reviews with extended teams and leadership to drive commitments and results. 🎯 𝗥𝗲𝘀𝘂𝗹𝘁𝘀 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝗲𝗱 ✅ Cost Reduction: 15% improvement in COGS due to streamlined processes. ✅ Efficiency Boost: 20% reduction in changeover times, increasing capacity utilization. ✅ Waste Minimization: 10% reduction in material usage and overtime labor. ✅ Improved Visibility: Actionable KPIs enabled proactive decision-making. 💡 This experience reinforced the power of data accuracy, cross-functional collaboration, and disciplined follow-up to drive measurable results in supply chain performance. When processes are optimized and aligned, the entire organization thrives. 📣 Have you ever faced challenges with misaligned data or processes in your ERP? How did you tackle them? Let’s connect to share experience. #SAP #Parameters #Data_Driven #Inefficiencies #COGS 👉 Share your thoughts or similar experiences below! 👤 Alejandro Sánchez Zavala 📞 +52 4422076495 📥 alesanzav2411@gmail.com 📱 wa.link/c44pfd Filiberto Cano