SAP Process Orchestration Reviews

The main use case for SAP Process Orchestration is that it's an SAP proprietary tool which integrates within SAP and outside SAP. It's the most familiar middleware tool which is used for integrations.

SAP Process Orchestration has various functions, and it's loosely coupled with all the legacy applications we're trying to integrate. It has various feasibilities, connecting to chemical industries, pharma, and manufacturing. It has all the features and adapters which are inbuilt and can be used to integrate applications using data exchange.

When it comes to the main benefits SAP Process Orchestration provides to users, in the open market, we have multiple tools readily available for third-party integration. However, with SAP Process Orchestration, the main advantage is its point-to-point integration, allowing us to directly create system-to-system integrations. It's very flexible, facilitating troubleshooting in one single system. It also offers easy maintainability, and is a very flexible tool that easily adapts to any integration standards and artifacts that are readily available.

SAP is already trying to make improvements for SAP Process Orchestration by releasing updates every quarter, including patches and modules, and from a security standpoint, while it's a tightly coupled tool, they are introducing a lot of enhancements aligned with current market trends. There are standard contents readily available for starting integrations, which suit around 90% of every industry across verticals including pharma, manufacturing, and employee data central with SuccessFactors integration.

Regarding functionality-wise improvements in SAP Process Orchestration, they are now incorporating the Salesforce system. Previously, we needed to rely on a third-party adapter for integration within SAP, but now they are building their own adapters to connect with Salesforce. Additionally, there are options like data connectors using Ariba coming up with SAP Process Orchestration. There's much more to explore, especially as they release new patches, enhancements, and adapters each quarter.

I have been working with SAP Process Orchestration since 2013.

SAP Process Orchestration is more stable now. It's matured and more stable than before. I recognize that every product has its own pros and cons, as not every product suits the market 100%. Each has its pros and its cons.

For scalability, SAP Process Orchestration rates as a nine.

The technical support from SAP deserves a rating of 10 out of 10.

Positive

The initial setup for SAP Process Orchestration is a one-time activity, and it's not that complex.

The price for SAP Process Orchestration is a little high when compared to market trends, which is just how the business is. I would rate it an eight.

SAP Process Orchestration has evolved into a cloud platform integration. The next version of SAP Process Orchestration is CPI, and it has evolved as an integration suite. Now, all the business models have been collected or collaborated in one single place called Integration Suite. It's a cloud-based application, while SAP Process Orchestration remains an on-premise tool.

When discussing event-driven architecture support in SAP Process Orchestration, the main thing is the architecture itself. If you don't know about the architecture, then there's no point in proposing this particular tool and understanding how and when to use it. Without that knowledge, we can't propose anything related to the infrastructure or integrations. That's the key concept in using SAP Process Orchestration.

On a scale of 1-10, I rate SAP Process Orchestration a 9.

The primary use cases for SAP Process Orchestration involve processing EDI invoices for customers.

SAP Process Orchestration is quite flexible in supporting various integration standards and protocols, and it's fulfilling all our needs.

We have the core component as SAP, but in a company that produces things, there are also conveyors, light signals, and steering systems. The machines in production have special software which is connected with SAP interfaces. There are quite a lot of interfaces being used to attach data to SAP. This is quite normal, as every customer has the same challenges with interfaces.

The main issue is that these products, which evolved from Process Integration to SAP Process Orchestration, will be replaced and will have no support in the future. That's the only concern, necessitating a move to new solutions.

Technically, the Java interface is pretty outdated nowadays. From a technical perspective, the installation works, but regarding functionality gaps, that can only be judged by colleagues from the integration team. According to what has been heard, it fulfilled our needs, though detailed knowledge is limited.

We have been using SAP Process Orchestration for approximately three years.

The deployment was straightforward.

We have used SAP technical support, and eventually, a solution is provided. The tricky part is always picking the correct component when reporting an issue; otherwise, the wrong team works on it until it reaches someone in the correct component. As SAP software is quite complex, assigning tickets to the correct person is challenging and should be improved in general.

Positive

We previously used Seeburger before migrating to another solution. We were using PI, which is now SAP Process Orchestration.

Technically, implementation took just a week to implement all three systems for development, test, and production. For the migration, it took about one year for the integration team to migrate all the mappings and processes from Process Integration to SAP Process Orchestration until everything was running in the new solution. The hard part of the migration is moving all business processes into the new solution. This typically takes a year or two, similar to a brownfield migration to S/4HANA.

I participated in the implementation of SAP Process Orchestration in my company, specifically in the sizing and setup of the servers.

The option we are considering is Integration Suite, also by SAP.

Our review rating for SAP Process Orchestration is 7.5 out of 10.

We are in a transition from ECC to HANA. We will migrate to Integration Suite for all EDI solutions via BTP, the Business Cockpit. It's moving toward Software as a Service solutions in the future rather than having these solutions, hardware, and software in-house.

Working primarily on SAP Basis and providing machines, with the integration team handling SAP Process Orchestration, the feedback provided is mainly technical in nature.

I have worked with SAP Process Orchestration to facilitate interfaces between different systems, including various SAP modules like HR and FISCO, and non-SAP systems. We also use it alongside SAP BTP to interface these modules.

The basic features of SAP Process Orchestration, especially the collection of adapters such as File Adapter, SOAP Adapter, REST Adapter, HTTP Adapter, and FTP Adapter, are the most valuable. Sometimes, the BPM feature is also useful, although it is used about twenty percent of the time compared to the standard features. In terms of overall usage, the suite's integration capabilities allow organizations to maintain stable connections across different platforms, with compatibility being a significant plus.

The user interface of SAP Process Orchestration should be more modern to enhance its appeal. It can seem complicated and outdated to new users. Additionally, the tool relies on Java, which feels less contemporary. Although its technology and power are excellent, a more updated interface would be beneficial.

I have been working with SAP Process Orchestration for about 15 years.

SAP Process Orchestration is a fairly stable solution, and I would rate its stability as an eight out of ten.

SAP Process Orchestration is easy to scale, as it has an interface to create users and assign roles accordingly. There is an identity provider integrated within the system for these actions.

I have not contacted SAP customer support in the last 10 to 13 years. My experience and the internet have been enough to solve any issues. I only possibly needed it at the beginning, but have not since.

Neutral

The initial setup of SAP Process Orchestration is not very difficult and I would rate it a seven out of ten in terms of ease.

SAP solutions are generally expensive. SAP Process Orchestration was integrated with SAP ECC in a package, but my customers have consistently described it as an expensive product.

The user interface of SAP Process Orchestration is considered older when compared to other solutions like Talend or WebMethods, which might look more user-friendly.

The biggest benefit of SAP Process Orchestration is its stability and specific adapters which are well-suited for connecting SAP ECC to SAP Process Orchestration. However, the suitability of the solution often depends on the knowledge and skills of the person implementing and using it. Overall, I would rate SAP Process Orchestration a 10 out of 10.

SAP Process Orchestration is used as a middleware for B2B and AI integrations. It serves as a standard middleware for SAP projects, facilitating data exchange between external partners or internal systems. 

It is particularly beneficial in the defense industry for orchestrating logistics, transportation management, warehouse management, finances, and other operations within defense agencies.

SAP Process Orchestration has driven cost savings and improved operational efficiency through its prepackaged content, which provides ready-made solutions, reducing development time and cost. It enables seamless B2B integration and support, which are essential for operations within defense agencies.

SAP Process Orchestration provides extensive integrations with external partners, supports B2B operations, and has prepackaged content that saves development time. The content offers readily available solutions that are particularly beneficial in environments like defense where systems are disparate.

SAP should improve the user interface, as it often lacks modern features and aesthetic appeal. Additionally, there are other areas in need of enhancement, including monitoring features and end-to-end graphical representations, which have not been improved for many years.

I have been using this solution for almost 20 years.

SAP Process Orchestration is very stable, and I would rate its stability at nine on a scale of one to ten.

The solution is highly scalable, and I would rate it at nine out of ten on a scale of one to ten for scalability.

SAP's customer service is generally not satisfactory. When a ticket is opened, by the time they respond with queries, we often already have an alternative solution. I would rate the customer service at five out of ten.

Neutral

As soon as SAP was chosen as the ERP system, SAP Process Orchestration was the default choice. It is cost-effective and provides content that is reusable and aligned with SAP, making it a straightforward choice over other middleware solutions.

The initial setup of SAP Process Orchestration is straightforward and uses a simple installation method. The availability of prepackaged content reduces the need to start coding from scratch, thereby saving time.

Deployment and installations are primarily done by administrators, with some technical involvement.

The return on investment comes primarily from the cost savings associated with the prepackaged content, which drastically reduces the time and cost of development. The availability of ready-made solutions enhances operational efficiency.

SAP Process Orchestration is considered to be cheaper than other middleware solutions up to a certain volume level. It is notably less expensive than alternatives like MuleSoft.

MuleSoft was evaluated as a potential solution, but due to its expense and the lack of specific prepackaged content available with SAP, it was deemed unsuitable for certain projects.

For organizations that operate within an SAP ecosystem, SAP Process Orchestration is recommended due to its cost-effectiveness and the availability of valuable prepackaged content. It is important to consider the needs of your industry, as SAP Process Orchestration may not meet all requirements in consumer-oriented sectors.

I'd rate the solution eight out of ten.

I use the solution in my company for the inventory part, specifically from our POS to our central inventory, from our e-commerce sites to our central inventory, and for all the communication and integrations involving purchase orders.

Some configurations can be a little tricky. The consulting team had to spend a long time checking SAP's community forums and documentation to achieve some goals. The tool could release some new functionalities.

I have been using SAP Process Orchestration for ten years. I am a customer of the solution.

I think it is a very stable tool. My company did not have any problem with the tool.

SAP's support is the same for all its products. It would help if you had patience because SAP tends to apply its SLAs, so it all depends on the kind of issue. In general terms, the support is very good. I rate the technical support an eight out of ten.

Positive

I have used IBM and Pentaho. I started to use SAP because the native integration with our company's other SAP systems was good. With SAP, our organization can manage all the use cases associated with the integration.

My role is as a manager, but I think the product's initial setup phase is somehow not so difficult for the consultants. I rate the product's initial setup phase as five out of ten.

I didn't participate in the product's deployment phase.

The solution is deployed using the cloud services offered by AWS.

The solution can be deployed in a month.

The product is not a low-priced solution, but I can say that it is competitively priced in the market. There is a need to make yearly payments towards the licensing charges associated with the product.

Before choosing SAP Process Orchestration, I evaluated other options, like Pentaho, Informatica, and Cloudera.

Speaking about the pros and cons of other tools compared to SAP Process Orchestration, I believe the integration with our SAP systems is good, the facility to implement all the solutions with the same consulting team and the fact that we deal with people who we already know adds trust when it comes to SAP systems. When it comes to the other systems, like in the case of Informatica, there is somehow some expenditure. In the case of Cloudera, the architecture was not all that we wanted for our ecosystem.

SAP Process Orchestration has benefited our company's workflow and integration management. One of the greatest benefits of the tool is that it is very reliable and robust. We have great support from SAP's team. The tool covers all of our company's use cases.

To those who are looking into purchasing SAP Process Orchestration, I will recommend they have the details of all the benchmarks associated with SAP with their consultants and look into other solutions. The important thing to figure out is whether it fits in a better manner as per your requirements.

I rate the tool an eight out of ten.

I use the solution in my company for any third-party or internal integrations, meaning that the tool is mainly used for integrations.

I think that SAP should work more on data modeling. Based on what I know and from my experience, I feel SAP is stable to a certain degree of volume when it comes to data modeling. If the volume of data goes high, then SAP PI/PO has issues while connecting with third parties, so we have another middleware to connect to third parties. If you are connecting directly to third parties, that means you are exposing your internal network to third parties. Data modeling is an area of concern in the product where improvements are required.

I have been using SAP Process Orchestration for four to five years. I am an end user of the solution.

It is a pretty stable solution. I have not seen any outages in the solution.

It is a pretty scalable solution. You can use the tool for small integrations and large integrations.

From a use case perspective, all the people, around 3,000 employees, use the tool in my organization since some form of the product's integration capabilities are used in the company and have their own requirements of interfaces.

There are no plans to increase the use of the solution in my company.

My company has a couple of managers and developers to do the coding and mapping in SAP PI/PO. If I talk about the APAC region, I have almost eight to ten people who take care of the tool's complete technical area.

I have experience with XIB Solutions. SAP connects to PI/PO, and then it connects with the third parties. My company decided to use SAP Process Orchestration since it was an enterprise-based decision to use the same solution across the country.

The product's initial setup phase was easy, especially considering my discussions with the technical personnel in my company.

The solution is deployed on an on-premises model.

For our company, if we have to do any integration, depending on the complexity, the deployment process can probably take two or three days for the technical team to manage, along with the flow setup.

I use the solution to integrate different processes in our company. For any integrations that require mapping on top of SAP IDoc, I use PI/PO.

The solution helps streamline B2B processes in our company, considering that we deal with a lot of 3PL integrations. SAP helps deal with areas like dispatch advice and IDocs, along with aspects related to the mapping that my company does with the help of SAP PI/PO, which is something mostly based on the recipient's requirements. My company has not exposed PI/PO to external parties. My company has another gateway that gets connected with SAP PI/PO, another third party we deal with, but PiP is currently only used for mapping purposes in our organization.

I Just provide the specifications to my company's team, and they take care of SAP PI/PO.

I don't have the experience to speak about how SAP Process Orchestration's user interface has enhanced our company's productivity.

I recommend the product to those who plan to use it, especially those who use SAP ECC. If possible, users should possibly use it for external or third-party connections. Users need to have their architecture and framework correct to be able to use integration platforms in their environment.

I rate the overall tool an eight to nine out of ten.

I use the solution in my company for connectivity to third-party systems, and it is simply for the processing of transactional data.

The solution's most valuable feature is its Java Message Service, which is fantastic. One of the key features of Java Message Service is the fact that it offers guaranteed delivery.

I think the big improvement required in the tool stems from the fact that the whole issue around it is that we have some downtime failures during upgrades and patching. The downtime phase is when we do maintenance, upgrades, backups, and then, of course, on the operating system side, when we need to do security patches and all those things. The whole improvement should be about automating those updates so there is no downtime.

I have been using SAP Process Orchestration for fifteen years. I am an end-user of the tool.

It is a very stable solution. Stability-wise, I rate the solution a nine and a half out of ten.

Scalability-wise, I rate the solution an eight out of ten.

We have around six developers who develop stuff with the help of the tool. It is basically used to functionally move data from SAP into other systems, so it is not really the users that log on to the system.

The solution's technical support is good. I rate the technical support an eight out of ten.

Positive

The product's initial setup phase was very straightforward.

The solution is deployed on an on-premises model and on AWS Cloud.

The solution can be deployed in about a day. There are configurations that you need to do, and after that, there are some connections to other applications and stuff, so that will take you additional, probably three to four days.

I think I have faced some issues related to the big basic connectivity to third-party tools, and I felt it was time-consuming. We have to create fire firewall rules and security group access.

My company has not used AI in the tool.

The performance of data processing has increased.

Normally, you will have to choose CPU-based licensing. I don't know the tool's actual cost, but it is expensive compared to other solutions or its direct competitors.

Compared with the other integration platforms, the functionalities and stability in SAP Process Orchestration are aspects we need to consider. I rate the tool price a five out of ten.

My company chose SAP Process Orchestration over other products in the market because our ERP system is on SAP, so it makes sense to go with it.

With the process automation feature, we could get data on the pricing of the stores in real-time. We could get sales back into SAP's system in real time. We can also get reports back into our SAP system. We could near real-time processing.

Any IT product is not seen as a financial benefit, but it gives them the luxury of ensuring the integration of data with other systems.

My company takes care of regular maintenance, patching, and upgrades with the help of one in-house member.

If you don't have any integration, you have to manually move the data.

I recommend the tool to others.

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

In my company, we normally use the solution to integrate all of our internal applications within our organization. As per SAP, the solution's lifecycle may end by 2027. My company plans to replace SAP Process Orchestration with a newer version of SAP product, which is a cloud-based version.

The most valuable features of the solution stem from the EDI integrations provided by SAP. Some of the inbuilt integrations, as well as its components, like the mapping engine and other items, like the available adapters, make for some of the valuable features of the product.

There is a lot to improve in the product, but the product itself is going into the sunset, and SAP is no longer investing in the product.

My company is no longer looking for any features in SAP Process Orchestration since we are just planning to get support from it until we move to the new cloud version of it. In general, my company hasn't evaluated anything related to the product since we just stopped investing in it at least six months back.

SAP needs to improve a lot in terms of the orchestration part so that more adapters can be provided to users, which are areas where the solution has downsides. SAP needs to improve in terms of providing connectivity to cloud providers like AWS, Azure, and other cloud providers.

The product's scalability is an area with certain shortcomings where improvements are required.

I have been using SAP Process Orchestration for twelve years. I am a customer of SAP. I use the solution's latest version.

Stability-wise, I rate the solution a seven out of ten.

It doesn't have any scalable solution. Scalability-wise, I rate the solution a one out of ten.

Ten to fifteen people use the solution, but there is a need to consider the fact that it connects multiple business processes, which is one of the critical aspects when it comes to the product.

The product is used daily in my company.

I rate the technical support a six out of ten.

Neutral

I rate the product's setup phase a nine on a scale of one to ten, where one is difficult and ten is easy since it is a very easy process.

The solution is deployed on the cloud and on-premises.

The solution can be deployed in a week.

One person is required in my company to take care of the product.

A third-party involvement is required for the installation of the product.

My company deals with different pricing models of the product, according to which we don't pay for the solution directly, but we do pay for the maintenance part.

When it comes to the maintenance part, there are two ways of maintaining the product. The product's maintenance phase includes the maintenance of the application and the maintenance of the infra. For the maintenance of the application, my company has around seven people, and for the maintenance of the infra, my company has around ten people.

I would not recommend the solution to those who plan to use it. I don't think anyone would consider the product anywhere since SAP itself doesn't give much consideration to Process Orchestration.

I rate the overall product an eight out of ten.

We use the product to integrate with several SAP and non-SAP systems for data transmission.

SAP can transform the data into any form. It is compatible with only IDOC. However, we can integrate it with third-party systems to convert the data into different formats.

We encounter challenges while connecting to MQTT and MQDD adapters. We have to purchase some adaptors to connect to the MQTT broker. They could enhance this particular area.

We have been using SAP Process Orchestration for eight years.

It is a stable product. We don't encounter any stability issues.

A cloud platform would be better than on-premises for a larger volume of data.

We receive help from the technical support team whenever we raise tickets via email. We can schedule in case of any crucial issues. We also share credentials in a very secure manner with them to check for problems and resolve them. However, they could respond faster. At present, they take a day or two to reply. We don't get an immediate assistant. It could be improved.

Our organization decided to work with SAP. I was eager to work with SAP modules during the migration process.

The complexity of the initial setup depends on various scenarios. It is simple to transfer files. We configure the business system with hostname code details and establish a connection using the firewall. It takes a few months to complete the system process.

I rate SAP Process Orchestration an eight out of ten. I look forward to working with cloud platforms.

Our use cases are all related to integration, from ERPs to third parties. 

The main benefit is that the solution is low maintenance. Moreover, it's the license cost is very low because it's part of the package. The maintenance is standard maintenance. And the updates are regular. So there's a regular update and you can choose whether you want to do those updates or not.

SAP Process Orchestration has a higher version of the CPIs and all that, which is a part of APs. But, it's on a case-to-case basis, whether there is any business requirement for it. But right now, whatever the process orchestration offers, it's good for our business requirements.

The solution is really easy to use and native to our SAP ERP. For me, the ease of mapping is valuable. 

Moreover, it is very native to ERP and can integrate with any third-party tool or any other system required, which has been valuable. 

There is room for improvement in terms of performance.  

Another area of improvement is technical architecture. 

I have been using this solution for 10 to 12 years. 

It is a highly stable solution.

It is scalable, but there can be performance issues with high data volume or traffic, especially during month ends.

SAP's technical support is very good, depending on your contract. It's based on the support contract; if there's active support available, it's a ten.

Positive

The initial setup is easy. We need to follow standard SAP procedures. Currently, we work with the cloud version.

We are the system integrators. Deployment steps are standard SAP procedures. We build a system, download the software from the SAP standard site, configure mappings with third-party and source ERP systems, and we're good to go.

For a new build, one database resource and three to four people for source and normal PI configuration should suffice.

It is easy to maintain the solution. You just need to follow standard SAP procedures.

It comes as a part of the SAP package, and no additional license is required. MuleSoft, on the other hand, is very costly.

We've started working with MuleSoft, but we're still exploring it.

If you have SAP ERP, SAP Process Orchestration is the best solution. It allows easy integration across your landscape and with third-party systems.

Overall, I would rate the solution a nine out of ten.