SAP Supplier Relationship Management (SRM) is part of SAP Business Suite 7 and has long been the backbone for strategic and operational procurement—covering sourcing, supplier collaboration, requisitioning, purchasing, and contracts—integrated with SAP ERP (ECC) and, more recently, S/4HANA back ends. Many organizations adopted SRM to standardize processes, enforce compliance, and drive savings through centralization and automation.
SAP is shifting focus from SAP SRM to align with its strategic move to cloud-based offerings and the S/4HANA platform. In 2020, SAP announced mainstream maintenance for Business Suite 7 through the end of 2027, with optional extended maintenance through the end of 2030. SAP SRM follows this policy, guiding customers toward modern successors that deliver faster innovation, better user experiences, embedded analytics, and networked supplier collaboration. See SAP Note 2881788 and SAP’s “SAP Extends SAP S/4HANA Maintenance Through 2040” announcement for context.
Supported SAP SRM releases from Q1 2026:
SAP will provide mainstream maintenance for the following SAP Supplier Relationship Management (SRM) Enhancement Packages until December 31, 2027 and provide optional extended maintenance from January 1, 2028 until December 31, 2030:
– EHP2 for SAP SRM 7.0 (release level 7.02): support non-Unicode and Unicode deployments.
– EHP3 for SAP SRM 7.0 (release level 7.13): support non-Unicode and Unicode deployments.
– EHP4 for SAP SRM 7.0 (release level 7.14): support Unicode deployments.
Note: If you run non-Unicode on EHP2/EHP3, consider Unicode migration as part of risk mitigation and transition planning.
Maintenance timeline for SAP SRM and what each phase means:
SAP will provide mainstream maintenance for the latest three EHPs only i.e. EHP4, EHP3 and EHP2 only. Maintenance timeline for SAP Business Suite 7 which also includes SAP SRM are as below.
– Until December 31, 2027: Mainstream maintenance with full standard support for supported SAP SRM releases.
– From January 1, 2028 (default): Customer-specific maintenance with limited support (no new innovations, constrained legal/regulatory coverage); SAP does not support customer-developed extensions in this phase.
– Optional January 1, 2028 to December 31, 2030: Extended maintenance for an additional fee; applies to the entire SAP Business Suite 7 core applications landscape and related add-ons (not selectable for subsets).
– From January 1, 2031: Only customer-specific maintenance is available.
Please be aware, extended maintenance is not available for a subset of the customer installation only. It always applies to the full landscape of SAP Business Suite 7 core applications and all respective SAP Business Suite 7 Add-Ons.
After its mainstream maintenance periods end in 2027 SAP SRM will no longer receive full standard support from SAP, though it will enter a limited “customer-specific maintenance” phase.
Please check out SAP Note 52505 for general details regarding the maintenance phases of SAP applications and specifically customer-specific maintenance.
Successor options:
SAP S/4HANA for Central Procurement: Centralizes operational procurement across ECC and/or S/4HANA with native ERP integration and embedded analytics—ideal for harmonizing processes and supporting a broader S/4HANA journey.
SAP Ariba: Cloud-based suite for strategic sourcing, supplier management, contracts, guided buying, and multi-enterprise collaboration—suited to organizations prioritizing rapid cloud innovation and supplier network scale.
Hybrid: Pair S/4HANA Central Procurement for operational buying with SAP Ariba for strategic sourcing and collaboration to balance risk and accelerate time-to-value.
Public sector: SAP Ariba Sourcing and Procurement for Public Sector in S/4HANA (SAP Ariba PPS) is the recommended path for SRM Government Procurement (see SAP Note 3668214).
SAP is transitioning away from SRM in alignment with its move to S/4HANA and cloud solutions. Mainstream support concludes in 2027, with optional extended maintenance available until 2030 and customer-specific maintenance thereafter. With this timeline in mind, now is the right moment to set a clear transition roadmap.
Choose the successor architecture that best fits your goals—S/4HANA for Central Procurement, SAP Ariba, or a hybrid approach (and Ariba PPS for public sector)—and plan a phased migration that accounts for your current release, Unicode posture, integrations, and regulatory needs. Taking these steps early will reduce risk, maintain compliance, and position procurement for modern, innovation-rich capabilities. For official guidance, consult SAP Note 2881788, SAP Note 3668214, and SAP’s S/4HANA maintenance announcement. Incase you have any further queries, please reach out to us at sap_srm_customer_care@sap.com
