| Status | |
| Owner | RUSNAK-ext, Peter |
| Stakeholders |
The purpose of this Key Decision Document (KDD) is to elaborate on the solution recommended to manage indirect procurement process on the new S/4HANA Cloud Private Edition SAP ERP system.
Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.
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.
Bellow is the architecture of the existing procurement solution. EZBuy is just a frontend, the whole business logic and data are in SRM7.

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited.
Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.
Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order".
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.
Option B: SAP S/4HANA MM
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.
Option D: Guided Buying with SAP Ariba Buying (2NV)
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 solution 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.
While SRM7 and
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|
|
| |
| Criterion 3 |
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.
