SAP Process Orchestration Reviews

We are using the solution mostly on-premise but we have purchased a license for cloud processing which we are planning on migrating to soon.

In general, we use SAP Process Orchestration for e-commerce and e-invoicing for the government. Others, we have done Salesforce integrations as well. Most of our work is distributed to approximately 140 countries and depending on the regional requirements we have a few interfaces which are spread across all the regions, such as America, Europe, and Asia.

SAP Process Orchestration is middleware where we are able to manage and interact with everything from a single location. One of the most beneficial areas is monitoring which is very easy because it is all in one place. There are many adapters added recently that can be used for new functionality. The solution is easy to operate and it is more mature than the cloud solution provided by SAP.

The improvement team from SAP Process Orchestration is good at taking in customer feedback. Recently we voted for an update to a migrating mappings issue that has now been added to the solution and that problem is now resolved.

The solution could improve by making it more user-friendly by limiting the code required. We have to add some code in some cases where we need complex logic or some other functions. If this was able to be done in a more simplified manner then it would save a lot of effort and time. By liming code like in case of dynamic variables usage.

We have experienced latency and reliability issues when using large amounts of data. In the future, they should come up with a solution to this problem. Latency in case of huge amount of data. Iterface gets timed out if data is very huge.

I have been using SAP Process Orchestration for approximately 11 years.

The stability is very good, we have not experienced any major issues.

The solution could improve in scalability. Files above 50 MB become a bit difficult to process. However, the scalability could improve if were using Microsoft Azure.

We have approximately 15 people using the solution in my organization.

We have experienced times where SAP support has not been able to solve our issue or other times they were not able to give back much feedback. There have been extended delays from one person to another. We have had some good experiences but they can improve on their knowledge and reducing delays.

We previously used other solutions, such as Xi and Pi.

The installation is quite easy to handle.  I have worked on previous versions also, this could be why I feel it is easy. It was easier for me to jump into the SAP Process Orchestration and feel comfortable with it.

We did the implementation of the solution using a team within our company. Additionally, they handle the migration, maintenance, patching, and updates.

Looking at market conditions, vendors nowadays are giving products at very low price levels. However, SAP Process Orchestration have not yet reduced their prices. The prices could be reduced a lot to stay competitive.

I recommend SAP Process Orchestration because it has currently reached maturity over the last few years. I can see on the online forums there are many questions raised by customers and SAP is slowly taking care of all the issues that people were facing. This is a good solution and they do not need to quit using it to move to a cloud version.

I rate SAP Process Orchestration an eight out of ten.

The solution makes it easy to solve integration problems. Most ESBs and most integration we do, we find it helps solve a lot of integration problems. 

The solution is easy to use. SAP used to be difficult. It was known for being difficult, however, the feeling is quite understandable. The way it's been extracted, the way it's model-driven, it's a very unique product. 

The main job for building, developing, on the tool is the NWDS. That is a NetWeaver Development Studio, and it has some technical things you cannot do unless you switch over to the web version. Therefore, you find yourself switching between tools. You find yourself in contracts, with issues, errors, and all that. They should perfect that.

Other than improvement in what it's currently doing, I do not have anything in mind in terms of a new feature that I would like to see. It just an improvement of what is already available.

The usability, for example, is an area where it can be improved upon.

We've been using the solution since 2018. It's been a few years at this point since we first launched it.

The solution is very stable. It doesn't have bugs or glitches. It doesn't crash or freeze. It's quite reliable.

As it is with most SAP solutions, the set-up for the scaling, we don't have experience with that. We are just using a single server, a single point of failure. We don't have experience with scaling.  That said, my intuition tells me that it's going to be a bit complex. It likely scales. The question as to how easily it does is what I can't really speak to.

Mostly, our team does the technical support. It's our own technical team that would handle any issues. For that reason, we have not had any direct technical support encounters or any reason to escalate to SAP Global as of right now. For that reason, I can't really speak to their level of knowledge, helpfulness, or responsiveness.

The initial set-up was done by a different team. Our business team handled it for the most part. I'm a developer and didn't really play a role in the implementation.

My understanding, however, is that it's not a very straightforward thing. It can be a little bit complex. In order to get different properties, you need to put together different materials.

We're just a custumer. We don't have a business relationship with the company.

The last I checked, we were using the 7.5 version. It may have since switched to 7.6, however, I'm not 100% sure. We typically use the latest version of the solution.

On a scale from one to ten, I would rate this product at a nine. We've been pretty happy with it overall.

We have several SAP systems in our landscape that have different modules incorporated in it, and we are using this solution as a gateway for the integration within our landscape of both SAP and non SAP applications that are within the firewall and outside of the firewall. 

The primary use case of this solution is as a gateway for all of the integrations.

Process Orchestration supports everything from simple workflows to complex practices by developing custom process applications.

Improved message processing - With the process Orchestration Single Stack version the throughput of message processing is improved. This is due to the fact that until now the messages were recorded in both the ABAP and Java databases.

Improved Alert Mechanism - Alerts can be filtered by message content.

SAP Process integration Test (PIT) tool - The PIT Tool is a framework with which you can set up automatic tests for process integration scenarios. It really helped us in testing the interfaces post-migration and saved a lot of effort and time.

B2B integration is easier with SAP B2B add-on.

ccBPM's were migrated to NWBPM which Supports human and automated tasks.

With the latest version, what I find to be the most valuable are the REST, SuccessFactors, and Ariba Network adapter, OAuth 2.0 authentication,x-csrf-token, Improved alert mechanism.

Message deletion option.

NWBPM, BRM and B2B add-on.

The NWBPM is also valuable. In the previous version, they had ccBPM, which caused performance degradation issues. With the migration into the new version, the performance has improved and our customers are pleased with this improvement.

They have rules to configure directly in the integration directory that can be done within the interface itself, instead of configuring within the NWA and manually sending it to the users.

Dell Boomi and MuleSoft have dedicated application based connectors. All of these connectors work on the same protocols such as SOAP, HTTP, and REST. They have dedicated application connectors that can be for  Amazon, Salesforce, ServiceNow, Slack, Google Cloud, Microsoft Azure, Workday, etc that are readily available to use.

When it comes to SAP PO, SAP provides SOAP, HTTP, or the REST-based adapters, which we can use to integrate with any of the above-mentioned applications / Webservices / APIs, etc. have to bit-customize to integrate with those particular applications. This is true when using REST, SOAP, or HTTP.

I feel both application-specific adapters and SAP provided adapters (SOAP /HTTP /REST) adapters, They Still use the same set of protocols to integrate/Connect with respective applications.

Customers will think that they had a dedicated application adapter that will make our life easier. We can just plug in, play, and use it. This is the way sales and customers think and they will tend to go with these tools.

I feel that support is an area that needs improvement. They need to improve the response time and address the customer's issues as soon as possible.

Instead of maintaining so many tools, they should explore all of the features and offer just one tool. It would be good and would help customers as well as SAP.

Since they have a cloud version of integration to SAP CPI, it would be a good idea to provide a migration tool where we can install that tool and migrate the existing interfaces from Process Orchestration to CPA. Customers would appreciate the flexibility, and it would reduce the project cost and manual effort time. 

We were using the 7.3 dual-stack version and recently migrated to Process Orchestration 7.5 (Single-Stack)version. We have been using it for approximately Nine months.

This solution is stable, we have not had any issues.

We have not yet explored the scalability as we are still in the evaluating phase.

Technical support response time is slow. It takes some time to get a response.

I have noticed that in many cases, even though we have priority one or priority two tickets, they simply change that to decrease the level of priority from P1 to P2, and from P2 to P3.

It can take a week to get a response to tickets.

No, We have not used any other Middleware solutions previously. We have implemented all the interfaces in SAP PI/PO itself.

With the previous version, it was a bit difficult and took approximately one week to install and set everything up. When it comes to Process Orchestration, it is a Java-based system that makes it easier when it compares to a dual-stack system, and since we are hosting it in Azure Cloud, it's not a large burden.

Deployment is less than a week with the updated version. Sizing and the hardware takes a matter of seconds when it is approved and once they procure it.

We are handling the deployment.

We have implemented it with the vendor team.

There are fees in addition to the licensing. 

If we want to use B2B, which we use for sending and receiving messages to EDA, then there is an additional charge.

EDA is partners with B2B and you have to integrate them. You have to procure that separately because it is not included in the standard PO license. 

Everything else is by default and B2B is the only addon that we have to pay for it.

We are currently evaluating several solutions, such as Dell Boomi, MuleSoft, and Informatica Cloud. These are the three tools that we are evaluating and will be comparing with SAP Processing Orchestration and SAP CPI.

We will be evaluating how much flexibility there is to move the existing logic. We have to consider both the migration from SAP to a third-party or from a third party Middleware to SAP. It may not be easy, as the main transformation logic that we have built on SAP propriety tools and the other tools. They may not have the compatibility, and we will have to read all of the logic again in those applications.

This all has to be considered before we can make a decision.

We are still in the evaluating phase and we are still evaluating other tools that are available. Based on that, we will be having a round table discussion in a meeting to discuss the outcome and finalize whether we will migrate the interfaces or go with Process Orchestration.

They want to evaluate and list the pros and cons of all of the tools.

As per the automation roadmap, we are planning to move everything into the cloud. We are just evaluating the cloud, particularly tools that are available. Even though we are hosting on Azure Cloud services, it is still on-premises.

They have introduced SAP CPI, and I am not sure whether SAP Process Orchestration is going to be available for much longer as they are investing more into SAP CPI. 

SAP CPI is the new IPaas tool that is improving and not a mature tool as SAP Process Orchestration. SAP is continuously improving and adding more features to SAP CPI.

Many customers are confused, whether they should invest in procure Process Orchestration or  SAP CPI.

There are some clients that invest in both  SAP CPI and Process Orchestration. because due to the current limitations in SAP CPI, they are not able to migrate all the interfaces from SAP PI/PO to SAP CPI.

If customers are considering investing in both, then they might want to think about the licensing costs. It will be a burden for them.

It will good to have a single middleware tool, instead of multiple middleware tools. 

I don't understand why the product companies are releasing multiple middlewares to handle various integrations like A2A, B2B, and EDI integrations, etc.

It will be a burden for the organizations to procure multiple middlewares for their various integration needs. They have to invest more money in licensing and maintenance.

I feel it's a bad practice to develop several middleware tools from the same organization. Instead of developing multiple middleware tools, It would be better to have all of those features into one middleware instead of providing multiple middleware tools? It's more of a business gimmick.

I think SAP seems to be following along the same path as they have many middleware tools within SAP. 

If you see the SuccessFactors, they have a SuccessFactors integration center (IC), where they can integrate the applications using SFTP / REST / SOAP protocols. The IC features are very limited to develop interfaces, it doesn't have flexible monitoring like SAP PO or SAP CPI. 

Of course, the Integration center (IC) is having some advantages, but it will not suffice for the customer to all the integrations using IC and they have to still invest in Middleware.

The SAP CPI area has to improve a lot when compares with the other middleware. 

I would rate this solution an eight out of ten.

SAP Process Orchestration is an interface tool. It's a tool to build interfaces between systems.

The most valuable feature of SAP Process Orchestration is its flexibility in being able to build integrations with SAP systems and non-SAP systems.

This is an on-premise platform and one area they can improve on is having the ability to work with SaaS solutions.

I have been using SAP Process Orchestration for approximately seven years. 

I rate the initial setup of SAP Process Orchestration a nine out of ten.

I rate the scalability of SAP Process Orchestration an eight out of ten.

The initial setup of SAP Process Orchestration is simple.

I rate the initial setup of SAP Process Orchestration a nine out of ten.

There is some monitoring that you can do in the platform in the interfaces which is beneficial. It's a little difficult to use, but it is a typical SAP design.

I rate SAP Process Orchestration a nine out of ten.

We are using SAP Process Orchestration to connect our on-premises safety banking systems. In the middle, we have another layer called SAP POL, which is the Process Object layer. That builds the actual orchestration and persistence of data with respect to the business objects. This is in case anything fails across multiple steps. 

For example, if we have seven steps and the process fails in the third step, we need to start processing from the point of failure, rather than from step one. So, there is a primary user for the process orchestration, which is the SAP POL. 

The most valuable feature is the seamless integration with backend systems.

SAP has decided to move everything to the cloud, which means that we have to invest more. New investments would include things like redevelopment and data transfer. In general, we are not satisfied with the roadmap.

I would like to see more flexibility. It does not have all of the industry-standard solutions available in PO and it is not plug and play, so we have to do a lot of development.

We have been using SAP Process Orchestration for about nine years.

We are satisfied with technical support.

We did not use another solution prior to SAP Process Orchestration but we are considering moving to something new, like Mulesoft.

SAP is doing some arm-twisting, saying that they are ending the support for this product and that we have to move to a cloud-based platform. This means that we have to redo all of our on-premises development and transition to the cloud. There are some small solutions that we can migrate but we are not convinced that this is the only way to go. This is the reason that we are researching alternatives.

The pricing for this solution is fine.

At this point, I'm not sure what advice I would give to those people who are researching this type of solution. I am looking at other products because I want to see how good they are. It may turn out that SAP Process Orchestration is still much better, which means that I would continue with it. There are pros and cons with all vendors, so it may not be worth switching if you are already using this.

At this point, I am generally satisfied with SAP, but the roadmap is something that is bothering us.

I would rate this solution a seven out of ten.

We use SAP Process Orchestration because we have a lot of SAP systems that need integration. There are several on-premises applications that fall into this category.

The most valuable feature is the proxy, which can be used when we have a very large volume of data.

The connectors are very good because you can connect with databases such as Microsoft SQL and Oracle to use their services.

The file adapter is great because we can deal with various file application systems.

The monitoring is one of the greatest features in Process Orchestration because it is user-friendly and easy for somebody who is not experienced. The messages are clear and they can learn how to use the monitoring by themselves.

Improvements are needed with respect to being able to handle a very large volume of data.

The responsiveness of technical support needs to be improved.

The pricing can be improved.

I have about 13 years of experience with SAP Process Orchestration.

Sometimes, if there is a system-related issue where I have to contact SAP and raise an incident, it takes a couple of days to resolve the issue. It is a crazy amount of time spent waiting because all of the end-users are on hold to complete their business, and the problem is stopping them.

In terms of technical expertise, my experience with support has been really good. The timeframe is too long, but their technical competence is high. 

The cost of SAP products is quite high but the quality is really good.

SAP Process Orchestration is something that I recommend because it is a very high-quality product. If the support were faster then it would be even better.

I would rate this solution an eight out of ten.

Primarily, my customers are using the solution for integration. There is so many possible scenarios. For example they are using RFC, IDOC, BAPI like SAP based protools and Database (JDBC), SOAP, File, Mail(SMTP) or REST API integrations. All these adapters are used bi-directionally, enabling a large number of synchronous and asynchronous integrations.

In addition, it offers different complicated solutions with extensive adapters such as expanded B2B, SalesForce and EDI etc...

There are multiple adapters and they are very good/native with SAP. There's a File/FTP/SFTP adapter, JDBC adapter, B2B (EDI) adapter, SOAP, REST. 

The solution provides very good and central logging systems. It offers high flexibility with vertical and horizontal extend capacity.  It means; each node or cluster added horizontally is put into use fully effectively. Likewise, all the RAM and CPU added vertically are allocated according to the need and put into use.

The PO package has about eight or nine products inside it. Like SAP PI, BRM, BPM; so it's quite extensive.

The solution could be more customizable. It's customizable, however, it's underdeveloped.  It supports custom modules, custom adapters, etc. but they need more time to truly develop them. 

It would help if the solution offered flexible adapters like REST adapters or some custom solution. It would help make it a more flexible product.

In terms of technical support, it would be helpful if they handled the tickets a bit faster when queries are sent to them.

I've been using the solution for ten years. I'm still working with it currently. Also have an senior level team in my own company that i manage.

The solution is very stable. In fact, it's amazingly stable. It's never shut down on us and we haven't witnessed any problems with the stability at all.

There are a lot of adapters, including non-SAP adapters. It's a good middleware product.

Typically the clients who have SAP are quite sizable companies. For us, some of the biggest companies in Turkey use this solution, so it can handle quite large organizations.

I've contacted technical support in the past when we found some errors in the product. Their support is based on a ticketing system. Usually, I get the answers I require. Occasionally they can be slow, but overall they're very good. We're quite satisfied with the level of service provided by them.

Neutral

The initial setup was straightforward. It's not complex. Previously, in older versions, it was very complex, but now it can be installed in one day or maybe even over the course of a half-day. They've really worked to simplify things. It could potentially take a maximum of two days to deploy, but no more than that.

It only takes about one to two people to deploy the solution. To maintain the solution, typically my clients might need one or two people.

We have freelancers that assist with deployment and handle other tasks. I'm a freelancer as well.

If you get a PO license, you have PI, BPM, BRM, etc. All of these tools can come in PO, or can be available in a single package under a single license. 

The licensing is based on a yearly contract. It is usually licensed per core, but may vary by country.

Some B2B or custom adapters may cost extra, but other adapters are included in the cost and free.

I have my own SAP installation on my local server but I'm not using it on production items. I'm just consulting with my customers on their production environment.

I'd rate the solution eight out of ten. If the solution was more flexible and offered external monitoring features I would rate it higher. The PI portion of the system is quite flexible, but I've had very complex integrations and had to develop an adaptive modem. It needs some more time to really come into its own.

I'd recommend the product to others. It's very stable and you can use it for SAP and non-SAP integrations.

My organization uses the Java system on SAP Process Orchestration.

The most valuable features of SAP Process Orchestration are its system monitoring and alerts.

SAP Process Orchestration breaks down sometimes.

I have been working with SAP Process Orchestration for the last two years.

I rate SAP Process Orchestration seven to eight out of ten for stability.

SAP Process Orchestration is a scalable product that works well with large and small companies.

I rate SAP Process Orchestration seven to eight out of ten for scalability.

SAP Process Orchestration has a moderate initial setup, which anyone can learn.

SAP Process Orchestration is deployed on-cloud in our organization.

Overall, I rate SAP Process Orchestration an eight out of ten.