A deep dive into the OSS Notes shipping with SAP S/4HANA OP2025 Feature Pack Stack 2 (FPS2), covering Location and Org Unit Data Products, Transportation Order Clean Core Foundations, Business Data Cloud integration, Read API extensions, and delivery stage API capabilities.

Contents

1. Introduction & Release Context
2. Location Data Products & CDS Foundations
3. Transportation Org Units Data Products
4. Transportation Order: Clean Core & BDC Integration
5. Read API Extensions & Lazy Assignment
6. ASR Read API Performance Improvements
7. Stage Information API for Deliveries
8. Deployment Scope & Availability Matrix
9. Summary

🚀 Introduction & Release Context

SAP S/4HANA OP2025 Feature Pack Stack 2

SAP S/4HANA OP2025 FPS2 continues a strategic trajectory that has been building across recent release cycles: making Transportation Management (TM) data consumable, extensible, and clean-core compliant. The OSS Notes released with this Feature Pack Stack reflect deliberate, coordinated investment across three distinct pillars — Data Products for SAP Business Data Cloud, Clean Core CDS and RAP objects for Transportation Orders, and targeted API performance and functional enhancements.

This blog synthesizes eleven OSS Notes into a coherent picture of what has changed, why it matters, and how it impacts customers running SAP S/4HANA on Public Cloud, Private Cloud, and On-Premise landscapes. Whether your focus is on analytics-ready data products, extensibility within the clean-core boundary, or improving integration performance, FPS2 delivers meaningful progress on all fronts.

Key Themes in FPS2 TM Development:
Location & Org Unit Data Products • Annotation Enrichment • Transportation Order Clean Core RAP Foundation • BDC Data Product Enablement (TOR) Lazy Assignment Read API Extensions • ASR Performance • Stage Information API per Delivery

🌏Location Data Products & CDS Foundations

OSS Notes: 3696891 • 3747480 • 3727007

Location master data is a cornerstone of Transportation Management. It underpins route determination, freight costing, carrier selection, and shipment scheduling. FPS2 formalizes Location data as a first-class Data Product consumable by SAP Business Data Cloud and external analytics platforms, backed by a clean, layered CDS architecture.

Core CDS Layer: Interface, Projection, and Data Provider Views

Note 3696891 establishes the foundational CDS view stack for Location data. Following the standard SAP VDM (Virtual Data Model) layering approach, new core interface views, consumption projection views, and dedicated data provider views for analytics have been introduced. This structured layering ensures that Location data can be exposed cleanly without breaking the extensibility contract defined by the clean-core paradigm.

• New Location core interface CDS views — exposing master data fields as stable, versioned APIs
• Data Product views aligned to the SAP Business Data Cloud consumption model
• Data Provider views enabling OData-based, event-driven, and replication-based consumption

 Annotations for Location Data Products

Note 3747480 targets completeness annotation. -typed fields within Location Data Product CDS views receive formal Analytics and UI   ensuring that indicator fields (e.g., active status, geo-coding flags, location type indicators) are correctly typed, sortable, and filterable when projected into analytics tools such as SAP Analytics Cloud. This closes a gap where fields previously rendered incorrectly in downstream reporting.

Service Development for Location and Org Units Data Products

Note 3727007 covers the OData V4 service layer sitting above the CDS foundation. Dedicated service definitions and binding annotations are created so that Location and Org Unit Data Products are fully addressable via standard OData services. This enables:

• Direct consumption by SAP Build Apps, SAP Integration Suite flows, and third-party tools
• Consistent metadata-driven service behavior (filtering, sorting, $expand support)
• Data replication targets for SAP Business Data Cloud integration scenarios

OSS 3696891

Location Core CDS Views, Data Product & Data Provider Views

Introduces the structured CDS view stack for Location master data. Establishes stable interface, consumption, and provider views aligned to the SAP VDM layering standard.

OSS 3747480

Location Data Product – Annotations

 Analytics and   annotations to Location Data Product CDS views, ensuring indicator fields render and behave correctly in analytics and reporting contexts.

OSS 3727007

Service Development for Location and Org Units Data Products

Creates OData V4 service definitions and binding annotations for Location and Org Unit Data Products. Enables direct service consumption by integration and analytics tools and provides the replication endpoint required for SAP Business Data Cloud scenarios.

🏛TM Data Products: Transportation Org Units

OSS Note: 3742552

Note 3742552 extends the Data Product framework introduced for Location entities to cover Transportation Organizational Units. In TM, Org Units represent the organizational structure governing freight management — including transportation planning points, shipping points, and carrier roles. Making these entities available as formal Data Products enables customers to build org-unit-aware analytics, workforce analytics overlays, and cross-functional reporting that bridges HR and TM structures.

• New CDS Data Product views for Transportation Org Unit entities
• Aligned data model with Location Data Products for consistent analytics join behavior
• OData V4 service exposure enabling downstream consumption by SAP Business Data Cloud and external BI tools
• Support for delta-enabled data replication for near-real-time analytics scenarios

Together, notes 3727007, 3696891, 3747480, and 3742552 deliver a complete, analytics-ready Location and Org Unit Data Product portfolio within SAP S/4HANA TM — a foundational capability for customers migrating to SAP Business Data Cloud.

🔒Transportation Order: Clean Core & BDC Integration

OSS Notes: 3619960 • 3691780 • 3688875 • 3620011

The Transportation Order (TOR) is the central business document in SAP TM represents a legally binding freight agreement between a shipper and a carrier. The FPS2 wave delivers significant investment in making TOR data cleanly accessible through SAP's standard RAP (RESTful Application Programming) model and available as a Data Product for Business Data Cloud.

Clean Core VDM CDS Views and RAP Objects for Transportation Processing

Note 3619960 introduces clean-core compliant VDM CDS views and RAP business objects for Transportation Processing. This is a foundational step: it means that access to TOR data no longer requires ABAP BAPI calls or direct table access — instead, it is channeled through stable, versioned, release-contract CDS entities and RAP behavior implementations. Customers building extensions stay inside the clean-core boundary, enabling smooth upgrades with FPS and support pack releases.

• New VDM interface CDS views for Transportation Order processing entities
• RAP behavior definitions enabling create, update, and action operations in a cloud-ready pattern
• Stable OData service exposure with documented release contract
• Foundation for BAdI-based extensibility within the clean-core model

Clean Core TOR Foundation Enhancement for OP25 FPS2

Building directly on 3619960, note 3691780 expands the foundation with additional TOR entity coverage and deepens the RAP implementation. Enhancements include additional projection views for specialized transportation processing steps, supplementary action implementations, and enriched metadata annotations for Fiori UI rendering. This note marks the FPS2 milestone for the ongoing clean-core TOR journey started in earlier feature pack stacks.

BDC Data Product for TOR – FPS1 Baseline (3620011) and FPS2 Expansion (3688875)

Notes 3620011 (FPS1) and 3688875 (FPS2) represent the Business Data Cloud (BDC) Data Product enablement track for the Transportation Order. While 3620011 established the initial TOR Data Product structure and replication-ready CDS views in FPS1, note 3688875 expands this for FPS2, adding:

• Additional TOR header and item attributes exposed in the Data Product model
• Extended BDC replication object definitions covering status fields, date/time attributes, and organizational assignments
• Alignment with updated BDC Data Product framework conventions introduced in OP2025
• Improved delta-handling support for incremental data replication to SAP Business Data Cloud

OSS 3619960

Clean Core TOR Transportation Processing VDM CDS + RAP

Foundational clean-core VDM CDS views and RAP business objects for Transportation Order processing, replacing BAPI/table-based access patterns.

OSS 3691780

Clean Core TOR Foundation Enhancement – OP25 FPS2

Expands CDS entity coverage and deepens RAP behavior for TOR in FPS2, including additional projection views and enriched Fiori annotations.

OSS 3620011

BDC / Data Product TOR – S/4 2025 FPS1

Establishes the BDC Data Product baseline for TOR in FPS1, providing replication-ready CDS views and initial BDC replication object definitions.

OSS 3688875

BDC / Data Product TOR – OP25 FPS2

FPS2 expansion of the TOR BDC Data Product, with additional header/item attributes, improved delta replication, and alignment to updated OP2025 BDC conventions.

Why this matters for clean-core adopters: With notes 3619960 and 3691780, SAP formally places the Transportation Order within the clean-core extensibility framework. Side-by-side extensions via BAdIs or custom CDS extensions remain upgrade-stable — a critical requirement for customers on the SAP cloud ERP journey.

🔁Read API Extensions for Lazy Assignment Scenarios

OSS Note: 3679607

Note 3679607 addresses a specific and common integration pattern in Transportation Management: lazy assignment. In lazy assignment scenarios, certain TOR-to-freight-unit or freight-unit-to-shipment assignments are not resolved at document creation time but are determined dynamically based on runtime conditions (e.g., available capacities, network constraints, carrier confirmations). This deferred resolution creates a challenge for Read APIs that expect fully resolved document state.

What Extension Delivers

The Read API extension introduced in 3679607 enriches the standard TM Read APIs to correctly handle and expose entities in lazy-assigned states:

• Extended response structures that indicate lazy assignment status on freight unit and TOR entities
• New filter parameters enabling API consumers to query specifically for lazily or fully assigned documents
• Consistent handling of partially-resolved assignment chains — avoiding incomplete data returns that previously caused integration errors
• Backward-compatible extension: existing integrations continue to function; new fields are additive

This improvement is particularly relevant for customers using SAP Integration Suite, third-party TMS integrations, or custom applications that consume TM document state via OData APIs and need to differentiate between fully committed and pending assignment states.

OSS 3679607

Read APIs Extension for Lazy Assignment Scenarios

Extends standard TM Read APIs to correctly handle lazy-assigned document states. Introduces assignment status indicators, new filter parameters, and consistent partial-assignment handling — enabling reliable integration with systems that consume TM document state via OData.

⚡ASR Read API Performance Improvements

OSS Note: 3759451

Advanced Shipment and Receipt (ASR) scenarios involve high-volume data exchange between SAP TM and execution systems such as Extended Warehouse Management, third-party WMS, and carrier portals. Read API performance directly impacts the throughput and reliability of these real-time integration flows.

Optimization Scope

Note 3759451 delivers targeted query performance optimizations for the ASR Read API. The improvements focus on:

• Database access optimization: Refined CDS view join strategies and buffer utilization to reduce redundant database roundtrips
• Result set reduction: Improved early filtering at the CDS layer, pushing selection criteria closer to the data source
• Large document handling: Better pagination and streaming behavior for ASR documents with high item counts
• Parallelism improvements: Where applicable, asynchronous fetch patterns for associated entity sets

Customers operating high-volume TM landscapes — particularly those in retail, consumer goods, and industrial manufacturing — will see the most significant benefit from these improvements, particularly during peak-period shipment processing windows.

OSS 3759451

ASR Read API Performance Improvements

Delivers targeted database and CDS-layer optimizations for ASR Read API queries. Reduces roundtrips, improves large-document pagination, and applies early result-set filtering — resulting in measurable throughput improvements for high-volume TM integration scenarios.

📦API for Stage Information per Delivery

OSS Note: 3737225

Multi-leg and multi-modal shipment scenarios in TM organize execution into stages — discrete legs of a transportation chain, each with its own carrier, mode of transport, and scheduling. While stage data has been available at the shipment document level for some time, retrieving stage-level detail specifically scoped to a delivery (outbound or inbound) required navigation through multiple document relationships.

What the New API Provides

Note 3737225 introduces a dedicated API endpoint that returns stage-level information directly in the context of a delivery document. This simplifies integration patterns significantly:

• Single-call retrieval of all stages associated with a given delivery key
• Stage attributes returned include stage sequence, departure/arrival location, carrier, scheduled and actual departure/arrival times, and transport mode
• Aligned with the existing Delivery OData service namespace for consistent API surface area
• Supports $filter on stage status, enabling consumers to query only active or completed stages

This API is particularly valuable for customer-facing track-and-trace applications, logistics control tower integrations, and EWM inbound delivery scheduling scenarios where the downstream consumer only holds the delivery number and needs to understand the full transportation chain behind it.

OSS 3737225

API for Stage Information per Delivery

New API endpoint exposing transportation stage data scoped to a delivery document. Provides stage sequence, location, carrier, timing, and transport mode in a single call — enabling simplified track-and-trace and logistics control tower integrations.

🏮Deployment Scope & Availability Matrix

Public Cloud • Private Cloud • On-Premises S/4HANA

The notes covered in this blog span all three SAP S/4HANA deployment models. The table below summarizes the availability of each capability area across deployment options based on the OSS Note scope declarations.

OSS Note	Capability	Public Cloud	Private Cloud	On-Premises
3696891	Location Core CDS Views, Data Product & Data Provider Views	✓	✓	✓
3747480	Location Data Product – Annotations	✓	✓	✓
3727007	Service Development for Location & Org Units Data Products	✓	✓	✓
3742552	TM Data Products: Location, Transportation Org Units	✓	✓	✓
3619960	Clean Core TOR Transportation Processing VDM CDS + RAP	✓	✓	✓
3691780	Clean Core TOR Foundation Enhancement – OP25 FPS2	✓	✓	✓
3620011	BDC / Data Product TOR – S/4 2025 FPS1 (baseline)	✓	✓	✓
3688875	BDC / Data Product TOR – OP25 FPS2	✓	✓	✓
3679607	Read APIs Extension – Lazy Assignment Scenarios	✓	✓	✓
3759451	ASR Read API Performance Improvements	✓	✓	✓
3737225	API for Stage Information per Delivery	✓	✓	✓

Note: Customers on On-Premises S/4HANA should apply via standard SAP Note installation using SNOTE. Private Cloud and Public Cloud customers receive changes through the standard release cycle. Always validate the minimum Support Package level stated in each individual OSS Note.

Summary

What FPS2 Delivers for TM Customers

SAP S/4HANA OP2025 FPS2 represents a well-coordinated release for Transportation Management, advancing three interconnected strategic priorities simultaneously.

For analytics and data platform customers, the Location and Org Unit Data Product investments (3696891, 3747480, 3727007, 3742552) deliver a clean, replication-ready data foundation that makes TM master data a first-class citizen in SAP Business Data Cloud. The formal annotation completeness in 3747480 may appear minor in isolation but directly impacts the quality of BI artifacts built on top of these data products.

For clean-core and integration architecture teams, the TOR Clean Core RAP foundation (3619960, 3691780) and BDC Data Product tracks (3620011, 3688875) mark a significant maturation. The Transportation Order — historically one of the most complex and heavily customized objects in TM — is being systematically brought into the clean-core extensibility model, reducing technical debt and upgrading risk for customers on the cloud journey.

For integration and operations teams, the Read API lazy assignment extension (3679607), ASR performance improvements (3759451), and stage information API (3737225) are practical, high-value improvements. They reduce integration workarounds, improve throughput in production TM environments, and enable simpler, more reliable track-and-trace and control-tower integrations.

Collectively, these eleven notes represent SAP's continued commitment to making SAP S/4HANA Transportation Management a modern, API-first, analytics-ready application — equally suited to public cloud SaaS consumption and on-premises enterprise deployments.

Hope that can help you.

Thanks, and regards

Rogerio Lima.