Technically, an SAP Ariba implementation is well under control. Interfaces to S/4HANA or ECC are standardised and the modules are proven. The difficulty lies elsewhere: procurement, finance, IT, business units and suppliers pursue different goals, scope grows unnoticed, and leadership expectations do not match what a first release can deliver. That is where it is decided whether SAP Ariba is actually used a year later or merely running.
We supported the process and system rollout of SAP S/4HANA and SAP Ariba for a global EPC group across more than 25 countries. We have also reviewed published experience from comparable implementations, such as Transport for London's lessons-learned report on its source-to-pay programme with SAP Ariba. The patterns are strikingly similar.
Orchestrating stakeholders: the core of any SAP Ariba implementation
More parties depend on SAP Ariba than on most IT projects:
- Procurement wants spend visibility and control.
- Finance wants clean invoice processes and compliance.
- IT wants stable interfaces and little custom logic.
- Business units want ordering to be as simple as possible.
- Suppliers want no additional effort.
These interests do not balance themselves. You need a sponsor from senior management who resolves conflicts, and a steering committee that actually meets. At Transport for London, the sponsor changed and the steering committee stopped meeting from early 2022. The report explicitly cites this as a reason for weakening support. Conversely, involving around 60 representatives from procurement and enabling functions in process design strengthened adoption.
Suppliers are part of this. They can use SAP Business Network with a free Standard account. The Enterprise account, according to SAP, involves a fixed subscription fee plus volume-based charges. Suppliers will ask about this, so have the answer ready.
Cutting scope deliberately
The most common cause of delay is scope that grows along the way. Agree early and in writing:
- direct or indirect procurement, or both,
- which modules go into the first release and which come later,
- which entities and countries go live in which wave,
- which deviations from the SAP standard are truly necessary.
Every scope change should be checked against the original business case, including dependencies on other initiatives such as an S/4HANA conversion in procurement. At Transport for London, repeated reprioritisation meant parts of the business case were not delivered. In a multi-country rollout, only a common template with few local additions keeps scope manageable.
Setting expectations in stages
Leadership often expects full transparency and quick savings from go-live. Yet value grows with adoption and the number of connected suppliers, and spend analytics are only as good as the data behind them. Define what should be measurable after the first release, such as the share of purchase orders through SAP Ariba, the number of connected key suppliers or approval cycle times, and what comes later.
What comparable projects often miss
- Data ownership: At Transport for London, contracts were missing from the system after go-live because ownership and tracking of the data upload were not defined. Some users could not raise requisitions as a result.
- Training by audience: Training videos worked for most users there, but not for all. Hypercare was extended from two to six months.
- Operating model: The support model was only in place months after go-live. Until then, the project team carried the load and requests piled up.
Next steps for decision-makers
- Appoint a sponsor and set up a steering committee with fixed dates.
- Map stakeholders, including suppliers, with their goals, concerns and decision rights.
- Fix the scope of the first release and check changes against the business case.
- Agree expectations in stages with measurable KPIs.
- Settle data ownership and the operating model before go-live.
Our SAP Ariba consulting and our references show how we set up projects like this. Our procurement assessment creates a solid basis for stakeholders, scope and timeline. Or book an initial consultation directly.