SAP Ariba Supplier Risk

From my perspective as a Principal Cloud Infrastructure Analyst, my overall experience with SAP Ariba has been positive, especially after the C2 transition stabilized. Reliability and uptime have been strong for core procurement activities (intake, approvals, PR/PO processing, invoice handling), and the platform has supported business continuity well once users were aligned to the new process controls. Reliability & Uptime: During the C2 go-live period, the team had to enforce the new PO number usage for invoicing (Wave 2 communication), I saw that if a supplier invoice did not include the updated PO number, it could not be processed and had to be reissued. This control improved data quality and our monitoring, but created short-term operational friction. After the freeze-period communications, we had to push unsubmitted invoices through Accounts Payable quickly to avoid payment delays. This showed that the platform could support return-to-BAU, but only with disciplined coordination/assessment between PCOs, AP, and supplier communications. Support Quality: Support channels were clearly defined (procurement support paths, AP support paths, role-based resources), and that helped incident management and users resolve issues faster. I have directly observed that role-specific job aids and training resources have reduced incidents and repeated tickets for common topics (approvals, status tracking, invoice handling, access). Integration Success: I observed effective integration of Ariba operating processes with SSO, role provisioning through SAM approvals and dual user experience (Guided Buying and Classic UI) for different user types. Industry-observed: Enterprise procurement platforms perform best when access governance, approval routing, and invoice control standards are enforced consistently.