SAP’s “clean core” strategy sets high-level guardrails that keep the digital core stable while still allowing innovation.

The white-paper “Clean Core for SAP S/4HANA Cloud” and the SAP Activate roadmap list the key guiding principles as

1) creating an organizational setup, technical platform, and transformation method that anchor clean-core thinking (A);

2) embedding clean-core activities throughout the entire value-process chain so that every change or extension is evaluated against the principle (E); and

3) running strict release- and lifecycle-management processes to keep the system aligned with SAP’s upgrade cadence (D).

Regular housekeeping (B) and defining roles in a transformation office (C) are good operational practices, but they are not called out by SAP as core guiding principles.

B. Housekeeping tasks are day-to-day operational measures, not part of SAP’s strategic “guiding principles” list.

C. Specific role definitions belong to governance details; SAP groups these under the broader organizational principle already covered by option A.

1. SAP SE

“Clean Core for SAP S/4HANA Cloud Private Edition – Guiding Principles

” Rev. 03/2023

pp. 8-9 (bullet list: “Establish organizational structure…”

“Integrate clean-core practices…”

“Establish release management”).

2. SAP Activate Roadmap Viewer

Task ID ACTDiscClrCoreGP

section “Guiding Principles for Clean Core

” SAP SE

2023 (lists same three principles).

3. SAP SE

“RISE with SAP S/4HANA Cloud: Clean Core Strategy

” Version 1.0

2022

§4.2 “Guiding Principles” (paragraphs 1-3 mirror A

E

D).

A consignment order in SAP S/4HANA Transportation Management (TM) is a business document that represents a logical group of items to be transported from a shipper to a consignee. It is specifically designed for use in shipper-consignee collaboration scenarios, serving as a primary basis for communication and information exchange between these two parties. This document consolidates transportation demands and facilitates planning and visibility for the consignee before the actual physical transport, which is managed by freight orders.

A. Freight order: This is an execution document sent to a carrier to perform the physical transportation of goods. It is not primarily a logical grouping for shipper-consignee communication.

B. Service order: This document is used to procure transportation services from a carrier, typically in a subcontracting scenario. It is a purchasing document, not a communication tool for consignees.

D. Sales order: A sales order is a source document from the Sales and Distribution (SD) module that creates a transportation requirement; it is not the TM document that represents the logical grouping itself.

1. SAP S/4HANA Help Portal

"Consignment Order": "A consignment order is a business document that you can use in shipper-consignee collaboration to represent a group of items to be transported from a shipper to a consignee." (SAP S/4HANA 2023

Transportation Management (TM) -> Order Management -> Consignment Order).

2. SAP S/4HANA Help Portal

"Freight Order": "A business document that is the basis for transporting goods. A freight order can contain one or more transportation stages. You send the freight order to a carrier and you can use it as the basis for charge calculation and settlement." (SAP S/4HANA 2023

Transportation Management (TM) -> Freight Order Management -> Freight Order).

3. SAP S/4HANA Help Portal

"Service Order for Carrier": "In SAP Transportation Management (SAP TM)

you can create a service order to purchase transportation services from a carrier." (SAP S/4HANA 2023

Transportation Management (TM) -> Freight Order Management -> Subcontracting -> Service Order for Carrier).

Incompatibilities are generic constraints that TM can check at several defined processing points (Usage). Standard delivered usages include:

• Delivery Proposal – the system checks the sales-order-based delivery proposal run and prevents grouping of items that violate an incompatibility.

• Freight Unit Building – while the FUB engine creates freight units from transportation requirements it evaluates incompatibility profiles so that no freight unit is built that contains mutually-exclusive objects (for example, products, partners).

• Carrier Selection – during automatic carrier selection the system again validates the incompatibility profile to ensure that the planned freight order offered to a carrier does not contain incompatible combinations.

Tendering and charge/price calculation do not call the incompatibility engine.

B. Tendering – incompatibilities are evaluated earlier (planning/carrier selection); the tendering worklist only sends the already-checked freight order to carriers.

C. Charge calculation – rating uses charge management (rate tables, calculation sheets); incompatibility profiles are not read during cost calculation.

1. SAP S/4HANA 2022 FPS02 Help Portal

Transportation Management → Planning → Compatibility and Incompatibility Checks → “Define Incompatibility Types”

table “Usage” (entries: Delivery Proposal

Freight Unit Building

Carrier Selection).

2. SAP S/4HANA TM Configuration Guide

section 10.4 “Incompatibility Profiles”

pp. 236-238 – describes evaluation points (Delivery Proposal

FUB

Carrier Selection) and explicitly states “not used for charge calculation or tendering”.

3. SAP Training Course TM110 (S/4HANA 2021)

Unit 5 “Planning Restrictions”

slides 9-12 – lists the same three usage contexts and demonstrates system behavior.

In Customizing you can attach a Change Controller Strategy to any Transportation Order (TOR)-based document type that carries the field CHNGSTRAT. Both Freight Order types (SPRO → TM → Freight Order Management → Freight Order → Define Freight Order Types) and Order-Based Transportation Requirement (OTR) types (SPRO → TM → Transportation Requirements → Order-Based Transportation Requirement → Define OTR Types) provide this field, allowing the system to control how changes in predecessor or successor documents are processed. Forwarding Orders and Service Orders have no CHNGSTRAT field; change handling for them is managed differently (e.g., status management or output control).

B. Forwarding order – Forwarding Order type customizing (/SCMTMS/TORTYPEFWO) has no Change Controller Strategy field; changes are handled through forwarding-specific logic.

C. Service order – A PM/CS object, not a TM TOR; TM Change Controller does not apply to this document type.

1. SAP S/4HANA 2023 Application Help – Transportation Management: “Define Freight Order Types

” Section ‘Field Properties’

field CHNGSTRAT (Change Controller Strategy).

2. SAP S/4HANA 2023 Application Help – Transportation Management: “Define Order-Based Transportation Requirement Types

” Section ‘Field Properties’

field CHNGSTRAT.

3. SAP S/4HANA IMG Documentation (SAP Library

S4CORE 107): Cross-Process Settings → Change Controller – Overview

paragraph 2 (explains that strategies are assigned only to TOR types that hold CHNGSTRAT).

A, D