SAP SRM Third-Party Support: Preserve Supplier Relationship Management Without Forced Migration to SAP Ariba Cloud

What SAP SRM Third-Party Support Actually Covers

SAP Supplier Relationship Management (SRM) is the on-premise SAP procurement platform providing end-to-end procurement process management beyond what SAP ECC MM provides. SAP SRM's core functional areas cover: Self-Service Procurement (SSP) — the employee-facing shopping catalogue for indirect goods and services procurement, including catalogue management via Open Catalogue Interface (OCI) and punchout to external supplier catalogues; Strategic Sourcing — including Request for Quotation (RFQ) management, reverse auctions, bid comparison, and supplier award; Contract Management — including global outline agreements, contract hierarchies, item-level contract conditions, and contract compliance monitoring; Supplier Evaluation — performance scoring, approved supplier lists, and supplier qualification workflows; and Service Procurement (Services Management) — timesheet capture, service entry sheets, and external workforce management. All of these functions integrate with SAP ECC via the Business Function Sets and integration components for purchasing documents, financial accounting, and supplier master data.

Third-party support for SAP SRM covers the complete application stack: SAP SRM Application Server (ABAP stack), SAP NetWeaver portal infrastructure hosting SRM self-service interfaces, Oracle or MaxDB database instance, SRM-ECC integration via RFC and IDOC, and SAP SRM master data objects. When your SAP SRM environment moves to TPS, GoVendorFree engineers provide incident resolution, catalogue management support, workflow configuration advisory, SRM-ECC integration troubleshooting, and contract management support — without SAP's forced patch compliance requirements that risk disrupting live procurement operations.

SAP's commercial position on SRM is unambiguous: SAP SRM 7.0 EHP3 reached end of mainstream maintenance in December 2020, and SAP's current position is that SRM has no further development roadmap. SAP's official guidance is migration to SAP Ariba Procurement cloud. The reality: SAP Ariba Procurement is a cloud SaaS solution with a fundamentally different technical architecture, integration model, and procurement workflow engine. The migration from SAP SRM to SAP Ariba is not an upgrade — it is a complete procurement process re-implementation. SAP TPS provides the exit from SAP's maintenance cost escalation while the Ariba migration ROI case is properly evaluated.

SAP SRM Version Support Matrix

Every version of SAP SRM is past SAP's mainstream maintenance end date. Organisations still paying SAP annual maintenance on SRM 7.0 are paying for a product receiving no new features, no functional improvements, and only critical security patches under Extended Support — which SAP now charges an additional 2% per year beyond standard 22% maintenance. The financial case for SAP SRM TPS is straightforward: TPS delivers 50–65% savings from day one on a product SAP has already functionally abandoned.

Why SAP SRM Customers Move to Third-Party Support

Three structural barriers consistently drive SAP SRM customers to TPS: SAP Ariba migration complexity, SRM-ECC integration lock-in, and contract management data re-platform costs.

Barrier 1 — SAP Ariba Procurement Cloud Re-Implementation Scope

SAP Ariba Procurement cloud — consisting of Ariba Buying and Invoicing, Ariba Sourcing, Ariba Contracts, and Ariba Supplier Management — uses a cloud-native SaaS architecture with REST APIs, Ariba Network for supplier connectivity, and a cloud-based procurement workflow engine that has no direct equivalence to SAP SRM's ABAP-based process configuration. SAP SRM procurement workflows, BAdI enhancements for approval routing, custom RFQ evaluation criteria, and punchout catalogue configurations cannot be migrated to Ariba via automated tooling. Each SRM procurement process must be re-designed and re-configured in Ariba's platform. For organisations with 30–80 custom SRM workflow configurations, complex ECC integration scenarios, and 500–5,000 active supplier relationships, the Ariba re-implementation programme costs £1M–£5M over 18–36 months. TPS delivers an immediate 50–65% reduction on SAP SRM support fees while that investment is properly scoped.

Barrier 2 — SRM-ECC Integration and Backend Document Lock-In

SAP SRM is deeply integrated with SAP ECC through the Business Function Sets for SRM, RFC connections for supplier master data and material master synchronisation, IDOC exchanges for purchase order replication, and the Extended Classic Scenario or Classic Scenario integration modes that control where purchasing documents are created and managed (SRM or ECC). Organisations that have implemented SAP SRM Extended Classic Scenario — where purchase orders are created in SRM and replicated to ECC — have a complex bidirectional integration architecture with custom enhancement spots and BAdI implementations managing document flow. Decomposing this integration before an Ariba migration requires complete re-design of ECC purchasing document management, adding £300K–£1.2M to the Ariba total cost of ownership. TPS stabilises the SRM-ECC integration at reduced cost while the Ariba architecture is designed from scratch.

Barrier 3 — Contract Management Hierarchy and Compliance Lock-In

SAP SRM Contract Management manages global outline agreements, local contracts, and contract hierarchies that govern procurement compliance across business units and geographies. SRM contracts link to SAP ECC purchasing info records, outline agreements, and source lists — creating a tightly integrated contract-to-purchase-order compliance framework. For organisations with 5,000–50,000 active SRM contracts managing £100M–£2B+ in annual procurement spend, the contract data migration to Ariba Contracts requires complete contract hierarchy re-design, contract data cleansing, and ECC integration re-architecture. UK organisations subject to PCR 2015 (Public Contracts Regulations) and the Procurement Act 2023 have contract transparency and documentation obligations embedded in SRM contract management workflows. Migrating these compliance workflows to Ariba requires re-assurance with procurement legal teams and, for central government bodies, Cabinet Office procurement team sign-off. TPS preserves the compliant contract management environment at reduced cost while this governance process is completed.

SAP SRM TPS by Industry

Public Sector and Central Government

Central government departments, NHS Trusts, and local authorities are among the largest SAP SRM deployments globally. SAP SRM implementations for public sector typically include complex approval workflows for Cabinet Office MEAT (Most Economically Advantageous Tender) criteria, PCR 2015 framework agreement management, and integration with Crown Commercial Service (CCS) framework catalogues. The Procurement Act 2023 introduces new transparency obligations for above-threshold contracts that are embedded in SRM contract management workflows. SAP TPS for public sector SRM preserves these PCR/Procurement Act-compliant workflows at reduced cost. Typical public sector SRM TPS saving: £160K–£420K per year.

Manufacturing and Automotive

Global manufacturers use SAP SRM for strategic sourcing of direct materials, MRO procurement, and service procurement. Automotive OEMs and Tier 1 suppliers run SRM alongside SAP ECC PP/MM with complex supplier scheduling agreement (SA) management, consignment procurement, and ERS (Evaluated Receipt Settlement) processes integrated with SAP SRM service entry sheets. The SRM-ECC integration for direct materials procurement in manufacturing environments is one of the most complex integration scenarios — disrupting this integration during an Ariba migration creates direct supply chain risk. Manufacturing SRM TPS typically saves £180K–£560K per year.

Financial Services and Insurance

Banks and insurers use SAP SRM for IT and professional services procurement with complex approval chains, supplier qualification workflows under FCA PS10/16 operational resilience requirements, and contract management for critical third-party suppliers. FCA SS2/21 (Operational Resilience) and PS21/3 require financial services firms to map and test important business services and their dependencies on third-party suppliers — a process that requires stable, auditable supplier management records. SAP SRM TPS preserves supplier management data continuity at reduced cost during any third-party risk management modernisation programme.

SAP SRM TPS Cost Model

SAP SRM support fees are charged at 22% of SAP SRM licence value annually, with Extended Support adding an additional 2% per year. GoVendorFree calculates your TPS saving across all SAP SRM and associated ECC licences in scope. Indicative four-profile saving model:

What GoVendorFree SAP SRM TPS Includes

• SRM Application Server support — incident resolution for SAP SRM ABAP stack, workflow engine failures, and SAP NetWeaver hosting infrastructure
• Self-Service Procurement support — shopping cart troubleshooting, OCI punchout catalogue configuration advisory, and approval workflow issue resolution
• Strategic Sourcing support — RFQ management troubleshooting, bid evaluation configuration, and sourcing event workflow issues
• Contract Management support — contract hierarchy troubleshooting, contract release order issues, and contract expiry alert configuration
• SRM-ECC integration support — RFC connection monitoring, IDOC replication troubleshooting, purchase order synchronisation, and ECC backend integration advisory
• Security Notes advisory — SAP Security Note assessment for SRM and NetWeaver ABAP; mitigating control recommendations for critical vulnerabilities
• 15-minute SLA response — P1 critical procurement system issues receive engineer engagement within 15 minutes, 24/7/365

SAP SRM TPS: Frequently Asked Questions

Does SAP SRM TPS work if we are still running on SAP ECC (not S/4HANA)?

Yes. The majority of SAP SRM TPS engagements involve SRM integrated with SAP ECC 6.0 (EHP0–EHP8). GoVendorFree provides TPS for the complete SAP SRM and ECC stack. SAP ECC TPS can be combined with SRM TPS for a comprehensive SAP procurement and ERP cost reduction in a single engagement.

Can TPS support the SAP NetWeaver Portal used for SRM self-service procurement?

Yes. SAP SRM 7.0's self-service procurement interface runs on SAP NetWeaver Portal (EP 7.x), and GoVendorFree's SRM TPS engagement covers the NetWeaver Portal infrastructure as part of the SRM application stack. SAP NetWeaver TPS can be provided as a standalone engagement or bundled with SRM TPS.

What about Ariba Network supplier connectivity — is that affected by moving to TPS?

No. TPS is a support contract arrangement — it does not affect your ability to maintain existing Ariba Network connections for electronic invoicing or order collaboration with suppliers. SRM TPS preserves your current SAP SRM environment and its existing supplier connectivity architecture without modification.

Related SAP TPS Guides