Between RISE, GROW, and Ariba: The unresolved gap in strategic SAP purchasing
Cloud transformation with S/4HANA, RISE with SAP, and GROW with SAP is a key modernization project for many companies, thereby also changing the underlying conditions for purchasing with SAP. Both bundles move the ERP to the cloud, standardize processes, and create a stable technological basis for operational purchasing – purchase orders, goods receipts, invoices, master data.
But strategic purchasing, with its sourcing processes, remains excluded from this. The result: additional integration efforts and unnecessarily complex process chains, even though cloud modernization actually promises simplification.
Key takeaways
- RISE and GROW modernize the ERP core—strategic sourcing remains outside the scope. RFX processes are not included in the scope of delivery and continue to run outside of S/4HANA.
- The Ariba bundle only covers operational purchasing. For strategic sourcing, additional Ariba modules must be licensed and integrated.
- Two system environments instead of consistent processes. Interfaces, data copies, and media discontinuities increase complexity and reduce the benefits of cloud transformation.
- After ERP migration, companies must decide where sourcing should be located in the future. Expand Ariba, continue manually, use third-party tools, or choose SAP-native alternatives.
What RISE SAP and GROW SAP actually deliver – and what they don't
RISE with SAP and GROW with SAP both pursue the same goal: To bring companies into the cloud faster, cleanly, and more predictably. The building blocks differ, but the logic behind them does not: The ERP core is modernized, not expanded.
👉 S/4HANA Cloud Private Edition is provided as part of an SAP RISE migration including infrastructure, operation, business process intelligence, and BTP options for integrations or enhancements. It is the transformation path for companies with mature landscapes, high integration requirements, and individual process setups.
👉 GROW SAP provides the public cloud. Standardized, preconfigured, quick to implement – for organizations that consciously rely on strict standards and require less customization.
Both cloud bundles neatly cover the operational purchasing processes: Processing of purchase orders, goods receipts, invoice verification, and master data logic. However, they do not include functions for RFX, requests for quotation, comparison of quotations, or awarding. These processes are structurally outside of S/4HANA, regardless of which bundle one chooses.
This is where the first gap arises:
RISE and GROW modernize the foundation, but not the part of purchasing that decides on prices, competition, and awarding.
Ariba in the context of SAP RISE and GROW
When companies consider their purchasing processes in the SAP environment, their attention quickly turns to Ariba. Both "RISE with SAP" and "GROW with SAP" include parts of the Ariba ecosystem —but exclusively in the area of buying and in the SAP Business Network.
This means, specifically:
- Ariba Buying (Light) in the form of catalog and procurement scenarios
- Access to the SAP Business Network for purchase orders, order confirmations, or delivery notes
- Basic supplier interactions in a network context
This supports operational purchasing, but is clearly limited in terms of functionality. Strategic sourcing functions are not covered. RFX processes therefore remain outside of S/4HANA and outside the scope of Ariba included in the bundle.
To close this gap, companies must license additional Ariba modules separately, for example: Ariba Sourcing (RFx, eAuctions), Ariba Contracts (CLM), or Ariba Supplier Lifecycle & Performance (SLP). This means that these modules run as separate cloud solutions, with separate licenses, separate implementation, and separate process logic.
"Mind the Gap" – where you should look closely
| ✅ S/4 HANA in SAP purchasing: Focus on Procure-to-Pay | Requisition & purchase orders: Purchase requisitions, approvals, purchase orders Goods receipt & services: Goods receipt, MM-SRV, Lean Services Invoice verification: Triple matching, MIRO Master data: Suppliers, materials/services, conditions Operational buying (bundled): Ariba Buying Light, SAP Business Network |
| ❌ Not covered Outside of S/4HANA: Strategic & tactical sourcing | RFx processes: Requests, quotations, bid comparisons Evaluations & awarding: Evaluation matrices, awarding decisions Supplier interaction: Submission of quotes, queries, portal logic Project/service sourcing: Multi-level item lists, GAEB-based structures Advanced functions: E-auctions, supplier lifecycle, CLM, tactical sourcing |
Special topic:
Sourcing & S/4HANA
Mapping RFX and procurement processes entirely within the SAP context – without an additional platform logic. FUTURA embeds strategic sourcing directly in S/4HANA in an SAP-native manner.
What happens when sourcing does not run in the SAP core
When operational procurement runs in the S/4HANA core, but strategic sourcing takes place in separate modules or tools, discontinuities arise – functionally, technically, and organizationally. The effects are evident in several areas.
⚠️ Divided data, divided truth
Purchase orders in the ERP, quotations and awarding in Ariba/Excel. Result: No consistent overview, weak reporting, unclear basis for decision-making.
⚠️ Integration effort instead of cloud simplicity
Despite RISE/GROW, every connected sourcing tool means additional interfaces, mapping, and governance. The cloud is not becoming simpler here, but more technical.
⚠️ Media discontinuity in daily work
Switching between SAP, Ariba, Excel, and e-mail. Exporting quotation lists, comparing them manually, storing everything somewhere. The most critical steps are taken offline.
⚠️ Gaps in governance and auditability
Awards are not included in the SAP document chain. This complicates verification and auditing and creates operational risks – even though the ERP core runs smoothly in the standard system.
⚠️ Reduced impact of cloud transformation
Modern in the P2P process, analog in the RFX process. RISE/GROW provide the foundation—but Excel remains a fixture in everyday sourcing.
Conclusion: Cloud modernization covers only half of the purchasing process
RISE and GROW create a modern ERP basis, standardize processes, and bring stability to operational purchasing. However, there is still a clearly recognizable gap in strategic and tactical sourcing. The upstream processes that give rise to competition, transparency, and awarding contracts remain outside the SAP core – regardless of whether a company uses a private or public cloud.
This is precisely why organizations face a simple but fundamental decision at the end of the transformation: How do we close the functional gap in sourcing?
In practice, there are currently four ways:
1️⃣ Licensing Ariba modules separately
→ Full sourcing functionality within the Ariba portfolio, but additional cloud solution, separate implementation, and integration effort.
2️⃣ Continue to perform sourcing manually
→ Excel, e-mail, and unstructured documents; low threshold, but without transparency, governance, or audit compliance.
3️⃣ Using third-party solutions or procurement suites
→ Dedicated sourcing tools or more comprehensive suites; Functionally powerful, but parallel platform, own data model, and additional interfaces linked to the ERP.
4️⃣ Use SAP-native additions
→ RFX processes directly in the S/4HANA data model and in conjunction with existing ERP functionalities (no additional platform environment), such as SAP-native RFX approaches like FUTURA.
This approach is recommended for companies that want to consciously pursue the clean core approach after the RISE/GROW migration and avoid setting up additional platforms, interfaces, and data copies.
Particularly suitable for purchasing organizations that:
👉 Want to fully integrate RFx processes into SAP,
👉 Prioritize governance, auditability, and data consistency.
👉 Strive for a manageable tool environment,
👉 Want to inteflink operational and strategic processes more closely,
👉 Need to issue requests for services und construction work in a structure manner and in accordance with SAP.
One thing is clear: the decision on the sourcing setup will not be made in RISE or GROW – it will only begin after ERP modernization.
From parallel worlds to a clear sourcing flow.
Take the next step in the digitalization of sourcing with S/4HANA – digitalize RFx processes directly within your SAP architecture.
