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.
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.
AVP IT at a construction company with 501-1,000 employees
Real User
Top 20
2024-01-19T09:39:20Z
Jan 19, 2024
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.
Technological Partner at Code-10 IT Consultants SL
Real User
2021-12-21T10:07:00Z
Dec 21, 2021
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.
We are using the solution for authentication purposes. The product is a useful solution for integrations with any internal systems or any third-party systems as we're connecting SAP to our end-user.
Global Integration Lead & Architect at a manufacturing company with 10,001+ employees
Real User
2021-09-20T15:54:35Z
Sep 20, 2021
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.
Infrastructure Specialist at a energy/utilities company with 1,001-5,000 employees
Real User
2021-01-27T10:01:16Z
Jan 27, 2021
It's a technical product. We primarily use the solution for our infrastructure. It's a mid ware. We use it due to the fact that we need to deal with messages between our system and external systems. We need to construct communication channels, interface with them to define how much time or how many times we need to complete each interaction between the system. We also need it for monitoring issues, and we use Solution Manager to monitoring interfaces.
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.
Software Engineer at a manufacturing company with 1,001-5,000 employees
Real User
2020-07-19T08:15:00Z
Jul 19, 2020
Our primary use case is for the business work clause. Even though there could be multiple cloud-based applications in real-time, doing on-premise work, people need some kind of security within their internet server and to do transactions. SAP Process Orchestration would encourage you to translate and do many activities. It has few disabilities. We can use standard EBA technology to transfer the invoices and make purchases.
SAP Process Orchestration Team Lead at a retailer with 10,001+ employees
Real User
Top 10
2020-06-04T09:41:23Z
Jun 4, 2020
We have 2 stances of the SAP PO 7.5 SP14 Java only and it is installed on-premise using IBM Hardware to support our on-premise SAP Applications and an instance installed on AWS to integrate our cloud application with other cloud application. We use the solution for application integration and transforming of data. Decoupling of systems is a feature of SAP PO that allows us to integrate systems without having to care about the data formats , communication protocols or security features of other systems on the bus. As a retailer, all our transnational data need to feed into our SAP system and visa versa to non - SAP systems . Example of this, would be raw point of sale data from the POS system to convert to XMLs and integrate it into the SAP system. We have a team of six developers that does development and support.Support issues are related to data and connectivity . Extrapolation data from other application systems are key to the proactive scaling of the system . We have built close to 700 Integration scenarios and process on average 1.2 m transaction per day.
Solution Architect - SAP Banking at a financial services firm with 10,001+ employees
Real User
2020-03-22T06:49:12Z
Mar 22, 2020
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.
Partner & SAP Netweaver Solution Architect at a tech services company with 11-50 employees
Real User
2020-03-04T08:49:00Z
Mar 4, 2020
I have been a solution architect since 2005. I have a lot of experience with SAP Process Orchestration. I have a lot of experience with many kinds of integration between all kinds of processes. SAP Process Orchestration is the tool we chose to use to help us effectively design and improve workflows.
Primarily, my customers are using the solution for integration, however, there are so many possible scenarios. Some of them are using RFC, IDOC, Database, SOAP, File or REST API integrations, for example. I've had lots of use cases over the past eight or nine years.
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.
SAP NetWeaver Process Integration facilitates the integration of business processes that span different departments, organizations, or companies. SAP PI is based on general standards so as to enable 3rd-party systems to be integrated. At the center of SAP PI is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). Irrespective of the scenario used, the application-specific contents are transferred in messages in user-defined XML eXtensible Markup Language) from the sender...
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.
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.
I use the solution in my company for connectivity to third-party systems, and it is simply for the processing of transactional data.
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.
We use the product to integrate with several SAP and non-SAP systems for data transmission.
My organization uses the Java system on SAP Process Orchestration.
Our use cases are all related to integration, from ERPs to third parties.
The solution is mainly used for integration.
The solution is used for file servers, soft services, and other RSC services also connected with SAP Process Orchestration
We use the solution to integrate multiple projects with SAP or non-SAP applications.
I primarily use Process Orchestration for integration.
SAP Process Orchestration is used for file transfers or file conversions before financial data get sent into SAP.
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.
We are using the solution for authentication purposes. The product is a useful solution for integrations with any internal systems or any third-party systems as we're connecting SAP to our end-user.
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.
It's a technical product. We primarily use the solution for our infrastructure. It's a mid ware. We use it due to the fact that we need to deal with messages between our system and external systems. We need to construct communication channels, interface with them to define how much time or how many times we need to complete each interaction between the system. We also need it for monitoring issues, and we use Solution Manager to monitoring interfaces.
This solution is good for specific customers who are not on the cloud.
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.
Our primary use case is for the business work clause. Even though there could be multiple cloud-based applications in real-time, doing on-premise work, people need some kind of security within their internet server and to do transactions. SAP Process Orchestration would encourage you to translate and do many activities. It has few disabilities. We can use standard EBA technology to transfer the invoices and make purchases.
We have 2 stances of the SAP PO 7.5 SP14 Java only and it is installed on-premise using IBM Hardware to support our on-premise SAP Applications and an instance installed on AWS to integrate our cloud application with other cloud application. We use the solution for application integration and transforming of data. Decoupling of systems is a feature of SAP PO that allows us to integrate systems without having to care about the data formats , communication protocols or security features of other systems on the bus. As a retailer, all our transnational data need to feed into our SAP system and visa versa to non - SAP systems . Example of this, would be raw point of sale data from the POS system to convert to XMLs and integrate it into the SAP system. We have a team of six developers that does development and support.Support issues are related to data and connectivity . Extrapolation data from other application systems are key to the proactive scaling of the system . We have built close to 700 Integration scenarios and process on average 1.2 m transaction per day.
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.
I have been a solution architect since 2005. I have a lot of experience with SAP Process Orchestration. I have a lot of experience with many kinds of integration between all kinds of processes. SAP Process Orchestration is the tool we chose to use to help us effectively design and improve workflows.
Primarily, my customers are using the solution for integration, however, there are so many possible scenarios. Some of them are using RFC, IDOC, Database, SOAP, File or REST API integrations, for example. I've had lots of use cases over the past eight or nine years.
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.