ERP Software Solutions

#Transport request failed? Don’t panic — troubleshoot smartly! Recently, I encountered a transport request failure with Return Code 12 in our SAP system. Instead of jumping into logs blindly, I followed a structured approach using user, RFC, background job, and BTC (background processing) checks — and it worked! Here’s a quick breakdown of the approach: ✅ User – Checked if the user who triggered the transport had the right authorizations such as: • S_TRANSPRT • S_RFC • S_BTCH_JOB used Tcode SU53 and SUIM. ✅ RFC – Verified RFC connections (especially TMSADM@<SID>) • Use SM59 > TMSADM@ • Run “Connection Test” and “Authorization Test” #Common Errors: • “Logon not possible (error in SAP logon)” – TMSADM is locked or password expired. • Authorization errors – use SU01 to check if TMSADM is active and not locked. #Action: • Unlock user if necessary. • Sync password from Domain Controller using STMS > Overview > Systems > Configuration > Reimport Configuration. ✅ Job – Used SM37 to review background jobs like RDDIMPDP. Use SM37 to check for jobs like: • RDDIMPDP (distributes import tasks) • TMS_BCI_START_SERVICE • Transport job started by STMS (custom-named) • Filter: • Job Name: RDD* • Status: “Canceled” • Time range: when the transport failed #Action: •Click the failed job > check Job log • Look for messages like: “Program RDDIMPDP does not exist.” • “Event RDDIMPDP not defined.” #Fix: • Ensure Program RDDIMPDP is scheduled and active via SM36. • Trigger the event manually via SM64 if needed. ✅ BTC – Monitored SM50/SM66 to see if any background processes were stuck. #What to look for: • Long-running processes in status “Running” without progress. • Short dumps in ST22 related to memory or file access. Entries like: • “Unable to write to cofile” • “Lock table overflow” #Fixes: • Free up system resources. • Increase memory or number of background work processes in RZ10. • Ensure enough disk space in /usr/sap/trans. This structured method helped isolate the issue quickly and avoid unnecessary rework. Sharing this hoping it helps others in SAP Basis or HANA administration roles!

ERP Projects Fail for Many Reasons. Ignoring Integrations is the Fastest Way to Doom One. Too often, ERP projects run over budget, take too long and fail to deliver. The culprit? Overlooked integrations. I see this mistake all the time. Companies focus on ERP functionality but forget that no system operates in isolation. Data flows, third-party systems, and automations must be planned from day one—not as an afterthought. That’s why I put together a no-nonsense whitepaper on how to make ERP integrations work instead of becoming a hidden pitfall. 5 Practical takeaways from the whitepaper: 1. Define all data flows at project kickoff – Document dependencies between systems early. Surprises later = delays & cost overruns. 2. Master data first, transactions second – Sync customers, vendors, and products first. If your master data is broken, transactions will fail. 3. Set a realistic integration timeline – Sync integration tasks with ERP rollout. If integrations are late, the entire project stalls. 4. Test with real data, not fake records – Your ERP test system should mirror production. Otherwise, the first real transaction is your actual test. 5. Make integrations visible – Use visual mapping tools to align teams, avoid assumptions, and ensure all critical systems stay connected. Get the full whitepaper here: https://lnkd.in/dfNHA9nN ERP success is not just about the ERP—it’s about how well everything connects. Integrations First. Always. #ERP #Automation #iPaaS #PMO #ProjectManagement

Before I let a CFO in Dubai sign an ERP contract, I ask 7 questions about multi-currency and FX rules. (Most vendors can’t answer even 3.) And that’s exactly why 90% of ERP finance teams end up with workarounds, Excel patches, or fire drills every month-end. Here’s what I ask every single time: (1) How does the system handle revaluation gains/losses across ledgers in real-time? (Or are you manually booking journals at month-end?) (2) Can FX rates be pulled live from central banks or is it still a static upload via CSV? (3) What happens to historical FX rates when you reopen a prior-period transaction? (4) Can you tag currency exposure by project, vendor, or contract in reporting? (5) Does multi-entity consolidation auto-adjust for intercompany FX differences? (Or do you have to “explain” the ₹6.2M gap to auditors every year?) (6) How does the ERP treat rounding off in multi-currency AP/AR aging reports? (7) Does the ERP allow dual base currencies? (say, for reporting in USD and AED natively?) If your vendor can’t answer these, walk away. Because the moment your business hits scale or enters new geographies… Your ERP won’t just fail. It’ll cost you millions in lost visibility and manual firefighting. Want the full 23-question FX audit checklist I use before every ERP project? Just comment “FX Checklist” below and I’ll send it across. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 so others can learn.

A big 4 consulting firm implemented ERP which caused a major business disruption for a client.   Top level partners in top notch suits made best promises in a beautifully crafted presentation.   The client got excited. Deal signed.   I joined the party at the SIT phase. Which could not complete.   The integration between ERP, WMS and boundary systems was failing.   SIT lasted for 3 more months. Go live data had to be pushed. But the integration still did not work.   The burn rate was insane.   Eventually the leadership decided to make it live and forced half-baked solution.   Yay! Everyone was happy until they realized what a sh*t show they were in.   Right after go live the planners and supply chain operations realized that the stock on hand in ERP, WMS, their custom system and on the shelf were all different.   They had to call the warehouse to make sure they had the right quantity of equipment.   The result: ·      All the departments started overordering to cover up for their projects. ·      2 million dollar sales were lost. No stock. Couldn’t deliver. ·      Inventory across the supply chain grew by $20M. ·      It took 18 months to stabilize the system.   Why did that happen? 1.      The vendor recently bought the WMS solution and did not yet build native integration. 2.      Poor integration between the systems. Transactions were stuck due to errors. 3.      Terrible user experience. Warehouse workers could not perform their role in a system and circumvented the restrictions. 4.      Lack of training and end user support   Want to avoid this costly mistake? Here’s what you should consider. ·      ERP can look great on a slide deck but may not necessarily fit your business ·      ERP can fit your business but not your boundary systems ·      An implementation partner can have a big brand name, but one integration architect can screw the whole thing ·      Hire an independent ERP adviser to make sure you have the right solution and partner   In summary:   Don’t trust ERP fairy tales.   Do your due diligence.   #ERP    #TheERPGuy     #ERPImplementation

"We're moving forward with another vendor." Every rep's nightmare sentence. I pressed for details. "Their approach felt more open. We actually knew what we were buying into." That stung. I'd shared: ••• Exhaustive feature documentation ••• Dozens of success stories   ••• Complete pricing breakdowns Where'd I go wrong? Days later, I got access to our competitor's sales process. The difference hit instantly: They didn't preach transparency. They lived it. Their follow-up wasn't an email avalanche. It was one collaborative hub where buyers could: ••• Monitor which stakeholders engaged with what ••• See their exact position in the evaluation journey ••• Find materials curated for their unique pain points ••• Manage internal distribution seamlessly My revelation: I was buried in PDFs. They were cultivating partnership. Next prospect, new approach: I built a shared workspace exposing EVERYTHING: → Which team members on our side viewed their data → Critical docs they'd missed → Realistic implementation expectations → Where we excel AND where we don't The buyer's response: "Finally, someone not playing games." Ink on paper in 10 days. Here's what's real: Today's buyers aren't starved for data. They're starved for authenticity. Yesterday's strategy: Bombard with polished assets that sidestep weaknesses. Tomorrow's strategy: Build transparent environments that tackle doubts directly. Your buyers know when something's off. Even when nothing is. Quit running sales like a shell game. Start running it like a glass house. You with me?

𝗘𝗥𝗣 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗮𝗿𝗲 𝗡𝗼𝘁 "𝗢𝗻𝗲 𝗮𝗻𝗱 𝗗𝗼𝗻𝗲" I had a call during the week from a CFO who shared that they were struggling with their new ERP, and it was not working well for them. Despite investing more than $1M dollars, they found themselves no better off than before they started. They were still facing issues with workflows, reporting and user adoption. The story thus far is as follows: 1️⃣ They completed an ERP Vendor and Solution Evaluation 2 years ago. 2️⃣ They selected their preferred Vendor and Solution. 3️⃣They signed Contracts with the Vendor. 4️⃣ The Vendor commenced the Implementation. 5️⃣ They went live on the new ERP system 13 months later. However, the client is still not happy with the outcome. So, what went wrong? They trusted the ERP Vendor would look after them and they probably did to a point. What they hadn’t realized is that they needed to take more responsibility for the success of the project themselves. 𝗧𝗵𝗲 𝗼𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗼𝗳 𝗮𝗻 𝗘𝗥𝗣 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗮𝗹𝘄𝗮𝘆𝘀 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝗿𝗲𝗺𝗮𝗶𝗻 𝗳𝗶𝗿𝗺𝗹𝘆 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗰𝗹𝗶𝗲𝗻𝘁. The Client needs to commit to the following resources: ✅ An involved and visibly engaged Business Sponsor. ✅ An experienced "client-sided" Project Manager. ✅ Business Process Owners who have time to be involved in the project. ✅ Regular Steering Committee Meetings to provide guidance and make decisions. ✅ Appropriate Change Management and Training. ✅ Rigorous Test Management. ✅ Ongoing support after Go-Live for future enhancements. These projects are not “𝗢𝗻𝗲 𝗮𝗻𝗱 𝗗𝗼𝗻𝗲”. They require ongoing care and attention to detail. As a CEO or CFO, don’t be pressured into going live until you are confident the system can effectively run your business. Remember, the responsibility for project success ultimately lies with the Client, rather than the Vendor. Do you have any thoughts to add? #ceo #cfo #coo #erp #erpprojects

𝗪𝗵𝘆 𝗱𝗼 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗘𝗥𝗣 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹? 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘁𝗿𝗲𝗮𝘁 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝗰𝗵, not the business transformation it truly is. Listening to my network, there seems to be a rush to complete ERP migrations, as fast as possible, with SAP S/4HANA plans driving most of it. But an ERP system is more than just an IT upgrade. It’s a chance to redesign how your business operates and build a solution architecture that supports agility and innovation. While necessary, these migrations often become redundant without proper alignment to business goals. Something, I've seen happen! Here some get rights to consider: ◉ 𝗔𝗹𝗶𝗴𝗻 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗮𝗻𝗱 𝘁𝗲𝗰𝗵 𝗴𝗼𝗮𝗹𝘀 Ensure that IT and business leaders are on the same page. ERP systems serve broader business objectives, such as innovation, improving procurement strategies, and enhancing supplier relationships. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗼𝗼𝗹𝘀. Instead of getting caught up in the technology itself, be clear about the business benefits you'd like to achieve. New ERP functionality can be of support to achieve goals like efficiency, cost reduction, and agility. ◉ 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 𝗮𝗻𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 Don't just migrate complex, outdated processes but streamline them end-to-end. Reevaluate processes for efficiency and desired outcomes. ◉ 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗶𝗻 𝘁𝗿𝗮𝗶𝗻𝗶𝗻𝗴 ERP migrations often fail due to poor user adoption. Beyond training, invest in communication & ongoing support showing the value and relevance of the system to users. ◉ 𝗜𝗻𝘃𝗼𝗹𝘃𝗲 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘁𝗲𝗮𝗺𝘀 ERP impacts every area of the business, so cross-team collaboration is essential. Involve stakeholders from finance, procurement, IT, and operations ensures the system meets everyone’s needs. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 - 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗰𝗼𝗺𝗽𝗿𝗼𝗺𝗶𝘀𝗲 An ERP system is only as good as the data it processes. Ensure that data is clean, consistent, and reliable before migration. Dirty or incomplete data is one of the biggest challenges post-go-live. ◉ 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘀𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗖𝗼𝗺𝗽𝗼𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 Choose an architecture which allows for future-proofing and integration of new features, scalability and integration. Business models evolve, and your ERP must evolve with them." ◉ 𝗦𝗲𝘁 𝗿𝗲𝗮𝗹𝗶𝘀𝘁𝗶𝗰 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲𝘀 - 𝗶𝘁'𝘀 𝗻𝗼𝘁 𝗴𝗼𝗶𝗻𝗴 𝘁𝗼 𝗯𝗲 𝗾𝘂𝗶𝗰𝗸 𝗶𝗳 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝘃𝗲 Don’t rush an implementation. ERP migrations are complex and require time to integrate properly. A phased approach allows for troubleshooting and mitigates a risk for failure. ❓Any other "get rights" i missed and you would add from your experience. #erp #businesstransformation #migration #sap4hana

The biggest businesses can get major programmes horribly wrong. Here are 4 famous examples, the fundamental reasons for failure and how that might have been avoided. Hershey: Sought to replace its legacy IT systems with a more powerful ERP system. However, due to a rushed timeline and inadequate testing, the implementation encountered severe issues. Orders worth over $100 million were not fulfilled. Quarterly revenues fell by 19% and the share price by 8% Key Failures: ❌ Rushed implementation without sufficient testing ❌ Lack of clear goals for the transition ❌ Inadequate attention and resource allocation Hewlett Packard: Wanted to consolidate its IT systems into one ERP. They planned to migrate to SAP, expecting any issues to be resolved within 3 weeks. However, due to the lack of configuration between the new ERP and the old systems, 20% of customer orders were not fulfilled. Insufficient investment in change management and the absence of manual workarounds added to the problems. This entire project cost HP an estimated $160 million in lost revenue and delayed orders. Key Failures: ❌ Failure to address potential migration complications. ❌ Lack of interim solutions and supply chain management strategies. ❌ Inadequate change management planning. Miller Coors: Spent almost $100 million on an ERP implementation to streamline procurement, accounting, and supply chain operations. There were significant delays, leading to the termination of the implementation partner and subsequent legal action. Mistakes included insufficient research on ERP options, choosing an inexperienced implementation partner, and the absence of capable in-house advisers overseeing the project. Key Failures: ❌ Inadequate research and evaluation of ERP options. ❌ Selection of an inexperienced implementation partner. ❌ Lack of in-house expertise and oversight. Revlon: Another ERP implementation disaster. Inadequate planning and testing disrupted production and caused delays in fulfilling customer orders across 22 countries. The consequences included a loss of over $64 million in unshipped orders, a 6.9% drop in share price, and investor lawsuits for financial damages. Key Failures: ❌ Insufficient planning and testing of the ERP system. ❌ Lack of robust backup solutions. ❌ Absence of a comprehensive change management strategy. Lessons to be learned: ✅ Thoroughly test and evaluate new software before deployment. ✅ Establish robust backup solutions to address unforeseen challenges. ✅ Design and implement a comprehensive change management strategy during the transition to new tools and solutions. ✅ Ensure sufficient in-house expertise is available; consider capacity of those people as well as their expertise ✅ Plan as much as is practical and sensible ✅ Don’t try to do too much too quickly with too few people ✅ Don’t expect ERP implementation to be straightforward; it rarely is

SAP Joule is not just a chatbot sitting on top of your ERP. The integration architecture tells a more interesting story. When Joule connects with S/4HANA, here is what is actually happening under the hood: The end user interacts through the Application Client, but authentication runs through SAP Cloud Identity Services with Identity Provisioning handling the trust flow between source and target systems. Nothing reaches Joule without that identity layer being resolved first. Inside BTP, the Joule Assistant operates through a Capabilities framework — connected to a Content Channel via SAP Build Work Zone, with Cloud Foundry Runtime underneath. The Destination and Connectivity Services handle the back-end data access back to S/4HANA's OData Services and Content Provider. The Document Grounding component is worth paying attention to. It extends Joule's context beyond transactional data — pulling from Microsoft SharePoint customer documents via CDM design-time access. This is where the "enterprise context" in AI responses actually comes from. Three things this architecture signals: 1. BTP is the non-negotiable integration fabric — Joule does not work around it, it works through it. 2. Identity and trust setup is the first real implementation challenge, not the AI configuration. 3. The value of Joule scales directly with the quality of your content grounding and OData exposure. AI in ERP is only as intelligent as the architecture enabling it.

Most sellers only uncover ONE level of impact in discovery. That’s why their deals stall, why their ROI slides don’t land, and why their champions can’t sell internally. The truth? There are 4 levels of impact—and if you miss even one, you’re selling half-blind. Selling is helping. But helping means going deeper than “company KPIs.” Here’s the framework I coach every AE on when they’re trying to win enterprise SaaS deals: 1. Company Impact This is where 90% of reps stop. “What’s the cost savings? What’s the revenue upside?” That’s table stakes. If you don’t tie your software to actual numbers—lost revenue, margin impact, labor cost—your ROI story collapses in front of a CFO. Example: A Service Cloud rep I coached quantified millions lost in unbooked hospital referrals because of missed scheduling calls. That turned a “$500K tool is too expensive” into “8X ROI, no-brainer.” 2. Buyer Impact Your champion has skin in the game. They left a stable job. Their reputation, career trajectory, even their family’s well-being are tied to this project. If you can show them how your solution makes them the hero internally, you create unstoppable personal buy-in. 3. User Impact These are the people who log in every day. If they hate the tool, adoption dies. If they love it, productivity soars, morale improves, turnover drops. Shadow them. Ask what frustrates them. Show them a better day in the life. 4. Customer Impact The most overlooked layer. How does your product improve the end customer experience? Faster service, better outcomes, less stress? For a hospital, it’s not about “efficiency.” It’s about a patient getting a life-saving scan booked in hours instead of days. Stop selling features. Stop selling “savings.” Start selling IMPACT. - Company. - Buyer. - User. - Customer. Miss one—and you’ll miss the deal. Hit all four—and you’ll never sell the same way again. Selling is helping. Always.