NetWeaver Process Integration vs. SAP Integration Suite

I would recommend using NetWeaver Process Integration with an SAP application only. SAP ISU/ECC can integrate with the PO very well to interact with non-SAP systems. It's best suited for extracting data from SAP systems into flat files, encrypt it, and sFTP to any 3rd party vendor.

Incentivized

In our case to have a such a poweful middleware in the cloud, give us a lot of benefits such as maintenance and support. In the integration part to be able to connect SAP and Non SAP applications makes SAP Integration Suite a good investment when our master data in this case is in S4HANA. Less appropriate is that sometimes the updates in production tenant failed and they have to downgrade or repair the issues. Affecting the usage of the tool. I guess SAP team have to be more aware of performing the changes and tested well on development environments and then when they know for sure that is the correct way to go with the update put it in production.

Incentivized

• Combined advantages of advanced business application programming (ABAP) and Java
• SAP with [other] SAP products and SAP with other solutions
• Real-time customer service
• Cascade data model

Incentivized

• Enhanced API management features that allow now the integration with a multitude of data feeds and rating agencies
• Immediate evaluation of potential issues and configurable thresholds and automatic notifications.
• The application will monitor all aspects of compliance and update them automatically for several jurisdictions at time

• Complicated UI. Could be more simple.
• Need more clear instructions on development environment.
• Hard to debug errors.
• Have many dependencies like Basis support.

Incentivized

• Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
• Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
• Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective

Incentivized

It is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.

Incentivized

The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.

Incentivized

It works great for integrating SAP applications. Without the box connectors and integration flows, the speed of development is fast. However, It has challenges in connecting other non-sap applications.

Incentivized

Support is hard to reach and takes a long time to get a response.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

I was not included in selecting product process

Incentivized

SAP Integration Suite was already part of our SAP stack, part of Business Technology Platform, with out-of-the-box integration with S/4 HANA transactional and ERP system that we are using as our main back-end. Thus, we are achieving significant Total Cost Optimization benefits or running both solutions on the same platform, hosted on Azure cloud.

Incentivized

• It reduces integration costs.

Incentivized

• In the long run will enable us to undeploy our on premise solution
• As long as integration suite doesn't support all capabilities PO has complete migration is hard
• Will probably be cheaper than our on premise solution when we are completely migrated

Incentivized