User interfaces in a SaaS ERP system, such as Oracle ERP Cloud/Fusion, are prone to changes because the application is constantly modified. Oracle makes form changes on their schedule, so customers do not have control over the release of new versions. Bots that use Oracle forms revisit them with each quarterly release to verify that the changes did not break the existing RPA bots. The bots integrating with ERP systems will frequently break if this is not completed seamlessly.
As complexity goes, Oracle’s EBS and Fusion ERP systems are tier I. This means the forms are large, complex with multiple zones, and not particularly fast.
The most difficult part of the integration process an RPA bot has to perform is the last stage, which is the entry of data into the ERP system. Result is fragility.
Such fragility means users have to revert to inefficient manual processes, like still having to spend time making repairs. Even worse, these bots are usually specific to individual users. You could have hundreds or even thousands of them.
The value of a fragile bot quickly disappears and can even become negative, hitting the total cost of ownership (TCO).