SAP SRM Successor: What Ariba Can Do for Services Procurement — and Where It Falls Short

The announcement that SAP SRM will be phased out in 2027 has put the decision of how to move forward back on the agenda for many companies. SAP positions Ariba solutions as the official successor—albeit with structural limitations: particularly when it comes to service procurement using GAEB-based service specifications, Ariba encounters functional limitations that are relevant for German small and medium-sized businesses. This article highlights where Ariba delivers—and where it falls short.

From SAP SRM to Ariba – through the lens of SAP

SAP's strategy is to replace SAP SRM with SAP Ariba and SAP S/4HANA: "One system covering purchase orders, release, delivery and billing, strategic agreements with preferred suppliers, centralized requests via a global platform and, lastly, analytics across all partners," is SAP's promise regarding the Ariba solution portfolio which consists of various cloud solutions for strategic as well as operational purchasing that can also be used in stand-alone mode.

🔹 SAP Ariba Network — a central platform for supplier communication, sourcing, and invoicing. More than 3 million registered companies, primarily serving global procurement organizations.

🔹 SAP Fieldglass — for staffing services and the management of external employees. The focus is on “who” performs the work, not “what” or “how much.”

🔹 Ariba Solutions in S/4HANA — For material- and quantity-based services, SAP recommends using Ariba solutions integrated into S/4HANA.

SAP Ariba: End-to-End Processes for Service Procurement

The SAP whitepaper Transform Procurement with SAP S/4HANA and SAP Ariba Solutions presents two process variants, one originating from the ERP system (here: S/4HANA) and one from SAP Ariba     

1. Purchase-to-Pay (P2P) — all workflows have been migrated to the Ariba Cloud; only the invoice is stored in the ERP system.
2. Purchase-to-Order (P2O) — The purchase order and goods receipt document, or the approved service entry sheet, are posted in the background in S/4HANA.

GAEB vs. SAP Logic: Two Different Worlds

However, regardless of the basic scenarios that involve different Ariba solutions in each case: In comparison, service descriptions and service entries are subject to an entirely different approach than in Germany.    

Because regardless of whether SAP parlance refers to so-called "Complex Services" or "Simple Services," billing is usually done on an hourly basis. In the project business, for example, services to be provided are described in separate Statements of Work (SOWs), which contain information on the initial situation, goal, focus, and task requirements – without a predefined, fixed structure. Contractual agreements refer to fixed hourly rates, which are then used for billing.   

The procedure in Germany is quite different: Services, in particular construction services, are described in the form of multi-level item lists, which are exchanged in accordance with the German GAEB format. Such complex item lists have nothing in common with SAP's understanding of "Complex Services".

👉 Example:

An item "Paint 1 sqm wall", for example, has a unit price, which may include a material and labor component - an order is placed specifying the unit price and the area in sqm. A service report is therefore not calculated on the basis of hours, but on the basis of the area painted, i.e., the service rendered. Only this differentiated description of the service to be rendered enables precise billing, which provides much greater transparency than the exclusive consideration of supplied material and hours spent.

This is precisely what is reflected in the simplification approach of S/4HANA and Ariba: services are to be handled as a simple list—“Lean Services.” The limitations become apparent, at the very latest, when services are recorded in a tender document structure.

Limitations of SAP Ariba and the consequences

Two limitations associated with Ariba have far-reaching consequences, to the detriment of handling, data consistency and transparency in the area of requests and billing of services or construction work:

🔹No service hierarchies — SAP SRM users could still map multi-level hierarchies in ECC via MM-SRV. Ariba Network does not support this: Purchase orders with more than one hierarchy level cannot be transferred.

🔹 No GAEB support — neither SAP ECC, the S/4HANA Procurement Suite, nor SAP Ariba support the GAEB format, which is widely used in Germany for exchanging specifications.

The result: Companies that plan their construction services in GAEB formats and use, for example, an AVA system (tendering, award billing) for this purpose have , by default , no way to import their bills of quantities into SAP —whether for a tender or for a purchase order that is to be communicated to service providers via the SAP Ariba Network.

This means that, in the case of a tender, the data required for an automatic price comparison at the line item level is missing, and in the case of a purchase order, performance confirmation cannot take place at the line item level.  

Workaround Undermines Procurement Transformation

When ordering construction services or services based on multi-level service specifications, Ariba users have only one workaround:

A statement of work can only be attached as a file.

This means that only one line item with the order total is posted in the SAP system (keyword: 1 LE); all details are included in the attachment and can be accessed separately only as a PDF form. 

This thwarts dedicated controlling and reporting. Because only if the individual services (i.e., items of the item list) are stored in the SAP system in the form of service lines can services be recorded at service line level – and thus ensure transparent billing.

Conclusion: SAP SRM Successor for Services Procurement: Ariba Is Not the Answer to Everything

From SAP’s perspective, the digital transformation of procurement views S/4HANA as the digital core to which SAP Ariba applications are connected. In a global context, this represents a consistent standardization strategy—local formats such as GAEB fall through the cracks.

However, Lean Services in a catalog structure are unable to meet local requirements for processing and using multi-level service specifications in GAEB format. Companies whose core competencies include the procurement and management of services—and whose procurement processes are largely concentrated in this area—cannot achieve the desired process optimization and cost transparency with SAP Ariba solutions.

In Germany, there is no alternative to exchanging bills of quantities in GAEB format for the detailed and transparent commissioning and billing of services, particularly construction services. FUTURA Engineering is exactly that solution: GAEB-compatible, integrated with SAP—bills of quantities directly in the system, no workarounds.

👉 Editorial Note (2025): With S/4HANA 2022, SAP introduced Item Hierarchies, which enable a more structured representation of service items. However, they do not solve the GAEB problem—without an additional solution, importing and exporting GAEB service catalogs remains impossible.

Latest blog posts on GAEB and SAP service procurement:

➡️ GAEB Converter in SAP Ariba: Limitations of File Conversion — Why the Converter Approach Does Not Solve the Structural Problem.

➡️ Lean Services with Item Hierarchies: GAEB in SAP Construction Tenders — How GAEB Specifications Can Be Integrated into SAP Processes.