SAP officially classifies its value-stream–oriented, end-to-end processes as Lead-to-Cash, Design-to-Operate, Source-to-Pay, and Recruit/Hire-to-Retire. These streams span SAP S/4HANA and the surrounding cloud portfolio and are the reference categories used in SAP Activate, SAP Signavio Process Explorer, and RISE with SAP documentation. Therefore Design-to-Operate (B), Hire-to-Retire (C), and Lead-to-Cash (E) are valid SAP end-to-end business processes.

A. Record to Report – A finance sub-process; not listed among SAP’s four standard value-stream end-to-end processes.

D. Procure to Pay – SAP’s official stream is “Source-to-Pay”; the “Procure” variant is not used in the canonical list.

1. SAP SE. “End-to-End Processes with SAP S/4HANA.” White Paper

2023

pp. 4-5 (Figure 1 lists Lead-to-Cash

Design-to-Operate

Source-to-Pay

Recruit-to-Retire).

2. SAP Help Portal. SAP Activate Roadmap “RISE with SAP S/4HANA Cloud

public edition – Deliver Phase

Solution Process Flows

” section “Design-to-Operate

” accessed Apr 2024.

3. SAP Signavio Process Explorer. “Hire-to-Retire Value Chain Overview

” Version 2024-Q1

slide 3.

4. Drees

T.

& Kiesel

R. Business Processes in SAP S/4HANA. SAP PRESS

2023

ch. 2.2

pp. 28-30 (overview of SAP’s four E2E processes).

SAP S/4HANA Cloud organizes data into three fundamental categories. Master data is the core, long-term data representing business entities like customers, materials, and suppliers, which remains relatively static. Transactional data is dynamic data generated from daily business processes, such as sales orders, purchase orders, and financial postings. Configuration data (also known as customizing) defines the system's structure and behavior, including organizational structures, business rules, and process settings, which are established during implementation to align the system with company-specific requirements.

A. Business: This term is too generic. While all data in the system is related to the business, "Business" is not a formal SAP classification for a type of data alongside Master or Transactional.

E. Organization: Organizational data, which defines the enterprise structure (e.g., company codes, plants), is a specific and crucial subset of Configuration data, not a primary data category itself.

1. SAP Help Portal

SAP S/4HANA Cloud

Public Edition 2402

"Data Migration to SAP S/4HANA from Staging": This official documentation clearly distinguishes between the migration of Master Data and Transactional Data using specific migration objects. Configuration is handled separately through tools like SAP Central Business Configuration (CBC). The entire framework is built on this data classification.

2. SAP Activate Methodology for SAP S/4HANA Cloud

Public Edition

"Data Management" Workstream: The methodology details tasks for data migration planning which are explicitly categorized. For instance

the task "Identify and Map Master Data" and "Identify and Map Transactional Data" are distinct from the system Configuration activities performed in the "Realize" phase. This confirms the three distinct data types.

3. Saueressig

T.

et al. (2022). SAP S/4HANA Cloud: An Introduction. SAP Press. Chapter 4

"Implementation with SAP Activate

" describes the process of setting up the system. It implicitly and explicitly separates the activities of system Configuration (customizing) from the loading of Master Data and historical Transactional Data

reinforcing this fundamental three-part data model.

A service contract in SAP is a long-term agreement with a customer that defines the scope and terms of services to be provided. Key data stored directly within the service contract document includes the Time Period (validity start and end dates) which defines the duration of the agreement. It also contains Conditions, which are the pricing elements (e.g., prices, discounts, surcharges) that determine the cost of the services covered by the contract. These two elements are fundamental to defining the what, when, and how much of the service agreement.

B. Warranty: A warranty is typically master data linked to a product or piece of equipment, not transactional data stored within the service contract itself.

D. Schedule Lines: Schedule lines are used in sales orders to specify quantities and delivery dates for goods, which is not the primary function of a service contract.

1. SAP Help Portal

SAP S/4HANA Cloud 2402

"Service Contracts": This document outlines the structure of a service contract

explicitly stating it is an agreement for a "predefined value or quantity over a specific period." This confirms the storage of a Time Period. The document also details that service contracts contain items with specific pricing.

2. SAP Help Portal

SAP S/4HANA Cloud 2402

"Header Details in Service Contracts": In the "General Information" section for the service contract header

the fields "Contract Start Date" and "Contract End Date" are listed as core data

confirming the Time Period.

3. SAP Help Portal

SAP S/4HANA Cloud 2402

"Pricing in Service Contracts": This official documentation states

"The system uses the condition technique to determine the price for a service contract." It further explains how pricing elements are stored as Conditions at both the header and item level of the contract.

Backwards scheduling for a planned order begins with the material requirement date and calculates backwards to determine the order start and opening dates. The system first subtracts the goods receipt processing time from the requirement date to find the production finish date. Next, the in-house production time is subtracted to calculate the production start date. Finally, the opening period, defined in the scheduling margin key, is subtracted from the production start date to determine the date by which the planned order must be converted, which is the planned opening date. These three elements are fundamental to this calculation.

C. Quality inspection time: This is not a distinct, top-level scheduling element. It is typically included as part of the goods receipt processing time or as a specific operation within the routing (part of in-house production time).

D. Goods issue processing time: This time is relevant for the staging and availability of components required for the production order, not for scheduling the planned order of the finished product itself.

1. SAP Help Portal

SAP S/4HANA

"Scheduling for In-house Production": This document outlines the scheduling process for materials produced in-house. It explicitly states: "The system subtracts the goods receipt processing time from the order finish date to determine the production finish date... The system subtracts the in-house production time from the production finish date to determine the production start date." This confirms options A and E.

(Reference: SAP S/4HANA -> Product Assistance -> Enterprise Business Functions -> Manufacturing -> Production Planning and Control (PP) -> Material Requirements Planning (PP-MRP) -> MRP Calculation -> Scheduling -> Scheduling for In-house Production)

2. SAP Help Portal

SAP S/4HANA

"Scheduling Margin Key": This documentation details the components of the scheduling margin key

which is used in scheduling calculations. It specifies that the "Opening period" is used to calculate the opening date of the planned order by subtracting it from the order start date. This confirms option B.

(Reference: SAP S/4HANA -> Product Assistance -> Enterprise Business Functions -> Manufacturing -> Production Planning and Control (PP) -> Basic Data (PP-BD) -> Material Master (PP-BD-MM) -> Scheduling Margin Key)

3. SAP Help Portal

SAP S/4HANA

"Material Master Data for MRP": The documentation for the Material Master

specifically the MRP 2 view

describes the purpose of the "In-house production time" and "GR (Goods Receipt) processing time" fields as direct inputs for production scheduling.

(Reference: SAP S/4HANA -> Product Assistance -> Enterprise Business Functions -> Manufacturing -> Production Planning and Control (PP) -> Material Requirements Planning (PP-MRP) -> Master Data for MRP -> Material Master Data for MRP)

In SAP's Materials Management (MM) module, the purchasing price is managed using the condition technique. The price itself, along with any associated discounts or surcharges, is stored as a condition record in the condition master data. Each price element is represented by a condition type (e.g., PB00 for gross price). While business objects like the Purchasing Info Record or contracts contain pricing information for specific vendor-material combinations, they do so by holding the relevant condition records. Therefore, the most fundamental and technically accurate location for storing a purchasing price is the condition master record, as this is the underlying data structure the system uses for price determination across various purchasing documents.

A. In the Material Master: The material master stores internal valuation prices, such as the standard price or moving average price, used for inventory accounting, not the external purchasing price from a vendor.

B. In the Vendor Master Record: The vendor master contains general data about a supplier, such as address and payment terms, but it does not store prices for specific products.

D. In the Purchasing Info Record: While a Purchasing Info Record is a primary source for the price of a material from a specific vendor, it is a business object that contains condition records. The condition record is the more fundamental data element.

1. SAP S/4HANA Help Portal

"Conditions in Purchasing": "In the SAP System

the term ‘conditions’ is used to refer to agreements with vendors relating to prices

surcharges

and discounts. These are stored in the system as individual condition records." This document clarifies that prices are stored as condition records.

2. SAP S/4HANA Help Portal

"Purchasing Info Record": "The purchasing info record contains information on a specific material and a vendor supplying the material... For example

the vendor's current price for the material is stored in the info record... You can maintain the following conditions in a purchasing info record: Prices and discounts that the vendor grants you." This shows that the Info Record is a container for the condition records.

3. Akhtar

J. (2018). Materials Management with SAP S/4HANA: Business Processes and Configuration. SAP PRESS. In Chapter 8

"Pricing and Conditions

" the text explains

"A condition record is a data record that stores a condition. For example

you can create a condition record for a material price or a customer-specific discount." (Section 8.1.3

"Condition Record"). This establishes the condition record as the core data storage entity for prices.