SAP Process Orchestration Reviews

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 use it for facilitating seamless communication among varied enterprise applications and integrating diverse hybrid technologies to enable the exchange of data and information between servers.

It facilitates the automation of various processes, particularly those demanding real-time data exchange between systems. This tool is instrumental in bridging gaps between two systems by synchronizing data, ultimately minimizing human intervention through the automation of diverse processes within Orchestration. SAP Process Orchestration serves as an excellent middleware tool for interfacing and exchanging data across digital channels.

Our priority is to establish a high-availability environment that is error-free, stable, sustainable, and easily scalable. It offers simplicity in design and configuration, along with the capability to seamlessly adapt to evolving business requirements. It provides essential features such as continuous monitoring of all interfaces are crucial for our needs. The documentation provided by SAP is clear and easy to follow.

Implementing changes and introducing new interfaces in Process Orchestration should have been more straightforward. The current system is burdened with a heavy load and has become overly complex, managing multiple parallel interfaces within a single box. It would be more desirable for the system to be lightweight, efficiently handling its tasks without unnecessary complexity. It would be beneficial to enhance the ease of implementing new projects and improve overall stability in our implementations.

I have been working with it for approximately seven years.

The system frequently experiences hang-ups, posing a significant challenge. Unfortunately, there seems to be no definitive solution; troubleshooting involves multiple root causes, and restarting is not always an effective resolution.

Currently, over a hundred interfaces are utilizing the server, and we intend to streamline our middleware infrastructure. The plan is to consolidate multiple middleware servers, encompassing more than a hundred to two hundred interfaces, into a centralized environment. This approach ensures scalability, optimal system performance, and facilitates the smooth transfer of all interfaces from various systems to a single centralized environment. The long-term goal is to simplify monitoring by having a single environment overseeing all types of interfaces.

The technical support from SAP is commendable. However, the support process involves different levels. Level one entails a basic investigation, and based on the incident's complexity, it may escalate to the second or third level. If it is product-related, it reaches level three of product support. Despite the established process, reaching the product support level is time-consuming. The resolution of actual product issues takes longer than anticipated. To enhance customer experiences, SAP can reduce the initial response time, improving turnaround time for issue resolution. Additionally, there is a need to enhance stability and optimize SAP BI for handling high-volume transactions and data exchanges, making it more lightweight.

The initial setup is quite straightforward.

Deploying SAP Process Orchestration for a couple of interface scenarios can be accomplished within a timeframe of four to eight weeks. Leveraging our in-house consultants, the initial steps involve managing the hardware and determining the landscape structure—whether opting for a two or three-system configuration. Configuration activities include linking all satellite systems to the SAP PO system and establishing necessary settings such as File Landscape Extension, exchange profiles, technical systems, and business systems. The next steps involve defining these elements within the SAP Process Orchestration environment. Once the groundwork is laid, the interface development process begins. Breaking down the interfaces into specific formats and fields is crucial. This involves creating mappings for the fields, specifying how data exchange should occur between systems. This comprehensive exercise is undertaken by the SAP Process Orchestration consultant.

We subscribe to annual licenses, and the competitive license cost is reasonable. We find that the cost is even more affordable compared to other options available in the market.

It is highly recommended for customers seeking a lightweight application. Overall, I would rate it seven out of ten.

I am an integration architect involved in the implementation side of SAP PO (Process Orchestration) where we deploy hybrid implementations for customers. Of our ten current customers, most are technical users of SAP PO.

Every day we integrate more and more components with other components. Naturally, the tendency of the market nowadays with middleware tools like SAP PO is to have all the various systems integrated within themselves and with third-parties, and so on.

In my opinion, SAP PO is the most mature suite of tools to integrate processes across SAP environments at this moment. It's really unbeatable because it allows you to integrate whatever scenarios you can imagine. Compared to the rest of the tools available, including other SAP tools like SAP Cloud Platform Integration, it's the most well-developed and versatile suite on the market when it comes to process integration.

I think the main area that SAP PO should improve on is offering pre-delivered content like they do when you use SAP Cloud Platform Integration (CPI). SAP should not forget that they still have a lot of customers using Process Orchestration and they should focus more on providing pre-delivered content in SAP PO.

The other main problem nowadays is that there is no easy migration from SAP PO to SAP CPI. In terms of moving from Process Orchestration to Cloud Platfom Integration given all the connectivity requirements (not only within SAP environments, but also with third-party systems), I feel that there is more work yet to be done by SAP. In addition, the knowledge and know-how gained from using SAP PO cannot be fully translated into SAP CPI, so there's another area that they could look into making easier for users.

I've been using SAP Process Orchestration for the past 12 years. 

It's a very stable and mature solution.

SAP PO is not as easily scalable as the cloud solution, but it is certainly scalable. That's the idea, after all. Every day you need to integrate more components with other components, scaling up as you go.

The technical support is good.

The initial set up is quite easy and straightforward. Of course, that depends on who does it, but with my years of experience, it's not a problem. All in all, it took me around one week for the installation.

I am the implementation consultant and I can say that the pre-requisites and staff requirements for implementing SAP are very target dependent, and it all depends on the project at hand.

Like most other middleware tools, it's not particularly demanding in terms of having lots of people involved. However, you do need professionals who are well-qualified.

The license is a one-time payment, and additional costs are only incurred on the infrastructure side since it's an on-premise solution.

My advice is that it's not a good idea to re-implement the wheel. It's better to go with secure and mature tools. And if you have a SAP ecosystem it's better to stick with the products of SAP. SAP PO is a very mature product and if you're going the cloud middleware route, I'd put forward that it's a good idea to have a hybrid test scenario with a combination of SAP PO on-premise and SAP Cloud Platform Integration together.

I would 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.

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.

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.