Reality check on SAP Ariba Sourcing: RFX, integration – and the consequences for purchasing

S/4HANA is here – now what? Head of purchasing who want to take the next step toward digital sourcing need a solution that allows RFX processes to be handled in a structured, transparent, and SAP-integrated manner. At first glance, purchasing with SAP Ariba Sourcing, the cloud module for requests for quotation, comparison of quotations, and awardings, seems like the obvious choice.

However, many SAP Ariba project experiences show that while its use brings advantages, it also entails noticeable new costs. Despite modern cloud architecture, additional costs, parallel data worlds, and media discontinuities arise. This blog article examines why this is the case, what experiences companies have had with SAP Ariba Sourcing, and what structural effects this platform separation has on SAP purchasing.

SAP Ariba Sourcing – a separate platform instead of ERP extension

SAP Ariba Sourcing is positioned as a central component for strategic procurement management. However, Ariba Sourcing is not an extension of S/4HANA, but rather a standalone cloud platform.

The implications for SAP purchasing are as follows:

• Separate middleware and interface projects for connection to S/4HANA

• Replication and synchronization of quotation, supplier and awarding data.

• Independent data model and separate business logic outside the SAP document chain.

Ariba Sourcing brings new features into play – but on a separate platform that decouples strategic sourcing from the ERP system. As a result, the basis for SAP's single-platform strategy cannot be fulfilled. And this is precisely where structural problems begin in many companies.

Integration effort & operation – the underestimated cost center

The connection between Ariba Sourcing and S/4HANA is not a “standard connector” that you set up once and then never touch again. The integration is a separate architectural strand – which is the biggest source of effort, errors, and hidden costs in many projects. Quotations, awards, supplier updates, and purchase requisition data are not available in the same data model. Everything has to be transferred, mapped, or replicated – based on outdated interface technologies such as IDocs and CSV files.

One customer told us that the project team spent over a year trying to get the integration up and running – ultimately without satisfactory results. The bottom line: SAP Ariba Sourcing is hardly practical for indirect procurement. The necessary ongoing development and maintenance of interfaces to S/4HANA slows down companies in their digital transformation instead of supporting them.

Typical cost drivers – confirmed by many SAP Ariba sourcing experiences:

⚠️ Setup and maintenance of integration interfaces (mapping, monitoring, error handling, release adjustments)

⚠️ Separate licenses for Ariba Sourcing and onboarding costs for the Business Network through which the suppliers are integrated

⚠️ Double the support and training effort for two system environments

⚠️ Ongoing maintenance effortand constant readjustment ties up internal and external personnel

Medium-sized companies in particular report that the expected savings from cloud standardization are largely lost due to the high integration costs. User acceptance often remains below 30 percent, and many purchasing teams continue to rely on their established workarounds. The originally defined ROI targets are therefore becoming increasingly distant.

User experience & process discontinuity – two worlds in purchasing

From the user's perspective, the separation between Ariba and S/4HANA is particularly evident. Both systems follow their own business logic – interface, navigation, process guidance, data structures.

👉 Two systems instead of one process
Purchasers record requisitions, purchase orders, and goods receipts in S/4HANA – and switch to Ariba Sourcing for requests for quotation, comparison of quotations, and awarding. These system changes are not only annoying, they also interrupt the workflow.

👉 Quotation and awarding data is missing in the ERP context
Award documentation, quotation details, and queries are processed in Ariba Sourcing – and are only partially written back to S/4HANA, or not written back at all. This makes reporting, traceability, and auditing unnecessarily complicated.

👉Shadow processes persist
If the business logic of Ariba Sourcing and the requirements in ERP do not match, purchasers revert to Excel lists, e-mail coordination, or local evaluation matrices. The very steps that were supposed to be digitalized end up being manual workarounds again. The result is not a consistent SAP purchasing process and a “single platform,” but rather a fragmented process across two system landscapes.

Where SAP Ariba Sourcing reaches its functional limits

Ariba Sourcing covers classic request scenarios, even if there is room for improvement in terms of usability in several areas. However, as soon as requirements become more complex – for example, in the case of technical equipment, services, project-related requests for quotation, construction projects, or multi-level structures – the system quickly reaches its functional limits.

This is precisely where many purchasing organizations experience the greatest gap between expectation and reality. The challenges begin with the new Lean Services in S/4HANA, which are not supported by SAP Ariba. In addition, there are quotation documents from suppliers that cannot be transferred to S/4HANA. The list of unresolved issues can be extensive.

Typical limitations are:

❌ Lean Services and Item Hierarchies: Not supported

GAEB-based item lists: Cannot be mapped

⚠️ Individual evaluation logic: Only possible via complex customizing

⚠️ Project-related awarding and approvals: Require additional modules or external tools

Many purchasing departments use Ariba Sourcing for simple standard RFQs, but revert to manual processes for complex or project-related sourcing events. This means that precisely those areas that would be strategically important remain analog or partially structured.

Structural impact on SAP purchasing – what causes the platform separation

The combination of two system landscapes –S/4HANA for operational purchasing and Ariba Sourcing for the strategic part – has more than just a technical impact. It changes the purchasing process itself: Governance, transparency, data availability, speed. And this often runs counter to the actual transformation goals.

The main structural consequences:

Conclusion – three decisions and one recommendation

SAP Ariba Sourcing is an established system –especially for global companies with a large supplier base. Ariba really shows its strengths when used in conjunction with other Ariba modules, such as Supplier Lifecycle, Contracts, or Buying. This combination creates a coherent process image within the SAP Business Network that works well for organizations with an international presence.

However, in S/4HANA-based organizations, Ariba Sourcing must be clearly evaluated against integration effort, system complexity, and ongoing operations – especially if the focus is on a lean, SAP-oriented architectural approach.

This is precisely why purchasing organizations must face three fundamental decisions today:

1️⃣ Where should sourcing be located in the future?
In the ERP, in a separate cloud or as a mixed architecture?

2️⃣ How much integration effort is acceptable?
One-off, permanent or preferably none at all?

3️⃣ What RFX complexity needs to be covered?
Simple standard requests or project-oriented, technical sourcing events?

It is worth considering the alternative of an SAP-native integration. Solutions that map strategic sourcing directly in the ERP data model do not require an additional platform or middleware. This reduces complexity and creates end-to-end processes without parallel worlds.

SAP-native solutions such as FUTURA Smart address precisely this issue: RFX processes run entirely within the SAP core and consistently follow SAP's “one platform strategy.” The document chain is complete, and the solution grows seamlessly with the S/4HANA system. This is an ideal approach for purchasing organizations that are looking for a lean, audit-proof, and fully integrated sourcing architecture – especially in medium-sized and large SAP environments.