SAP Intelligent RPA Reviews

The inputs of SAP Intelligent RPA used to come from the process mining output. Whenever we connect process mining to the SAP instances, their SAP instances give us what processes, where the bottlenecks are, and stuff like that; then that is what we fed into the automation, and we started automating it, but it has been almost a year and a half ago.

I used the tool for automatic, automated material master creation. The company I was working for was dealing with a lot of oil and gas companies that had SAP and every time they had to send a product to an offshore plant, they had to create a material in the back-end system. Creating materials is always a manual process, so that was the kind of a backlog or one of the bottlenecks for them. We automated the process using UiPath and SAP Intelligent RPA. We first did it on UiPath and then moved to SAP Intelligent RPA, and both solutions worked really well. What we did is we created a template that people can fill in an Excel template and then send to the bot, and the bot automatically creates a material master based on which offshore plant, which onshore plant, and all those kinds of business logic. It used to create something for plant maintenance and the list of materials, which were all areas that were automated.

The major use case for SAP Intelligent RPA is in the area of SAP's ecosystem. If you want to automate anything outside of SAP, like Salesforce, for instance, or you want to automate anything else, then SAP Intelligent RPA is not the best tool. The tool's use cases are limited, and it is limited to SAP only. If you are thinking of any other applications, then it is not the best tool. You might have to use some independent IRPA providers like UiPath or some other product.

As I am an automation specialist, SAP Intelligent RPA and process mining tools would be the more beneficial ones.

The tool's licensing has been kind of a challenge. If the tool can bring up a usage-based licensing model, it would be really good. Even a flat rate kind of licensing model would be good, where, for instance, you can have any number of unattended bots, but you pay a package kind of price. At the moment, the tool does not offer different licensing models to users.

I have been using SAP Intelligent RPA for years.

It is a stable solution.

It is a scalable solution.

My company is a service provider and I am a part of the developers and admins who provide the tool to others. I have seen client companies where there are 100 to 500 users using the product.

The solution's technical support is amazing. When you contact SAP, there are account managers, specifically technical account managers, who can help you with anything.

Right now, I am not working on process mining at the minute. Before I switched to the company, I worked extremely closely with the process mining tool from UiPath, SAP BTP, and the process mining that they had created. I am working with MuleSoft Automation and Anypoint. We are not doing any sort of process mining at the minute, but in my company, because MuleSoft is one of the only RPA tools that we are looking at, we have another application called Appian that we are trying to explore now. Appian has process mining capability, which is why we thought we would look at it along with AI capabilities.

The product's initial setup phase was not extremely straightforward, but it was not very difficult either. For somebody who knows SAP, it becomes very easy for them to use it, but we have a lot of dependency on the admin or SAP personnel who have to enable a certain transaction code. We should be able to work with the transaction code to get things operational. I wouldn't say the tool has the most straightforward setup process, but it is not very difficult either.

Speaking about bot creation and management features, I rate the tool as four out of five compared to the other market leaders. UiPath is much better, but SAP is not very far behind.

For SAP Intelligent RPA, the main thing I would say is that whenever someone plans to use SAP, it is best to use it within an SAP ecosystem. If they already have an infrastructure set up with admins and basic consultants, it is really good for them to start and jump onto SAP Intelligent RPA. In terms of process mining, SAP is extremely good. Process mining gives us the bottlenecks, and SAP Intelligent RPA can tap into them and start automating them, but if they don't use it without process mining, then they will have to depend on business users to tell them where the bottlenecks are. Relying on business users is not reliable most of the time, and then they cannot prioritize things because there might be one department, like the finance department, which will prioritize their processes to be automated while somebody like plant maintenance or material masters, material management teams might not have the supply chain team to have their processes automated. It is important for people to use SAP Intelligent RPA with the process mining tool.

SAP's process mining part is the area where some AI is embedded. Considering that it has been a while since I worked on SAP Intelligent RPA, I feel there might be new features that have come up since then, but I don't know if they have any AI integrations. The time I worked with the tool, there were no AI integrations in it.

I rate the tool a seven and a half out of ten.

We try to automate some of our scenarios, basically based on requirements, SAP scenarios like sales order creation, sales order simulation, and something like that.

I found the document extraction service to be very useful. It was easy to use and integrated well with SAP ALC. 

I also liked the ability to call back and connect to our data and the ability to automate web services without having to do any manual work and create a sales bot. It was pretty easy to use the tool. 

I found that SAP Intelligent RPA can be somewhat unstable when using SAP GUI. When we upgraded from SAP GUI version 7.50 to version 7.70, we had to update our SAP Intelligent RPA screens even though the screens were the same. This was difficult and time-consuming.

I have been using this solution for two years now. 

Scalability is fine. It is pretty nice. There are around 20 end users using this solution in our company. 

If you are using a ticket, it is pretty much, like, they will assist us well. But, without raising a ticket, it is difficult to get support. 

If you are using any query in that SAP community, sometimes it will get there, and sometimes it will not. So that is there.

Our company used UiPath.  

The initial setup from an end-user perspective was pretty easy. The first time, it will take some time if we know the processes, it will take an hour to set up.  

The pricing is not that expensive. It is manageable. 

I will recommend using the solution. 

Overall, I would rate the solution an eight out of ten because it is easy to work with and easy to handle.

I have been involved in automating several procurement and sales-related processes, and this has been a thorough and rigorous undertaking. The automation process begins with email extraction from the inbox, saving emails during the first week. Following that, data was extracted from email attachments. Once the data was extracted from the files, the IRP monitored and validated the data for correctness. If any data was found to be in an incorrect format, it was transferred to the SAP system, which includes SAP ERP or SAP ECC.

The introduction of RPA brought several notable improvements for our clients. First and foremost, it eliminated the repetitive manual actions that end users had been performing for a decade or even two. These manual tasks were prone to occasional errors due to human intervention. Another key benefit was the speed of processing. For example, manually processing an invoice used to take three to five minutes, but with RPA, this time was cut by at least 50%, often even more. In financial terms, manual processes require the involvement of three or four people handling different aspects of tasks like purchase requisitions and invoices. RPA streamlined these processes, resulting in cost savings.

It proved to be a significant improvement in terms of data extraction. It is remarkably easy to configure and code, and it doesn't require an extensive technical background or coding expertise. The ease of use is a major plus point because the level of technical knowledge needed for initial setup and ongoing support was minimal. The tool provides templates and pre-existing features that simplify the coding process. One of the most significant advantages is its adaptability. Client requirements often evolve, and business departments frequently change their needs, with IRPA, you can easily adapt and make modifications and adjustments swiftly, which is highly efficient.

For potential features or improvements, one aspect I would suggest enhancing is the flexibility of the extraction process. Presently, there are some rigid requirements when it comes to templates for data extraction. It would be helpful if SAP IRPA could be more adaptive, allowing data extraction from various templates. This would be particularly valuable since every client, vendor, or business may have unique invoices, purchase orders, and documentation formats. It would be advantageous if SAP IRPA could simplify locating and extracting information from various templates, perhaps by making coding adjustments or changes to the background template structure.

I have nearly two years of experience implementing it.

The stability is quite satisfactory, and it's important to note that they are consistently working to enhance it.

It offers excellent scalability capabilities. It is applied across various business scenarios, and the number of clients utilizing it continues to increase steadily.

I had a positive experience with their support services. They were responsive and often exceeded my expectations, as I would typically receive a response within one day. I would rate it eight out of ten.

Positive

When preparing for the implementation of an SAP IRPA project, there are several key steps to follow. It usually begins by analyzing the client's system and data. Understand the existing processes, especially those that the client wishes to automate. Determine whether the processes are based on SAP standard practices or involve customizations. Then proceed to investigate the format of the data, ensuring it aligns with SAP standards or identifying any variations. It is important to map out the steps involved in the processes you intend to automate and understand how the processes are currently executed manually. After you start building the RPA bot, determine how data will be extracted, where it will be extracted from, and where it needs to be placed. The next step is to conduct a user acceptance test to ensure the bot performs according to the client's requirements. This step is crucial for identifying any issues or discrepancies and ensuring the bot meets expectations and it should be documented. It is mandatory to test the bot thoroughly in different environments, including the development and production server, make any necessary changes, and ensure the bot is ready for deployment in the client's production environment. The number of team members required for this process depends on the complexity and the number of scenarios the client wants to automate. If the client's requirements align with SAP standard practices, the implementation may take four to five months. However, if there are customizations or non-standard processes, it could extend to six months.

While there is an initial investment in implementing RPA, the efficiency of the systems improves over time. Within six months to a year, the company's expenses are significantly reduced compared to manual operations, ultimately achieving cost efficiency.

Overall, it is an affordable solution. The initial cost might seem higher, but over time, with continued use over five or ten years, the cost tends to decrease, making it a more economical choice. The pricing is typically fixed.

Before opting for it, it's crucial to analyze which processes should be automated. It is also important to understand that SAP IRPA isn't a one-size-fits-all solution and it can't magically automate every process. It's advisable for the client's technical or IT team to carefully assess which processes are straightforward and align with its standard configurations. These are typically the processes where automation is most efficient and has a higher likelihood of achieving successful results. On the other hand, if a process is highly complex and heavily customized, attempting to automate it might lead to reduced efficiency. In such cases, the client should be prepared for challenges, and the efficiency gains may not be as significant, perhaps only a slight reduction in manual effort. Overall, I would rate it eight out of ten.

It's related to automating redundant processes, especially in retail and wholesale businesses. It has a new functionality of BTP, allowing a low code or no code approach for consultants without a coding background.

It seems to be a good offering by SAP in terms of the value it provides.

I would really appreciate SAP if we could integrate it into my Outlook mailbox to help me with churning out the mail that I should prioritize and based on that. I should go with it. So, automating my mailbox Outlook.

I've been associated with it for the last two, or three years. However, in my twelve years of experience, I just tried POC and was trained around it, but not implemented on any of the live projects.

It's stable and it can be monitored and customized as per the client's needs.

It is a scalable solution. It can be scaled to the number of employees or consumers without a challenge.

This RPA is being sold in a bundle approach. Every mid or bigger-size company goes ahead with it to automate their processes.

People are getting more information, and it's starting to get traction from consumers.

Most of the details are already in the help portal and SAP notes are available. It is well documented as part of the product support.

Before IRPA, people were using their own Python codes to automate things.   

And there are other programming engines the customers use. So, this is something that SAP has brought in as part of their own umbrella.

We chose SAP IRPA because it is a more integrated part of SAP itself, giving the client more confidence to have it within the same brand.

The initial setup is of medium complexity. It is neither too hard nor too simple.  You need some background in SAP and an understanding of it.

You require a background in coding. So, if somebody did not have a background in SAP, it would be a difficult setup for them. 

The setup is not time-consuming. If you have the license, it's ready to go.

The deployment model is dependent on where the clients want to store their data. It can be on any of the available transcripts like Azure or Google Cloud or stored in SAP as a database.

It all comes with a bundle right now.  Having advanced features, it is competitively priced.

I would recommend you to visit SAP's partner site. They have various testimonies given by various diamond clients that they have, those who have implemented this solution, and go through those testimonies and relayed them to their case studies. If it relates to you and you feel the product is right, you should go for it.

I would recommend using the solution. Overall, I would rate the solution an eight out of ten. The reason is that the SAP IRPA is a very nice product, part of it completely under the SAP Umbrella, but it's a bit late in the game. The reason is that people already have automation, which is not something new. 

People have already had their alternatives with outside offering products that are available. So only they can tap into the new implementation or green the new projects that are coming up, they can push for that. 

There is something that has to be tested in terms of different industries and how it can be having more use cases around it, being a new product. 

SAP Intelligent RPA has greatly improved efficiency in various business processes, from real-time customer support to background operations. In my RPA projects, I have automated tasks for both attended and unattended scenarios. For attended processes, like in a call center, I have created bots to assist agents during customer calls, retrieving information efficiently. In unattended cases, the focus is on automating tasks without user interaction, making it flexible for on-demand triggers.

The standout features of SAP Intelligent RPA are its flexibility and integration capabilities. It smoothly handles both attended and unattended automation tasks, connecting seamlessly with systems like CRM, databases, and APIs. Noteworthy features like Orchestration and Job Factory simplify scheduling and deployment, eliminating the need for complex manual setups and enhancing overall efficiency.

One way SAP Intelligent RPA could improve is by integrating built-in DI services for document processing. Currently, users might have to use external AI tools, but having these services within SAP Intelligent RPA would make document-related tasks more straightforward and eliminate the need for external solutions.

I have been working with SAP Intelligent RPA since 2019.

SAP Intelligent RPA is a quite stable product. I would give it a nine out of ten for stability. I have faced issues and bugs with the product during debugging. Sometimes, we run into bugs that require going to the task manager to manually end instances.

I would rate the scalability of SAP Intelligent RPA as a seven out of ten. It allows for as many users as needed, but organizing permissions and access to projects requires some management.

The technical support is excellent. They are quite responsive. I would rate the support as a ten out of ten.

Positive

Deploying SAP Intelligent RPA is easy. In development, create and upload the file to the server. Beforehand, set up the environment, including users and agents. There is a desktop studio for development and a desktop agent for interactive tasks. Install the desktop agent on the machine where automation occurs, and ensure it is connected to the server. Creating an account with SAP makes deployment easy. SAP manages the setup for you, and you pay for server usage. 

The pricing for SAP Intelligent RPA operates on a model that considers power usage and transactions per job. It is adaptable based on the number of cases and the specific needs of our business. The cost can vary, making it either more affordable or more expensive depending on our individual requirements and usage patterns.

Overall, I would rate SAP Intelligent RPA as a nine out of ten.

We are using SAP Contextor for accounting processes.

SAP Contextor has improved our organization by giving us better operational efficiency. 

The most valuable feature of SAP Contextor is that everyone is in one place in the program that I need.

SAP Contextor could improve by automating some processes.

I have been using SAP Contextor for approximately two years.

SAP Contextor is a reliable solution.

I found SAP Contextor to be scalable.

We have thousands of people in my company using SAP Contextor.

I would recommend this to large companies, such as big corporates. I am not aware if it will be useful for startups and contemporary startups.

I was satisfied with the support from SAP Contextor.

I have not used another solution previously.

SAP Contextor has made our organization efficient which has provided us with cost savings.

I did not evaluate other solutions. The choice to use SAP Contextor was done by my organization.

I rate SAP Contextor a seven out of ten.

A few companies in France use Contextor. For example, the Engie gas company is large in France, another company is EDF electrical company, and there are other companies as well. This tool is installed in a few companies in France because Contextor has been in existence for more than ten years. It's known.

In the new economic model, it's good for small use cases. The SAP Contextor provides a volume of transaction operations.

SAP uses Contextor as a tool to increase automation capacity.

With Contextor, it is possible to add functionality and add capacity with another language, much like Python or C#. 

It is also possible to do that with UiPath and Automation Anywhere, but it is more complicated with these solutions.

The older models of Contextor are good and competent, with good skill, good practice, and the level of precision is important.

One of the biggest differences between Contextor and other solutions is that it is not based on the OCR functionality to discover certain applications like Citrix or remote access.

UiPath and Automation Anywhere use OCR functionalities but with Contextor it's the runtime into the Citrix server.

Contextor is a good solution for a Citrix environment. It's the first with this tool. Other tools provide the same functionality, but not with the Citrix environment.

The support is expensive.

Contextor is more difficult to learn and use because of its approach. It is more with the programming. It's a tool for developers who have a good understanding, with good practical skills in JavaScript, and knowledge of the Windows operating system. 

UiPath has another approach that is more user-friendly with the strategy that is oriented for the end-user.

I would like to see a better capacity for unstructured data, for example, PDF, or text within images.

I am the owner of a precursor of Contextor. I created it 20 years ago.

This solution is stable. 

You must have a good understanding and knowledge of this tool to produce good delivery.

It's similar to UiPath or Automation Anywhere, but the approach of Contextor is more program-oriented and more technical than UiPath or Automation Anywhere.

With the older versions of Contextor, the scalability was not very good because it was necessary to install the backend server directly.

Now, with SAP iRPA, it is not the same situation because SAP provides iRPA on-premises. It's fast and scalable.

I have not deployed the ERPA yet, but I have a few developers who are learning this application.

We have a few thousand users.

The technical support is good but It's more expensive than Contextor.

It's easy to deploy this solution for one or two automated robots, which is good for a small, medium, or large company.

This is not a tool or software with a license as others are. The SaaS model is based on the usage of the tool.

I created a Contextor precursor in the Societe Generale Group 20 years ago. 

This tool was discovered by the Xsarnet Company, and ten years ago Xsarnet changed its name to Contextor. In December of last year, Contextor was purchased by SAP. 

As a creator of the Contextor precursor, I know this solution internally. I have a strong knowledge of this tool and other solutions, so I am capable of many comparisons between all of these solutions.

UiPath or Automation Anywhere are good solutions, each has its advantages and disadvantages.

I would recommend this solution to others. It's a good solution.

I would rate this solution an eight out of ten.

Currently, I am an SAP consultant with 30 years of experience. I am interested in the upload automation.

SAP Contextor was used as a test, so it was pre-work to determine a package selection.

I originally implemented SAP Contextor because of the list of functionality options it had. Unfortunately, I found that the SAP scripting of a program is easier than SAP Contextor, so I am not using Contextor any further. 

The solution does not recognize objects, command windows, buttons, and fields, so it is not useful. Because of this, I was not able to complete any single or transition error. Every time I tried, Contextor would fail.

I have been using SAP Contextor for one month.

I don't believe the product is commercial, it is not enough.

The initial setup of SAP Contextor is easy.

I personally installed the solution myself.

The product did not work. I would rate it a two out of ten overall.