We primarily use this for integration between multiple SAP products, and between SAP and other systems. Some integrations are standard SAP packaged flows, some are modified standard packages and others are bespoke where one endpoint is not a SAP system. Some examples are SuccessFactors to S/4, S/4 to planning systems and plant systems back to S/4 maintenance.
Pros
It is very reliable
It generally does not require maintenance
Pre packaged standard integration flows which update with products
Cons
There is a steep learning curve. The interface is not intuitive
When maintenance is required, eg certificate updates it is difficult to follow the documentation
It is easy to build poor integration flows that are hard to follow
Debugging tools that are built in are not sufficient, you must instrument flows as part of the build
Likelihood to Recommend
It is very good for SAP to SAP and quite powerful for other API calls. Good if you have good development resources
VU
Verified User
Manager in Information Technology (Mining & Metals company, 501-1000 employees)
We use the SAP Integration Suite to create interfaces between non-SAP internal applications, internal SAP solutions, and external SaaS solutions. It is very user friendly and using the iFlow packages, it is possible to group the interfaces as to get the full overview over the outgoing and incoming data and how the interfaces relate to each other
Pros
iFlow packages for overview
Generating alerts
Developing new flows
Cons
Documentation opportunities
Not sure
Not sure
Likelihood to Recommend
It is well suited for internal applications interfacing with each other and internal applications interfacing with external SaaS applications, but for one of our finance processes, we actually use SAP Integration Suite to provide interfaces between two SaaS applications, but we’re struggling to get it to work, and it’s not working at all right now
VU
Verified User
Consultant in Information Technology (Oil & Energy company, 5001-10,000 employees)
We use the SAP Integration Suite for integrations with SuccessFactors and also for a lot of inbound and outbound IDOC interfaces. This helped us resolve the issue we had with many terminals posting sales data into SAP ERP system. We also use CPI for a lot of File Transfers using FTP.
Pros
IDOC Integration
EDI Mapping
FTP transfers
Cons
Better monitoring capabilities
Likelihood to Recommend
It is most suited where an integration involves IDOCs and SAP relevant APIs. We had issues with integrating our ERP system with external terminals and we used CPI to integrate the SAP system with external Terminalling systems. However, in scenarios where one of the end systems is not SAP, it might not be the best tool.
This is our first year integrating the integration suite. Previously, we had Boomi as our middleware. Since making the transition, our organization has better visibility to not only manage existing integrations but also optimize current business processes. For example, we have recently changed benefits providers. This provider has very specific data mapping requirements. The integration suite allows us to leverage our EC environment and, almost seamlessly, ensure concrete data integrity. It also supports the relationship between our organization and the vendor.
Pros
Better visibility on connections
Neo and cloud foundry options
Strengths relations with vendors
Affordable cost with licensing
Cons
Integration dashboard
More clear connector options
Likelihood to Recommend
Well suited for: -new/existing vendor integrations -cloud to cloud connections -downstream processes w/ SFTP
Integration suite is great for vendor connections between your HRIS platform (EC) and downstream vendors such as a retirement or benefits vendors, payroll management, or surveyor. It is very clear on both sides of the aisle what is and is not required to make a successful connection from one end point to the other.
In my opinion, SAP Integration Suite's version management is not up to industry standards and lacks features. Tagging and Release processes are very basic. You need to come up with a versioning scheme for your external APIs to ensure users using the latest release and not a dev release. The development itself and data mapping and transformation a top priority. As always, with SAP, licensing is a little bit of an issue, but solvable. With over 1 year of productive integrations with CPI, we can say that we have had a very positive experience when it comes to stability and performance within CPI. When taking heavy coding in Groovy, the debugging capabilities are up to standards. Although you should use a full IDE for that.
Pros
Ease of use and lots of connectors
Availability of standard integration content
Cons
Version management is not up to industry standards and is lacking features.
The tagging and release processes are very basic.
Likelihood to Recommend
If you already have working middleware and strong developer powers, check whether you really need this integration platform. Make sure that you evaluate the CPIs' existing integrations to save developing costs. It can really save time and costs.
VU
Verified User
Analyst in Professional Services (Mining & Metals company, 5001-10,000 employees)
We have implemented SAP IS in both sap-to-sap and non-sap-to-non-sap. We will have more custom integrations solution for complex integration once we have cc BPA on perm. Designed and rebuilt them with SAP IS. The only thing we see the product should have provided are native git support and native CI/CD steps to achieve integration use cases. Even with these limitations, we have around 160+ integrations that say the product is good. Please add more dev tools to the product line. Like the groovy script, develop and debug them while integration is running.
Pros
sap to SAP integration.
when we have complex integration use cases.
Cons
native git support.
groovy script debug in interface simulation
native ci/cd support.
multi region support.
increased availability from 99.5.
local run time of integration suite.
Likelihood to Recommend
It can fit well for sap-to-sap use cases. And this is soo quick to build multi-API calls and complex integrations. And have multiple API calls and orchestrate final API call needs. Having more customization scope and having a good developer tool to support is as much required as the tool.
