Item: NetWeaver Process Integration
Rating: 7
Author: Verified User

Use Cases and Deployment Scope

NetWeaver Process Integration is being used as an integration layer between SAP applications is our landscape. It's being used by our department only. PO has built-in integration with SAP, and that why it's our preferred choice to integrate SAP applications. It's also being used as a gateway to exchange files on file-based integrations.

Pros and Cons

Integration between SAP applications
Supports Active directory integration.

Has limitations on consuming different types of Queues. Like JMS queue.
Has limitations on datatypes and size of the message in the queue
Have limitations in connecting to Kafka. This can be solved with 3rd party adapters
Have limitations on processing large files.

Return on Investment

Development cycle is fast on PO .

Alternatives Considered

webMethods Business Process Management and Apigee Edge

Support Rating

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.

Key Insights

Do you think NetWeaver Process Integration delivers good value for the price?

Yes

Are you happy with NetWeaver Process Integration's feature set?

Yes

Did NetWeaver Process Integration live up to sales and marketing promises?

Did implementation of NetWeaver Process Integration go as expected?

Would you buy NetWeaver Process Integration again?

Yes

Other Software Used

Apigee Edge, webMethods Business Process Management

Likelihood to Recommend

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.

SAP PIPO

Overall Satisfaction with NetWeaver Process Integration