Introduction

Follow my previous blog  SAP Transportation Management Clean Core Evolution – SAP Community. As  part of the continuous  evolution of SAP  TM SAP S/4HANA  marks a pivotal milestone for SAP Transportation Management (TM). This release delivers a cohesive set of innovations that collectively advance three strategic imperatives: Clean Core extensibility, API-first integration, and intelligent logistics automation. The 49 SAP Notes documented in this blog represent the authoritative reference for architects, developers, and functional consultants who need to understand what has changed, why it matters, and how to act on it.

The notes are organised into eight thematic areas — each with a curated list of notes and an architectural commentary that frames the changes within the broader SAP Logistics landscape. A full reference table at the end provides a one-page summary of all 49 notes.

1  CDS Views & Virtual Data Model (VDM)

The Virtual Data Model is the foundation of SAP's Clean Core strategy. C1-released CDS view entities provide stable, versioned interfaces that partners and customers can consume without risk of breaking changes at upgrade. S/4HANA 2025 introduces new VDM artefacts for the Transportation Order model and for the Material and Location business objects.

• SAP Note 3840080  New V2 view I_MaterialFreightGroup_2 (C1 released)
• SAP Note 3838137  VDM Foundation layer for TOR Party node
• SAP Note 3780776  TM: Enable enhancement of BO Material root via CDS view entity
• SAP Note 3756405  TM: Enable enhancement of BO Location root via CDS view entity

Architectural Commentary

SAP Note 3840080 elevates I_MaterialFreightGroup to a V2-stable, C1-released interface, making it safe to consume in BTP extension projects, fiori apps, and analytical queries without worrying about undocumented changes at upgrade time. SAP Note 3838137 delivers the VDM foundation for the Party node of the Transportation Order — a prerequisite for downstream data product and API capabilities introduced elsewhere in this release.

Notes 3780776 and 3756405 are architecturally significant: they expose the Material and Location business object roots as CDS view entities, enabling BAdI-based enhancement in a fully Clean Core-compliant way. This replaces the need for implicit enhancements or custom dictionary includes, and aligns with the SAP BTP extensibility model where side-by-side extensions interact with the core through stable, released interfaces.

2  Location & Organisational Units Data Products

Data Products represent SAP's next-generation approach to master data consumption: semantically annotated, OData-ready, and governed through a formal release contract. S/4HANA 2025 completes the Location and Organisational Unit data product foundation for SAP TM, delivering the full stack from core CDS views through data provider infrastructure to service exposure.

• SAP Note 3677186  S/4HANA 2025 Development – TM Clean Core Location CDS view foundation
• SAP Note 3696891  S/4HANA 2025 Development – Location core CDS views, Data Product and Data Provider views
• SAP Note 3747480  S/4HANA 2025 Development – Location Data Product – boolean annotations
• SAP Note 3727007  S/4HANA 2025 Development – Service Development for Location and Org Units Data Products

Architectural Commentary

The four notes in this group follow a deliberate layering pattern. SAP Note 3677186 creates the stable CDS-view foundation for Location master data — the single source of truth. Note 3696891 builds the data product and data provider views on top, while Note 3747480 corrects boolean annotation semantics that affect downstream OData filter and search behaviour. Note 3727007 completes the picture by exposing Location and Org Units through OData services.

The Org Units data product in Note 3727007 is particularly valuable for organisations integrating SAP TM with SAP S/4HANA Central Finance or SAP Analytics Cloud, as it provides a standardised, API-accessible interface to the organisational hierarchy without custom BAPI wrappers.

3  Transportation Order (TOR) & Clean Core Extensions

The Transportation Order is the central business object in SAP TM, orchestrating the full freight lifecycle from order entry through carrier assignment to proof of delivery. S/4HANA 2025 delivers a wave of Clean Core enhancements — new data products, remote APIs, and creation types — that deepen the TOR model while preserving a clean, stable core.

• SAP Note 3803774  BDC/Data Product – TOR (S/4HANA 2025)
• SAP Note 3688875  BDC/Data Product – TOR (S/4HANA 2025)
• SAP Note 3675348  Clean Core TOR TP Enhancement & Remote API
• SAP Note 3691780  Clean Core TOR Foundation Enhancement
• SAP Note 3791310  New TOR Creation Type for Local API

Architectural Commentary

Notes 3803774 and 3688875 deliver the Business Document Composition (BDC) data product for the TOR, enabling standardised document exchange in SAP Business Network for Logistics scenarios and providing a governed read interface for the full TOR payload.
Note 3691780 provides the Clean Core foundation that every subsequent TOR extension builds on — without it, custom fields and logic added via BTP extension projects cannot attach cleanly to the TOR. Note 3675348 introduces Remote API capabilities for Transportation Planning enhancements, allowing side-by-side BTP extensions to interact with TOR planning logic on the S/4HANA backend. Note 3791310 adds a dedicated TOR creation type for local API-driven scenarios, relevant for event-driven architectures and integration via SAP Integration Suite.

4  Order Management — Advance Developments

S/4HANA 2025 introduces a significant cluster of advance developments in Order Management, delivered through a coordinated set of SAP Notes. These notes extend Freight Order and Transportation Order capabilities with new fields, UI improvements, and process logic — collectively raising the bar for end-to-end order lifecycle management in SAP TM.

• SAP Note 3841367  Advance Developments for S/4HANA TM – Order Management
• SAP Note 3841186  Advance Developments for S/4HANA TM – Order Management
• SAP Note 3840156  Advance Development in the Area of Order Management
• SAP Note 3839471  Advance Developments for S/4HANA TM – Order Management
• SAP Note 3837052  Advance Development in the Area of Order Management
• SAP Note 3839570  Advance Developments for S/4HANA TM – Order Management
• SAP Note 3805411  Enhancements in freight order management
• SAP Note 3418826  TM: Cumulative enhancements (S/4HANA 2025)

Architectural Commentary

The volume of Order Management notes in S/4HANA 2025 reflects the strategic importance of this domain. Notes 3841367, 3841186, 3840156, 3839471, 3837052, and 3839570 form a coordinated advance development package — each addressing a specific aspect of order lifecycle management such as status handling, document flow, and carrier integration. These notes should be applied as a set; partial application may leave the system in an inconsistent state.

Note 3805411 targets Freight Order management specifically, adding UI fields and processing logic that support the expanded order scenarios introduced in this release. Note 3418826 is the cumulative enhancement note — it consolidates corrections and incremental improvements and should be a standard part of any S/4HANA 2025 maintenance patching checklist.

Recommendation:  Review all Order Management advance development notes (3841367, 3841186, 3840156, 3839471, 3837052, 3839570) together with your SAP TM functional lead before applying. Regression testing on Freight Order creation, status transitions, and carrier assignment workflows is strongly advised.

5  Event Reporting & Trigger Handling

Real-time visibility and event-driven processing are critical capabilities for modern logistics networks. S/4HANA 2025 advances both areas with dedicated developments for Event Reporting and Trigger Handling within SAP TM.

• SAP Note 3840749  Advance Developments for S/4HANA TM – Event Reporting
• SAP Note 3839577  Advance Development for S/4HANA TM – Trigger Handling

Architectural Commentary

SAP Note 3840749 extends the Event Reporting framework within SAP TM — enabling richer, more granular shipment event capture and reporting. For organisations running SAP Track and Trace or integrating with SAP Business Network for Logistics, this note is a key enabler of real-time visibility dashboards and exception-based alerting.

SAP Note 3839577 targets Trigger Handling — the mechanism by which SAP TM reacts to upstream events (e.g. goods issue, delivery creation, EWM transfer order confirmation) and initiates downstream TM processes automatically. Enhanced trigger logic reduces manual intervention and improves end-to-end process automation, supporting the Autonomous Enterprise vision.

6  Transportation Planning Enhancements

Transportation Planning is at the heart of TM's value proposition — optimising freight consolidation, route determination, and carrier selection. S/4HANA 2025 brings targeted UI improvements, engine enhancements, and a significant refactoring of the VSR engine activity model.

• SAP Note 3759273  Enhancements in Transportation Planning
• SAP Note 3758381  Freight Unit UI enhancements
• SAP Note 3734234  MTR Determination Facade and VSR
• SAP Note 3481260  ABAP VSS: Engine Activity Model Refactoring

Architectural Commentary

Note 3759273 is the umbrella note for planning enhancements — it should be reviewed alongside the release documentation to understand the full scope of changes in Freight Order and Freight Booking planning. Note 3758381 improves the Freight Unit UI with new field additions and list view improvements that streamline day-to-day planner operations.

Note 3734234 updates the MTR (Mode of Transport Routing) Determination Facade and its interaction with the VSR (Vehicle Scheduling and Routing) engine — a critical integration point for customers using TM optimisation. Note 3481260 performs a deep refactoring of the ABAP-side engine activity model within the VSS. While transparent to end users, this is important for technical consultants who have implemented custom BAdIs or enhancements in the planning engine. A thorough regression test of optimisation runs and manual planning is strongly recommended after applying this note.

 

7  API Enhancements & Consumption

API-first design is central to SAP TM's evolution. S/4HANA 2025 significantly expands the available API surface — introducing Configuration APIs, a new Agent API framework, performance improvements in ASR Read APIs, and important authorisation controls. This section covers 14 notes across five API sub-domains.

7.1  Configuration APIs

• SAP Note 3804213  TM TOR Configuration API
• SAP Note 3804214  TM Configuration API

The Configuration APIs expose TM customising objects through stable OData V4 interfaces, enabling automated landscape management, CI/CD pipelines for configuration transport, and integration with SAP Cloud ALM. These are particularly valuable for customers managing multiple system landscapes.

7.2  Agent APIs

• SAP Note 3800652  TM CO creation Agent API should support PKG & APM items
• SAP Note 3752950  TM Agent API – Consignment Order (V1)
• SAP Note 3770079  New Authorization Object T_AGTAPI

The Agent API framework is a new class of SAP TM integration — designed for AI-agent and autonomous process orchestration. Note 3752950 introduces the V1 Consignment Order Agent API, while Note 3800652 extends CO creation to support Packaging (PKG) and Autonomous Planning Module (APM) items. Note 3770079 creates the dedicated authorisation object T_AGTAPI to govern access to these endpoints — a critical control for security architects reviewing the API attack surface.

7.3  ASR Read APIs — Performance & Data Quality

• SAP Note 3759451  ASR Read API performance improvements
• SAP Note 3765315  ASR Read API performance improvements – Part 2
• SAP Note 3676599  TM ASR Read APIs: Correction for empty Freight Orders

Availability and Schedule Resource (ASR) Read APIs are high-frequency endpoints in planning-intensive deployments. Notes 3759451 and 3765315 deliver two rounds of performance optimisations — critical for customers running large-scale carrier availability checks where API response time directly impacts planning cycle time. Note 3676599 fixes a data quality issue where empty Freight Orders were incorrectly returned in API responses.

7.4  Read APIs — Delivery, DG, and Lazy Assignment

• SAP Note 3679607  Read APIs extension for the lazy assignment scenarios
• SAP Note 3737225  API for stage information per delivery
• SAP Note 3743773  Provide packaging instructions to DG Check API
• SAP Note 3781229  Prevent passing of stages without locations to PC API
• SAP Note 3716814  Unnecessary Product Compliance API calls for non-relevant documents

Note 3737225 adds stage-level delivery information to the API surface — closing a visibility gap for customers tracking multi-leg shipments in external systems. Note 3743773 enriches the Dangerous Goods (DG) Check API with packaging instruction data, essential for chemical, pharmaceutical, and hazardous materials shippers. Note 3716814 eliminates redundant Product Compliance API calls for non-relevant documents, reducing integration load and improving performance.

7.5  API Governance & Supported Versions

• SAP Note 3703361  Support status of TM OData APIs in S/4HANA Private Cloud and On-Premise
• SAP Note 3567395  Supported APIs – Private Cloud, Public Cloud, On-premise S/4HANA versions

Notes 3703361 and 3567395 are governance references — they map every TM OData API against its support status across deployment models. Every API integration project should validate against these notes before committing to an API as a stable interface.

8  Settlement Integration & GTS Extension

Two strategically important notes expand the integration footprint of SAP TM — one into financial settlement via lean service frameworks, and one into global trade compliance through a new GTS integration capability.

• SAP Note 3802781  BAdIs for TM Settlement Integration using Lean services
• SAP Note 3448484  New Feature: GTS-Integration in Decentralized Advanced Shipping and Receiving

Architectural Commentary

SAP Note 3802781 introduces a set of BAdIs that allow custom logic to be injected into the TM Settlement integration flow when using lean (lightweight) service frameworks. This is particularly relevant for organisations with complex charge calculation or settlement approval workflows that require customer-specific logic at the point of financial posting.

SAP Note 3448484 is a significant functional addition: it integrates SAP Global Trade Services (GTS) into the Decentralized Advanced Shipping and Receiving (ASR) process. For companies operating across international trade lanes with export compliance requirements, this note brings GTS-driven compliance checks directly into the ASR workflow — reducing the risk of non-compliant shipments leaving the warehouse without the required trade documentation.

 

9  Technical Corrections & BAdI Extensions

Every release cycle includes targeted corrections and BAdI additions that address issues found post-GA and fill extensibility gaps reported by customers. These notes are operationally important for system stability and for closing known functional gaps without waiting for a full feature release.

• SAP Note 3809059  On-The-Fly Data Conversion during Release and Support Package upgrade
• SAP Note 3733352  Technical correction, TM BOBF Navigator 12
• SAP Note 3773548  BOBF buffer may not correct when calling TOR OData V4 API
• SAP Note 3728224  BAdI for controlling the change documents related to charges
• SAP Note 3671117  BAdI missing for additional LINC error categories

Architectural Commentary

SAP Note 3809059 describes On-The-Fly (OTF) data conversion behaviour during Release and Support Package upgrades — critical reading for Basis teams and upgrade project managers to avoid data inconsistencies during patching windows.

SAP Note 3773548 resolves a BOBF (Business Object Processing Framework) buffer inconsistency when the TOR is accessed via OData V4. This can cause stale data to be returned in API responses — a high-priority fix for any customer using the TOR OData V4 API in a production environment.

Notes 3728224 and 3671117 introduce new BAdI implementations: Note 3728224 provides fine-grained control over charge-related change document creation, useful for compliance and audit trail requirements; Note 3671117 closes a gap in LINC (Logistics Integration and Collaboration) error handling. Both are additive and require explicit activation in the BAdI framework.

Complete Reference: All 49 SAP Notes

The table below consolidates all notes covered in this blog for quick reference.

Category	SAP Note	Title
CDS Views & VDM	3840080	New V2 view I_MaterialFreightGroup_2 (C1 released)
CDS Views & VDM	3838137	VDM Foundation layer for TOR Party node
CDS Views & VDM	3780776	TM: Enable enhancement of BO Material root via CDS view entity
CDS Views & VDM	3756405	TM: Enable enhancement of BO Location root via CDS view entity
Location Data Products	3677186	TM Clean Core Location CDS view foundation
Location Data Products	3696891	Location core CDS views, Data Product and Data Provider views
Location Data Products	3747480	Location Data Product – boolean annotations
Location Data Products	3727007	Service Development for Location and Org Units Data Products
TOR & Clean Core	3803774	BDC/Data Product – TOR
TOR & Clean Core	3688875	BDC/Data Product – TOR
TOR & Clean Core	3675348	Clean Core TOR TP Enhancement & Remote API
TOR & Clean Core	3691780	Clean Core TOR Foundation Enhancement
TOR & Clean Core	3791310	New TOR Creation Type for Local API
Order Management	3841367	Advance Developments – Order Management
Order Management	3841186	Advance Developments – Order Management
Order Management	3840156	Advance Development – Order Management
Order Management	3839471	Advance Developments – Order Management
Order Management	3837052	Advance Development – Order Management
Order Management	3839570	Advance Developments – Order Management
Order Management	3805411	Enhancements in freight order management
Order Management	3418826	TM: Cumulative enhancements
Event Reporting & Triggers	3840749	Advance Developments – Event Reporting
Event Reporting & Triggers	3839577	Advance Development – Trigger Handling
Transportation Planning	3759273	Enhancements in Transportation Planning
Transportation Planning	3758381	Freight Unit UI enhancements
Transportation Planning	3734234	MTR Determination Facade and VSR
Transportation Planning	3481260	ABAP VSS: Engine Activity Model Refactoring
APIs – Configuration	3804213	TM TOR Configuration API
APIs – Configuration	3804214	TM Configuration API
APIs – Agent	3800652	TM CO creation Agent API (PKG & APM items)
APIs – Agent	3752950	TM Agent API – Consignment Order (V1)
APIs – Agent	3770079	New Authorization Object T_AGTAPI
APIs – ASR	3759451	ASR Read API performance improvements
APIs – ASR	3765315	ASR Read API performance improvements – Part 2
APIs – ASR	3676599	TM ASR Read APIs: Correction for empty FOs
APIs – Other	3679607	Read APIs extension for lazy assignment scenarios
APIs – Other	3737225	API for stage information per delivery
APIs – Other	3743773	Provide packaging instructions to DG Check API
APIs – Other	3781229	Prevent passing of stages without locations to PC API
APIs – Other	3716814	Unnecessary Product Compliance API calls
APIs – Governance	3703361	Support status of TM OData APIs in S/4HANA
APIs – Governance	3567395	Supported APIs – Private / Public Cloud / On-Premise
Settlement & GTS	3802781	BAdIs for TM Settlement Integration using Lean services
Settlement & GTS	3448484	GTS-Integration in Decentralized Adv. Shipping and Receiving
Technical / BAdI	3809059	On-The-Fly Data Conversion during upgrade
Technical / BAdI	3733352	Technical correction, TM BOBF Navigator 12
Technical / BAdI	3773548	BOBF buffer issue when calling TOR OData V4 API
Technical / BAdI	3728224	BAdI for controlling change documents on charges
Technical / BAdI	3671117	BAdI missing for additional LINC error categories

Conclusion & Recommended Actions

S/4HANA is a strategically coherent release for SAP Transportation Management. The investments cluster around four themes:

1.  Clean Core & Extensibility — VDM notes, data product notes, and BAdI extensions collectively advance TM's Clean Core readiness, enabling customers to extend and integrate without modifying SAP code.

2.  API Breadth & Quality — 14 API notes signal SAP's commitment to an API-first integration model. The Agent API framework anticipates AI-driven logistics orchestration.

3.  Order Management Depth — The largest note cluster in this release, covering advance developments, cumulative corrections, and freight order management improvements.

4.  Event-Driven Intelligence — New Event Reporting and Trigger Handling capabilities lay the groundwork for autonomous, event-driven TM processes.

Priority Actions for S/4HANA Projects

• API Strategy Validation:  Review SAP Notes 3567395 and 3703361 early to confirm API availability in your deployment model before committing to an integration architecture.
• Immediate Production Fix:  Apply SAP Note 3773548 (BOBF buffer inconsistency with TOR OData V4 API) immediately if the TOR V4 API is used in production.
• Planning Engine Regression:  After applying SAP Note 3481260 (VSS engine activity model refactoring), run a full regression test on optimisation and manual planning scenarios.
• Order Management Note Set:  Apply the Order Management advance development notes (3841367, 3841186, 3840156, 3839471, 3837052, 3839570) as a coherent set, not individually.
• Agent API Readiness:  Begin evaluating the Agent API framework (3752950, 3800652) as a foundation for AI-assisted and autonomous logistics automation scenarios.
• GTS Compliance:  If operating international trade lanes, evaluate SAP Note 3448484 (GTS-Integration in Decentralized ASR) to close compliance gaps in the shipping and receiving workflow.

Thank you and regards,
Rogerio Lima

Source link