Running SAP Ariba as a Service: Supplier Onboarding from 21 Days to 5
CUSTOMER
An enterprise buyer running SAP Ariba across purchase-to-pay, with a supplier base of more than 1,200.
LOCATION
United States
PROJECT
SAP Ariba Application Managed Services
TECHNOLOGY
SAP Ariba, Ariba Network
KEY RESULTS
CHALLENGES
Five things were true at once, and each one made the others harder.
Purchase-to-pay ran manually and it ran slowly. Suppliers hadn’t adopted the Ariba Network, so the platform held part of the process and the rest happened off it. Maverick spend was high, which is the predictable result: when the agreed channel is slow, people route around it. The system went down often enough for downtime to be a known quantity. And spend visibility was poor, which meant none of the four problems above could be sized.
That last one matters most. You can’t fix what you can’t count, and the reporting wasn’t good enough to tell anyone how bad the other four were.
SOLUTIONS
- Proactive monitoring. Health checks around the clock instead of waiting for a user to report an outage. Downtime fell by 90%.
- Automated invoice processing, which removed 70% of manual invoice handling.
- A supplier enablement drive. 1,200+ suppliers onto the Ariba Network in six months. That is roughly 200 a month, or about ten every working day, sustained for half a year. A number like that is not a campaign somebody runs alongside their day job.
- Automated supplier scorecards. On-time delivery went from 65% to 88%. Put differently: about two thirds of the late deliveries stopped being late.
- A supplier self-service portal, which took 30% off buyer workload.
RESULTS
Supplier onboarding went from 21 days to 5. Sixteen days out of a three-week process, and about four times faster than where it started.
Two of these numbers are worth reading together. Onboarding got four times faster, and the supplier base grew by 1,200. Speed usually costs quality somewhere, and on-time delivery went up instead.
Why It Worked
Ariba was already implemented. What changed was who was watching it, and how often.
An implementation ends. An application managed service doesn’t, and procurement platforms drift in ways a go-live cannot anticipate: suppliers churn, catalogues age, approval chains move as people move, and the vendor ships on its own calendar.
The onboarding number is the clearest case. Twenty-one days is not a technical limit. It is what onboarding takes when it belongs to nobody in particular, and five days is what the same platform does when it belongs to somebody.
Modernizing a complex utility SAP environment?
Request a utility SAP readiness assessment
