| Status | |
| Owner | RUSNAK-ext, Peter |
| Stakeholders |
The purpose of this Key Decision Document (KDD) is to elaborate on the solution recommended to manage the indirect procurement process on the new S/4HANA system.
"Guided Buying with SAP Ariba Buying" is recommended as the indirect procurement process for Syensqo. This recommendation is based on several key factors, including a high degree of integration with S/4HANA, simplified and intuitive user interface for procurement tasks while ensuring policy compliance for everyday purchases, and the strategic alignment within the SAP ecosystem .
Currently, all indirect purchases for both goods and services are handled in SAP SRM7 that works with both ERP systems. EZBuy platform that is built on top of SRM7 offers an “Amazon like” experience and serves as the gateway to Ariba Catalogs. Here, shopping carts for non-stock catalog items are assembled and then sent back to SRM7 for the approval and ordering processes to proceed.
Ariba Catalogs are utilized by 14 countries, encompassing a total of 200 internal non-stock material catalogs and 140 punchout catalogs.
Below is the architecture of the existing procurement solution. EZBuy is just a frontend, the whole business logic and data are in SRM7.
Implementing Guided Buying with SAP Ariba Buying can significantly enhance the procurement process, offering benefits in terms of user experience, compliance, efficiency, and cost savings. However, the transition requires careful planning considering factors such as change management, system integration, and user training to fully realize these benefits
Currently, no specific business rules have been identified. Further updates may be determined during the detailed design phase.
Indirect procurement, which involves the acquisition of goods and services that are not directly incorporated into a product being manufactured, can be managed through various solutions, each with its own set of features and capabilities.
SAP SRM 7 is a legacy procurement solution designed to optimize the procurement process, focusing on supplier collaboration and efficiency.
However, it is reaching the end of its lifecycle and it is not natively included or specifically designed to run as part of the S/4HANA suite. Its Shopping Cart functionality was replaced with the S/4HANA Self-Service Procurement functionality based on the Purchase Requisition document.
SAP S/4HANA MM is part of the larger SAP S/4HANA Enterprise Resource Planning (ERP) suite, offering comprehensive materials management and procurement functionalities. It is designed for businesses looking for an integrated solution that covers all aspects of their operations, including procurement.
SAP Ariba Buying is a comprehensive cloud-based procurement solution designed to manage the end-to-end procure-to-pay process. It offers a wide range of functionalities to automate and optimize procurement tasks.
Procure to Pay with SAP Ariba Buying combines the simple and elegant shopping experience and the user guidance of Ariba Buying and Invoicing with integrated business processes and data transparency of SAP S/4HANA Cloud as the digital core.
The following picture illustrates the process.

However, with the latest S/4HANA release this process became deprecated and will not be enhanced in upcoming releases.
Guided Buying is an add-on capability to SAP Ariba Buying that focuses on enhancing the user experience by providing a simplified and intuitive interface for procurement tasks. It is designed to help users make the right purchasing decisions in compliance with company policies. It combines the guidance for requisitioners provided by guided buying with the proven procurement processes provided by SAP S/4HANA Cloud.
In this scenario, employees create requests for catalog items, existing materials, planned lean services, limit items for material and service, or free-text items by adding them to a request in Guided Buying. Then the request is replicated to SAP S/4HANA Cloud, where a purchase requisition is created. In the request in Guided Buying, employees can see the document numbers of the follow-on documents that were created in SAP S/4HANA Cloud.

For organisations running SAP S/4HANA Cloud, Private Edition, the recommended indirect procurement process is Guided Buying with SAP Ariba Buying (2NV) that combines the guidance for requisitioners provided by guided buying with the proven procurement processes provided by SAP S/4HANA Cloud . It offers numerous benefits to the indirect procurement process, including improved user experience, spot buy support and allows procurement organisations to scale self-service procurement across spend categories while enforcing compliance and potential cost savings.
This table provides a snapshot of the key advantages and disadvantages associated with each procurement solution.
Option A: SRM7 | Option B: S/4HANA MM | Option C: P2P with Ariba Buying | Option D: Guided Buying with S/4HANA | |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
Option A "SRM7" is not natively supported by S/4HANA and since SRM7 is also nearing end of lifecycle it is not recommended as a long term solution.
Option B "S/4HANA MM" brings deep integration with other S/4HANA modules, however lacks advanced user interface and guided buying capabilities and policy compliance controls. The procurement solution of S/4HANA is not a successor of SAP SRM7 and it has limited capabilities compared to SAP SRM7.
Option C "P2P with SAP Ariba Buying (1ZM)" has been deprecated and will not be enhanced in upcoming releases and therefore it is not recommended as a long term solution.
Option D "Guided Buying with S/4HANA (2NV)" combines the advantages of option B and option C and adds additional capabilities that focus on simplifying the buying process and improving compliance with procurement policies. It also natively integrates with S/4HANA and SAP Business Network, as shown below.

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
