We have over 50 bots running on our legacy ERP, but we are migrating to SAP S/4HANA next quarter. How do we prepare for the massive bot breakage that will likely occur? Are there tools for "Self-Healing" bots that can detect UI changes automatically, or are we looking at a complete rewrite of our automation library? I am worried about the downtime for our automated financial closing process.
3 answers
ERP migrations are the "acid test" for RPA stability. If your bots rely on "Surface Automation" (image recognition), they will 100% fail. You should move toward "Object-Based" selectors or, better yet, API-led automation where possible. For the UI parts, some modern platforms offer "AI Computer Vision" that can adapt to minor layout shifts, but for a major move like S/4HANA, you need a migration factory approach. This means auditing your bots now, identifying which ones interact with the legacy screens, and re-mapping them in a sandbox environment before the actual go-live date to ensure zero day-one failures.
Have you considered using this migration as an opportunity to replace some of your UI-based bots with native SAP Fiori apps or internal scripts?
Always build a "Kill Switch" into your bots during migrations. If a bot starts inputting data incorrectly due to a UI shift, you need to stop it instantly.
Great point, Maria. An uncontrolled bot on a new system can cause more data cleanup work than manual entry ever would.
Kevin, that is exactly our secondary goal. We realized that about 10 of our bots were just moving data between Excel and the ERP because the legacy system lacked a specific report. S/4HANA actually has those reports built-in. By doing a "Lean" audit alongside our migration planning, we hope to retire about 20% of our bots and replace them with native ERP functionality. This reduces our RPA maintenance burden and makes the entire IT ecosystem much more stable in the long run.