3.4 out of 5 (16 Ratings)

16 Verified Reviews

Ariba Procure-to-Pay

Ariba support is impressive

This was not a typical SAP engagement - the Ariba team is far more agile and helpful

Ariba Procure-to-Pay

SAP Ariba

Most of the things worked during implementation

Ariba Procure-to-Pay

Implementation was some heavy lifting by IT on account of newer technology

The technology was new and less stable.

Ariba Procure-to-Pay

Another stand-alone solution without an interface.

We decided on moving from on-prem SAP Frictionless for eContract and eSourcing in September, 2015, agreeing on an implementation date of 01APR2016. It took until late December, 2015 to complete negotiations, so the implementation team was left with three months to 'lift and shift' from Frictionless to the Ariba Contract Management and sourcing solutions. Neither solution is interfaced with our homegrown procurement solutions, or even other implementations of SAP within the enterprise. Central sourcing organizations are not keen on using the tool for most transactions.

1

Ariba Procure-to-Pay

Implementation went quite smoothly but the interface could be more user friendly

The interface could be more user friendly and intuitive.

Ariba Procure-to-Pay

Product is good but could be better

Support could have been better

Ariba Procure-to-Pay

Need to drive buy in from users

hard to get buy in from users to do their own procurement

1

Ariba Procure-to-Pay

Ariba is not a simple cloud app which works seamlessly with other ERPs. Plan for support.

Ariba lifecycle to solve a service request can be upto 121 days after they agree or acknowledge this is an issue. Also Ariba did not turn out to be a business owned application with little IT support as the integration was not mature.

Ariba Procure-to-Pay

Don't overthink and stay with the out-of-the box features

Ariba offer very robust out of the box features that will cover the end-to-end P2P cycle. However, any customization to the product will cause a lot of up-keeps and customizations may fail/break when new releases came out. Therefore, I would suggest organizations / Ariba clients to stay with the suggested best practices and out of the box features to avoid maintenance nightmares.

Ariba Procure-to-Pay

Ariba and SAP Procure to Pay

Ariba was not as tightly aligned with SAP ECC as marketed. We were telling SAP how to do more complex integrations and providing specs for them to work against, on functions that we felt should be basic and already in place. SAP worked with us to create the interfaces, but it greatly slowed the timing of the project.